A MIB Textual Convention for Language Tags
RFC 5131

Note: This ballot was opened for revision 03 and is now closed.

(Bill Fenner) (was Discuss, Yes) Yes

(Ted Hardie) Yes

Comment (2007-03-08 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
(Original comment resolved in discussion)

(Chris Newman) Yes

(Dan Romascanu) Yes

Comment (2007-03-07 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
1. Based on a LC comment from CE Whitehead, I suggest to replace in the DESCRIPTION clause of the LangTag TC 'This language tag' by 'The language tag described in this TC'.

2. I believe that the following comment from the MIB Doctor review of Juergen Schoenwaelder was not completly addressed:

'
   I note that the LanguageTag in RFC 2932 is 100 octets long while
   the new LanguageTag is 60 octets - so an update (in general not
   legal) is technically not possible. Furthermore, MIB modules may
   end up using different TCs with different sizes. This might
   practically not be an issue - but since the document talks about
   obsoleting IPMROUTE-STD-MIB, I would have expected some more
   discussion about this. Note that RFC 2932 LanguageTag is used by
   the MALLOC-MIB (RFC 3559) (and it is subtyped to 94 octets there,
   probably because it is used in an INDEX).'

Although now the text about RFC 2932 moved to Section 6, there is no text that warns the reader that some other documents may still use the LanguageTag TC defined in 2932.

(Jari Arkko) No Objection

(Ross Callon) No Objection

(Brian Carpenter) No Objection

(Lars Eggert) No Objection

(Sam Hartman) No Objection

Comment (2007-03-08 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
I believe the title of the document should make it much more clear
that this only defines textual conventions.

(Russ Housley) No Objection

(Cullen Jennings) No Objection

(David Kessens) No Objection

(Jon Peterson) No Objection

(Mark Townsley) No Objection

Magnus Westerlund No Objection