Re: [storm] IANA registries for iSCSI

It seems that this resolves the mismatch by codifying what IANA does,
and it works just as well as what the original text called for.  Looks
fine to me.

	paul

> -----Original Message-----
> From: storm-bounces@ietf.org [mailto:storm-bounces@ietf.org] On Behalf
> Of Mallikarjun Chadalapaka
> Sent: Wednesday, September 23, 2009 8:19 PM
> To: storm@ietf.org
> Subject: [storm] IANA registries for iSCSI
> 
> RFC 3720 in section 13.4 says the following:
> 
>    For each of these registries, IANA must record the registered
string,
>    which MUST conform to the format rules described in Section 13.5.4
>    Standard iSCSI extension item-label format for iSCSI extension
>    item-labels, and the RFC number that describes it.  The key prefix
>    (X#, Y# or Z#) is not part of the recorded string.
> 
> The "each of the registries" there refers to the three registries:
> extension
> keys, digests and auth methods.
> 
> I noticed in RFC 4850 however that IANA did something different from
> RFC
> 3720's advice, see the excerpt:
> 
>    IANA registered this key as follows:
>         o Key Name: X#NodeArchitecture
> 
> I.e., IANA's recorded string apparently included "X#".
> 
> The easiest way to address this would be to replace the last quoted
> sentence
> from RFC 3720 text ("The key prefix.....") in the new iSCSI
> consolidated
> draft with the following:
> 
>       The key prefix (X#, Y#, Z#) MUST be part of the recorded string.
> 
> Doing so would put all keys into the same registry, but the key prefix
> would
> indicate what the key relates to - extension keys, digests or auth
> methods.
> This also requires a few additional changes in the IANA section, but I
> can
> handle that.
> 
> Does that sound reasonable?  Anyone disagree?
> 
> Mallikarjun
> 
> _______________________________________________
> storm mailing list
> storm@ietf.org
> https://www.ietf.org/mailman/listinfo/storm