Subject: [Enum] [ticket.frobbit.se #870] DDDS - RFC3404 reserves ALL flag characters

From: "lconroy via RT" <[email-masked]>
Date: Sun, 26 Mar 2006 15:17:12 +0200 (CEST)

Sun Mar 26 15:17:11 2006: Request 870 was acted upon.
Transaction: Ticket created by [email-masked]
       Queue: 3761bis
     Subject: DDDS - RFC3404 reserves ALL flag characters
       Owner: Nobody
  Requestors: [email-masked]
      Status: new
 Ticket <URL: http://ticket.frobbit.se/Ticket/Display.html?id=870 >

RFC 3404 specifies that all flag characters are reserved "for future  
versions of this document".

This is wrong, IMHO. It reflects a problem with the way flag  
characters (and the expected output these imply) are specified.
[i.e. within DDDS Applications, with behaviour that must not be  
redefined in other DDDS Application documents]

Options:
(i)   simply remove the single sentence that reserves all flags -  
this is ignored by other DDDS Application specifications.
This can be done as an erratum to RFC3404.

(ii)  remove this sentence and request an IANA registry for flags (as  
suggested for future use in RFC3404).
i.e. have a separate small document to update RFC3404, listing the  
flag characters that have been defined and requesting a registry for  
them.

(iii) note that all RFCs that define a new flag must indicate that  
they update RFC3404.
(because they change the current RFC3404 reservation).

atb,
    Lawrence

_______________________________________________
enum mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/enum