[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Ltru] Issues [psg.com #982] through [psg.com #991]



I hadn't tried using rt.psg.com before. It is not obvious how to select all
and only those ltru items that are not rejected. Any hints?

‎Mark

----- Original Message ----- 
From: "Randy Presuhn" <randy_presuhn at mindspring.com>
To: "LTRU Working Group" <ltru at ietf.org>
Sent: Monday, May 16, 2005 23:37
Subject: [Ltru] Issues [psg.com #982] through [psg.com #991]


> Hi -
>
> I've entered another block of issues into the tracker.
> All these are either rejected or resolved, *except* [psg.com #985]
> You can view these using the issue tracker at https://rt.psg.com/ with
> user and password "ietf".
>
> [psg.com #982] Alpha order in extension subtags
>     rejected
>
> [psg.com #983] Ban singleton "i"
>     rejected
>
> [psg.com #984] Ban singletons "y" and "z"
>     rejected
>
> [psg.com #985] Specify case rules for canonical tags
>     open
>
> [psg.com #986] RFC 822 line wrapping in the registry
>     resolved
>
> [psg.com #987] Remove leading zeros from character references
>     resolved
>
> [psg.com #988] Remove private use tags from the registry and sample
registry
>     rejected
>
> [psg.com #989] Simplify the language tag registration form
>     resolved
>
> [psg.com #990] need to define extension registry and format
>     resolved
>
> [psg.com #991] replacement for deprecated tags needs to be
machine-readable
>     resolved
>
> If you think I've gotten any of these wrong, or you you think an issue
merits
> further discussion, *please* use an appropriate subject line to help us
track
> the discussion and link it back to the issue tracker.
>
> Randy, ltru co-chair
>
>
>
>
> _______________________________________________
> Ltru mailing list
> Ltru at lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/ltru
>
>



_______________________________________________
Ltru mailing list
Ltru at lists.ietf.org
https://www1.ietf.org/mailman/listinfo/ltru




Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.