Re: FW: I-D ACTION:draft-ietf-nsis-qspec-20.txt

Gerald Ash <[email protected]>
Newsgroups gmane.ietf.nsis
Message-ID <[email protected]>
Hi Roland,
 
> Just a small first comment:
>
> Page 43: (Sec. 7 - IANA considerations)
> QSPEC Type: since this is only 4 bits, the given ranges
> cannot be allocated and must be reassigned.
 
Good catch.
 
> I propose
> 0-7: specification required
> 8-12: local/experimental use
> 13-15: reserved
 
IMO we should allow more space for specified QOSMs.  7 seems like insufficient space for future growth (recall that 0 is assigned as the default QSPEC Type).
 
One alternative would be 
 
0 = default
1-12: specification required
12-15: local/experimental use

 
IMO a better alternative would be to expand the space for QSPEC Type, as follows:
 
In Section 5.1.1 reallocate 7 bits to QPSEC Type as follows:
 
 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|  Vers.|I|  QSPEC Type |  QSPEC Proc.  |      Length           |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 
And reallocate QSPEC Type bits in Section 7 (IANA Considerations) as follows:
 
 QSPEC Type (7 bits):
   The following value is allocated by this specification:
   0: Default
   The allocation policies for further values are as follows:
   1-31: Specification Required
   32-63: Private/Experimental Use
   64-127: Reserved

Thanks,
Jerry

 
 

_______________________________________________
nsis mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nsis
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.