|
In response to a reminder of an
earlier comment:
-------- Forwarded Message --------
> > > Hi Rob, > > > > I have two comments about the IANA section: > > > > (1) As you are changing the format of the ipseckey-rr-parameters table (by adding a new “Format description” column), please update the text with an explicit action for IANA. This change does not impact RFC4025, IMO. > I believe that the text in -04 covers this: This document requests IANA to update the "Description" field in existing entries of the "Algorithm Type Field" subregistry of the "IPSECKEY Resource Record Parameters" [IANA-IPSECKEY] to explicitly state that is for "Public" keys: "requests IANA to update" sounds like explicit action for IANA. > > > (2) I would delete this text as it is redundant with the text right before + the entry right after: > > > > IPSECKEY: > > This document defines the new IPSECKEY value TBD1 (suggested: 4) > > (Section 2) in the "Algorithm Type Field" subregistry of the > > "IPSECKEY Resource Record Parameters" registry. > I disagree, as the first section is asking IANA to change the formating (and add some text) to the current entries in the subregistry. Whereas this 2nd section is instructing IANA to ADD an additional entry to the subregistry. Two different requests, worded differently. Bob > > > Thanks. > > > > Cheers, > > Med > > |
-- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
