[Ltru] Re: Last Call: draft-mcwalter-langtag-mib (Language Ta
g MIB) to Proposed Standard
imcdonald at sharplabs.com
Sat Feb 10 22:15:58 CET 2007
Right - ASN.1 doesn't allow discontinuous integer ranges.
The DESCRIPTION clause of this textual convention could
disallow the length of '1', but it's not important to do,
With respect to max length of 60, the public MIBs that
I'm aware of often use 63 octets and the rest use a
longer max length (except for the admittedly flawed
legacy objects in Printer MIB v2, RFC 3805 - I tried
to fix them before we published RFC 3805, but got shot
down by my co-editors).
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Blue Roof Music / High North Inc
PO Box 221 Grand Marais, MI 49839
email: imcdonald at sharplabs.com
From: John Cowan [mailto:cowan at ccil.org]
Sent: Saturday, February 10, 2007 1:16 PM
To: Doug Ewell
Cc: ietf-languages at iana.org; LTRU Working Group; ietf at ietf.org
Subject: [Ltru] Re: Last Call: draft-mcwalter-langtag-mib (Language Tag
MIB) to Proposed Standard
Doug Ewell scripsit:
> Since tags of 1 character are never well-formed, I suggest that the
> SYNTAX OCTET STRING (SIZE (0..60))
> be amended to exclude the 1-character case. I assume that a zero-length
> tag, while also not defined in RFC 4646, was included in the I-D to
> allow the special case of "no tag."
AFAIK, ASN.1 does not allow sizes like (0, 2..60). I wouldn't even
bother with this change.
John Cowan cowan at ccil.org http://ccil.org/~cowan
Rather than making ill-conceived suggestions for improvement based on
uninformed guesses about established conventions in a field of study with
which familiarity is limited, it is sometimes better to stick to merely
observing the usage and listening to the explanations offered, inserting
only questions as needed to fill in gaps in understanding. --Peter Constable
Ltru mailing list
Ltru at ietf.org
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.441 / Virus Database: 268.17.33/678 - Release Date: 2/9/2007
More information about the Ietf-languages