Re: AD review: draft-ietf-nsis-nslp-auth-02.txt
Roland Bless <[email protected]> Mon, 02 Aug 2010 17:02:08 +0200
| Newsgroups | gmane.ietf.nsis |
|---|---|
| Organization | Institute of Telematics, Karlsruhe Institute of Technology (KIT) |
| Message-ID | <[email protected]> |
Hi Lars, On 29.07.2010 13:56, Lars Eggert wrote: > I re-reviewed -05. There are remaining issues that need to be fixed: Thanks for the fast review feedback. Version -06 is out, hopefully fixing all remaining issues. Sorry for not providing a real registry earlier. >> X-Type: 8 bits >> >> Session authorization attribute type (X-Type) field is one octet. >> IANA acts as a registry for X-Types as described in Section 8, >> IANA Considerations. This specification uses the following >> X-Types: > > Section 8 does not define a registry for X-Types. Done. >> SubType: >> >> The following sub-types for AUTH_ENT_ID are defined. IANA acts as >> a registry for AUTH_ENT_ID sub-types as described in Section 8, >> IANA Considerations. Initially, the registry contains the >> following sub-types of AUTH_ENT_ID: > > Section 8 does not define a registry for these sub-types. Done. >> SubType: >> >> The following sub types for SOURCE_ADDR are defined. IANA acts as >> a registry for SOURCE_ADDR sub-types as described in Section 8, >> IANA Considerations. Initially, the registry contains the >> following sub types for SOURCE_ADDR: > > Section 8 does not define a registry for these sub-types. Done. >> SubType: >> >> The following sub types for DEST_ADDR are defined. IANA acts as a >> registry for DEST_ADDR sub-types as described in Section 8, IANA >> Considerations. Initially, the registry contains the following >> sub types for DEST_ADDR: > > Section 8 does not define a registry for these sub-types. Done. >> 1. 1 NTP_TIMESTAMP NTP Timestamp Format as defined in RFC 5905 >> [RFC5905]. > > RFC5905 needs to be a normative reference. Done. Regards, Roland