Hi Guy,

 

[AB2] inline.

 

[AB1] For the registrations in the new registry that are going to refer to the 
RFC rather than tcpdump.org,


Are you referring to the registrations that will be made for the linktypes in 
the current I-D, or to future registrations?

 

[AB2] I’m referring to registrations made by the current I-D, but this question 
could also come up in the future if an I-D makes additional registrations in 
the same way (i.e. listing another organization’s website in the reference 
field). 

 

If it's for the registrations for the linktypes in the current I-D, presumably 
"the RFC" is the one that draft-ietf-opsawg-pcaplinktype will become. If so, 
which of those would refer to the RFC?

 

[AB2] There are a number of registrations in Section 2.2.1 that don’t list a 
reference (4, 6, and 7 are the first ones I see). When an RFC-to-be registers a 
name/codepoint without listing a reference for it, we have to assume that the 
document itself is the intended reference. If it’s going to be an IETF-stream 
RFC, we would also expect that the IETF would be the change controller. 

 

Thanks,

Amanda

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
OPSAWG mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to