ltru Discussion Archive - Date Index

[Prev Page] [Next Page] [Thread Index] [IETF Mailing List Directory] [ltru List Information]

Jun 01 2005

Re: [Ltru] Re: [psg.com #1018] Add Macro-Language field, Randy Presuhn
Re: [Ltru] [psg.com #1018] Add Macro-Language field, John Cowan
Re: [Ltru] [psg.com #1018] Add Macro-Language field, Randy Presuhn
Re: [Ltru] Meta, Randy Presuhn
Re: [Ltru] [psg.com #1018] Add Macro-Language field, John Cowan
[Ltru] Re: [psg.com #1018] Add Macro-Language field, Frank Ellermann
[Ltru] Meta (was: MAY a conformant implementation impose length constraints), Frank Ellermann
RE: [Ltru] Re: expectation of support for automated reading of registry, Addison Phillips
[Ltru] Re: expectation of support for automated reading of registry, Frank Ellermann
Re: [Ltru] [psg.com #1018] Add Macro-Language field, Randy Presuhn
RE: [Ltru] [psg.com #1018] Add Macro-Language field, Addison Phillips
RE: [Ltru] [psg.com #1019] move redundant tags from draft registry toan appendix, Addison Phillips
RE: [Ltru] Re: [psg.com #944] MAY a conformant implementation imposelength constraints?, Addison Phillips
[Ltru] [psg.com #1020] stable forever != canonical forever, Randy Presuhn
[Ltru] [psg.com #1019] move redundant tags from draft registry to an appendix, Randy Presuhn
[Ltru] [psg.com #1018] Add Macro-Language field, Randy Presuhn
[Ltru] [psg.com #1017] Add Required-Prefix field, Randy Presuhn
[Ltru] Re: [psg.com #944] MAY a conformant implementation impose length constraints, Randy Presuhn
[Ltru] Re: [psg.com #944] MAY a conformant implementation impose length constraints?, Frank Ellermann
RE: [Ltru] Re: [psg.com #965] expectation of support for automatedreading of registry, Addison Phillips
[Ltru] Re: [psg.com #965] expectation of support for automated reading of registry, Randy Presuhn
RE: [Ltru] Re: [psg.com #944] MAY a conformant implementation imp oselength constraints?, McDonald, Ira
RE: [Ltru] Re: [psg.com #944] MAY a conformant implementation imposelength constraints?, Addison Phillips
RE: [Ltru] Re: [psg.com #944] MAY a conformant implementation imp oselength constraints?, McDonald, Ira
RE: [Ltru] [psg.com #944] MAY a conformant implementation imposelength constraints?, Addison Phillips
Re: [Ltru] [psg.com #944] MAY a conformant implementation impose length constraints?, Randy Presuhn
RE: [Ltru] Re: [psg.com #944] MAY a conformant implementation imposelength constraints?, Addison Phillips
RE: [Ltru] Re: [psg.com #944] MAY a conformant implementation impose length constraints?, Addison Phillips
RE: [Ltru] Re: [psg.com #944] MAY a conformant implementation imp ose length constraints?, McDonald, Ira
[Ltru] Re: [psg.com #944] MAY a conformant implementation impose length constraints?, Doug Ewell
[Ltru] Re: [psg.com #944] MAY a conformant implementation impose length constraints?, Doug Ewell
[Ltru] Re: [psg.com #1016] restrict the maximum number of extlang subtags to five, Doug Ewell
Re: [Ltru] [psg.com #944] MAY a conformant implementation impose length constraints?, Randy Presuhn
RE: [Ltru] [psg.com #944] MAY a conformant implementation imposel ength constraints?, McDonald, Ira
RE: [Ltru] [psg.com #944] MAY a conformant implementation imposelength constraints?, Addison Phillips
Re: [Ltru] [psg.com #944] MAY a conformant implementation impose length constraints?, Randy Presuhn

May 31 2005

[Ltru] [psg.com #1016] restrict the maximum number of extlang subtags to five, Randy Presuhn
[Ltru] Re: extlang again, John Cowan
RE: [Ltru] [psg.com #875] should initial registry contents be madeinto an internet-draft?, Addison Phillips
Re: [Ltru] Re: [psg.com #949] remove three-character limit in sections 2.2.2, 2.2.3 (of -00), Randy Presuhn
Re: [Ltru] [psg.com #878] should the initial registry contents i-d be published as an RFC?, Randy Presuhn
Re: [Ltru] [psg.com #875] should initial registry contents be made into an internet-draft?, Randy Presuhn
Re: [Ltru] [psg.com #1011] add suppress-region, Randy Presuhn
Re: [Ltru] Re: extlang again, John Cowan
[Ltru] Re: extlang again, Frank Ellermann
RE: [Ltru] Re: extlang again, Peter Constable
Re: [Ltru] Re: extlang again, John Cowan
[Ltru] Re: extlang again, Frank Ellermann
RE: [Ltru] extlang again (was: [psg.com #1011] add suppress-region), Peter Constable
[Ltru] New registry to reflect draft-03 changes, Doug Ewell
Re: [Ltru] Re: extlang again, John Cowan

May 30 2005

[Ltru] Re: extlang again, Frank Ellermann
[Ltru] Re: extlang again (was: [psg.com #1011] add suppress-region), Doug Ewell
RE: [Ltru] use of region subtags, Addison Phillips
RE: [Ltru] use of region subtags, Martin Duerst
[Ltru] Re: [psg.com #966] remove something from security considerations, Frank Ellermann
[Ltru] extlang again (was: [psg.com #1011] add suppress-region), Frank Ellermann
[Ltru] Re: extlang again, Doug Ewell
[Ltru] Re: [psg.com #1011] add suppress-region, Doug Ewell
[Ltru] Re: [psg.com #966] remove something from security considerations, Doug Ewell

May 29 2005

Re: [Ltru] Re: extlang again, John Cowan
[Ltru] Re: extlang again, Frank Ellermann
Re: [Ltru] extlang again (was: [psg.com #1011] add suppress-region), John Cowan
[Ltru] extlang again (was: [psg.com #1011] add suppress-region), Frank Ellermann
Re: [Ltru] Re: [psg.com #1011] add suppress-region, John Cowan
[Ltru] Re: [psg.com #1011] add suppress-region, Frank Ellermann
Re: [Ltru] Re: [psg.com #1011] add suppress-region, John Cowan
[Ltru] Re: [psg.com #966] remove something from security considerations, Frank Ellermann
[Ltru] Re: [psg.com #1011] add suppress-region, Frank Ellermann
[Ltru] Re: last response, Doug Ewell

May 28 2005

[Ltru] Re: [psg.com #1014] make scope of applicability universal, Doug Ewell
Re: [Ltru] Re: [psg.com #1011] add suppress-region, John Cowan
[Ltru] Re: [psg.com #1011] add suppress-region, Doug Ewell
Re: [Ltru] [psg.com #966] remove something from security considerations, Doug Ewell
[Ltru] [psg.com #1014] make scope of applicability universal, Randy Presuhn
[Ltru] three more closed issues: 1012, 1013, and 1015, Randy Presuhn

May 27 2005

Re: [Ltru] [psg.com #966] remove something from security considerations, Randy Presuhn
Re: [Ltru] [psg.com #1011] add suppress-region, Randy Presuhn
RE: [Ltru] [psg.com #1011] add suppress-region, Peter Constable
[Ltru] [psg.com #1011] add suppress-region, Randy Presuhn
Re: [Ltru] use of region subtags, John Cowan
RE: [Ltru] use of region subtags, Addison Phillips
[Ltru] use of region subtags, Peter Constable
[Ltru] [psg.com #1010] conformance terminology, Randy Presuhn
[Ltru] [psg.com #1009] generic variant subtags, Randy Presuhn

May 26 2005

[Ltru] Re: last response, Randy Presuhn
Re: [Ltru] [psg.com #969] character set considerations, Randy Presuhn
[Ltru] Re: last response, Frank Ellermann
RE: [Ltru] last response (was: character set considerations materialis contradictory), Peter Constable
[Ltru] last response (was: character set considerations materialis contradictory), JFC (Jefsey) Morfin
Re: [Ltru] [psg.com#967] address homograph issues in security considerations, Randy Presuhn
Re: [Ltru] [psg.com #969] character set considerations materialis contradictory, Randy Presuhn
[Ltru] [psg.com #1007] future-proofing wrt anticiapted ISO 639-6, Randy Presuhn

May 25 2005

[Ltru] On the records (was Editorial error in BNF), JFC (Jefsey) Morfin
RE: [Ltru] Editorial error in BNF, Debbie Garside
Re: [Ltru] Re: Fix for ambiguous conformance requirements, Martin Duerst
[Ltru] Re: Editorial error in BNF, Doug Ewell
RE: [Ltru] Editorial error in BNF, JFC (Jefsey) Morfin

May 24 2005

[Ltru] Re: [psg.com#967]addresshomographissuesinsecurityconsiderations, Frank Ellermann
Re: [Ltru] Re: Fix for ambiguous conformance requirements, Randy Presuhn
Re: [Ltru] Editorial error in BNF, Randy Presuhn
RE: [Ltru] [psg.com #941] determining currency of registry versions, Addison Phillips
Re: [Ltru] [psg.com #967]addresshomographissuesinsecurityconsiderations, Mark Davis
RE: [Ltru] [psg.com #967] addresshomographissuesinsecurityconside rations, McDonald, Ira
RE: [Ltru] [psg.com #967] addresshomographissuesinsecurityconsiderations, Addison Phillips
RE: [Ltru] Editorial error in BNF, Peter Constable
RE: [Ltru] Re: Fix for ambiguous conformance requirements, Addison Phillips
Re: [Ltru] Editorial error in BNF, John Cowan
RE: [Ltru] Editorial error in BNF, Addison Phillips
RE: [Ltru] Editorial error in BNF, McDonald, Ira
RE: [Ltru] Editorial error in BNF, Peter Constable
RE: [Ltru] Editorial error in BNF, Addison Phillips
RE: [Ltru] Editorial error in BNF, Peter Constable
RE: [Ltru] Editorial error in BNF, Peter Constable
RE: [Ltru] Re: Fix for ambiguous conformance requirements, Addison Phillips
[Ltru] Re: Fix for ambiguous conformance requirements, Doug Ewell
[Ltru] Re: [psg.com #967] address homograph issues in security considerations, Frank Ellermann
[Ltru] Re: Fix for ambiguous conformance requirements, Frank Ellermann
Re: [Ltru] Re: Fix for ambiguous conformance requirements, Randy Presuhn
[Ltru] issue resolutions 999 & 1000, Randy Presuhn
[Ltru] Re: [psg.com #967] address homograph issues in security considerations, Doug Ewell
[Ltru] Re: [psg.com #967] address homograph issues in security considerations, Doug Ewell
[Ltru] Re: Fix for ambiguous conformance requirements, Doug Ewell
Re: [Ltru] [psg.com #967] address homograph issues in security considerations, Randy Presuhn
RE: [Ltru] [psg.com #967] address homograph issues insecurityconsiderations, JFC (Jefsey) Morfin
Re: [Ltru] Editorial error in BNF, Mark Davis
RE: [Ltru] [psg.com #967] addresshomographissuesinsecurityconsiderations, Martin Duerst
[Ltru] Re: Editorial error in BNF, Frank Ellermann
Re: [Ltru] Editorial error in BNF, Randy Presuhn

May 23 2005

RE: [Ltru] Editorial error in BNF, Addison Phillips
[Ltru] Editorial error in BNF, John Cowan
RE: [Ltru] [psg.com #967] address homographissuesinsecurityconsiderations, Addison Phillips
Re: [Ltru] [psg.com #967] address homograph issuesinsecurityconsiderations, Randy Presuhn
RE: [Ltru] [psg.com #967] address homograph issues insecurityconsiderations, Addison Phillips
Re: [Ltru] Fix for ambiguous conformance requirements, Mark Davis
RE: [Ltru] Fix for ambiguous conformance requirements, McDonald, Ira
RE: [Ltru] [psg.com #967] address homograph issues in securityconsiderations, Peter Constable
[Ltru] draft of draft-03 posted..., Addison Phillips
Re: [Ltru] Fix for ambiguous conformance requirements, Mark Davis
RE: [Ltru] Fix for ambiguous conformance requirements, Addison Phillips
RE: [Ltru] Fix for ambiguous conformance requirements, McDonald, Ira

May 22 2005

RE: [Ltru] Fix for ambiguous conformance requirements, Addison Phillips
[Ltru] Fix for ambiguous conformance requirements, McDonald, Ira
RE: [Ltru] Re: [psg.com #954] all aliases must be equally support ed, Addison Phillips
Re: [Ltru] Re: [psg.com #954] all aliases must be equally support ed, Mark Davis

May 21 2005

[Ltru] Re: [psg.com #967] address homograph issues in security considerations, Doug Ewell
[Ltru] Re: [psg.com #954] all aliases must be equally support ed, Frank Ellermann
Re: [Ltru] Re: [psg.com #954] all aliases must be equally support ed, Mark Davis
RE: [Ltru] Re: [psg.com #954] all aliases must be equally support ed, McDonald, Ira
RE: [Ltru] Re: [psg.com #954] all aliases must be equally support ed, Addison Phillips
Re: [Ltru] [psg.com #967] address homograph issues in security considerations, John Cowan
RE: [Ltru] [psg.com #954] all aliases must be equally supported, Peter Constable
[Ltru] Re: [psg.com #954] all aliases must be equally support ed, Frank Ellermann
Re: [Ltru] RE: Some comments on draft-ietf-ltru-matching-00, Randy Presuhn
Re: [Ltru] [psg.com #992] provide way to alias language-variant combination to a lang-extlang combination, Randy Presuhn
Re: [Ltru] [psg.com #992] provide way to alias language-variant combination to a lang-extlang combination, Randy Presuhn
[Ltru] Tickets [psg.com #993] through [psg.com #996], Randy Presuhn
[Ltru] [psg.com #998] fate of grandfathered tags when subtags registered or replacements found, Randy Presuhn
[Ltru] [psg.com #997[ simplify ABNF by merging field and record-jar definitions, Randy Presuhn
Re: [Ltru] [psg.com #967] address homograph issues in security considerations, Randy Presuhn

May 20 2005

[Ltru] I-D ACTION:draft-ietf-ltru-registry-02.txt, Internet-Drafts
RE: [Ltru] [psg.com #954] all aliases must be equally supported, Misha Wolf
Re: [Ltru] [psg.com #954] all aliases must be equally supported, John Cowan
RE: [Ltru] [psg.com #954] all aliases must be equally supported, Misha Wolf
RE: [Ltru] [psg.com #954] all aliases must be equally supported, Addison Phillips
RE: [Ltru] [psg.com #954] all aliases must be equally supported, Misha Wolf
Re: [Ltru] [psg.com #954] all aliases must be equally supported, Randy Presuhn
RE: [Ltru] Re: [psg.com #954] all aliases must be equally support ed, Addison Phillips
RE: [Ltru] Re: [psg.com #954] all aliases must be equally support ed, McDonald, Ira
Re: [Ltru] UNSD adds two new codes, John Cowan
[Ltru] Re: [psg.com #954] all aliases must be equally supported, Frank Ellermann
[Ltru] Re: UNSD adds two new codes, Frank Ellermann
[Ltru] Re: [psg.com #954] all aliases must be equally supported, Mark Davis
[Ltru] UNSD adds two new codes, Doug Ewell
[Ltru] Re: [psg.com #954] all aliases must be equally supported, Doug Ewell
[Ltru] Re: [psg.com #954] all aliases must be equally supported, Doug Ewell
[Ltru] Re: [psg.com #954] all aliases must be equally supported, Doug Ewell
[Ltru] Re: [psg.com #985] Specify case rules for canonical tags, Frank Ellermann
[Ltru] Re: Open points before -02, Doug Ewell
[Ltru] Re: [psg.com #985] Specify case rules for canonical tags, Doug Ewell
[Ltru] Submission: LTRU Registry Draft 02, Addison Phillips

May 19 2005

RE: [Ltru] Re: [psg.com #954] all aliases must be equally support ed, Addison Phillips
Re: [Ltru] while we're housekeeping..., Randy Presuhn
Re: [Ltru] Re: [psg.com #954] all aliases must be equally support ed, Mark Davis
[Ltru] while we're housekeeping..., Addison Phillips
Re: [Ltru] [psg.com #894] add figure-of-merit matching, Randy Presuhn
Re: [Ltru] Re: [psg.com #901] add "Deprecated" field, Randy Presuhn
Re: [Ltru] Re: [psg.com #954] all aliases must be equally support ed, John Cowan
Re: [Ltru] Re: [psg.com #954] all aliases must be equally support ed, Mark Davis
Re: [Ltru] Re: [psg.com #954] all aliases must be equally supported, John Cowan
[Ltru] Re: [psg.com #954] all aliases must be equally supported, Frank Ellermann
RE: [Ltru] Re: [psg.com #954] all aliases must be equally support ed, Addison Phillips
Re: [Ltru] Re: [psg.com #954] all aliases must be equally support ed, John Cowan
RE: [Ltru] Re: [psg.com #954] all aliases must be equally support ed, Addison Phillips
Re: [Ltru] [psg.com #992] provide way to aliaslanguage-variantcombination to a lang-extlang combination, Mark Davis
RE: [Ltru] [psg.com #992] provide way to alias language-variantcombination to a lang-extlang combination, Addison Phillips
[Ltru] Re: [psg.com #992] provide way to alias language-variant combination to a lang-extlang combination, Frank Ellermann
[Ltru] Re: Open points before -02, Frank Ellermann
[Ltru] Re: [psg.com #954] all aliases must be equally support ed, Frank Ellermann
Re: [Ltru] Open points before -02, John Cowan
[Ltru] Schizophrenic treatment of grandfathered tags, John Cowan
Re: [Ltru] grandfathered tags and generative capacity, John Cowan
Re: [Ltru] [psg.com #992] provide way to alias language-variant combination to a lang-extlang combination, John Cowan

May 18 2005

Re: [Ltru] Open points before -02, Randy Presuhn
[Ltru] [psg.com #992] provide way to alias language-variant combination to a lang-extlang combination, Randy Presuhn
Re: [Ltru] [psg.com #954] all aliases must be equally supported, Randy Presuhn
RE: [Ltru] Re: [psg.com #954] all aliases must be equally support ed, Misha Wolf
Re: [Ltru] Re: [psg.com #985] Specify case rules for canonical tags, Randy Presuhn
RE: [Ltru] Re: [psg.com #954] all aliases must be equally support ed, McDonald, Ira
[Ltru] completed milestone for ltru charter, Randy Presuhn
Re: [Ltru] Re: [psg.com #954] all aliases must be equally supported, John Cowan
[Ltru] Re: [psg.com #954] all aliases must be equally supported, Frank Ellermann
[Ltru] Re: Open points before -02, Doug Ewell
[Ltru] Re: [psg.com #954] all aliases must be equally supported, Doug Ewell
[Ltru] Re: [psg.com #954] all aliases must be equally supported, Doug Ewell
[Ltru] Re: grandfathered tags and generative capacity, Doug Ewell
[Ltru] Re: [psg.com #985] Specify case rules for canonical tags, Doug Ewell
[Ltru] Re: Some comments on draft-ietf-ltru-matching-00, Frank Ellermann
[Ltru] Re: [psg.com #985] Specify case rules for canonical tags, Frank Ellermann
[Ltru] grandfathered tags and generative capacity, Peter Constable

May 17 2005

[Ltru] RE: Some comments on draft-ietf-ltru-matching-00, Addison Phillips
[Ltru] I-D ACTION:draft-ietf-ltru-matching-00.txt, Internet-Drafts
RE: [Ltru] Re: [psg.com #985] Specify case rules for canonical ta gs, McDonald, Ira
Re: [Ltru] Re: [psg.com #985] Specify case rules for canonical tags, Randy Presuhn
Re: [Ltru] [psg.com #985] Specify case rules for canonical tags, John Cowan
RE: [Ltru] [psg.com #985] Specify case rules for canonical tags, Addison Phillips
Re: [Ltru] [psg.com #985] Specify case rules for canonical tags, John Cowan
RE: [Ltru] [psg.com #985] Specify case rules for canonical tags, Addison Phillips
Re: [Ltru] [psg.com #985] Specify case rules for canonical tags, John Cowan
[Ltru] Re: [psg.com #985] Specify case rules for canonical tags, Frank Ellermann
Re: [Ltru] [psg.com #960] use ITU E.164 calling codes instead of ISO 3166 country codes, Randy Presuhn
Re: [Ltru] Issues [psg.com #982] through [psg.com #991], Randy Presuhn
Re: [Ltru] Issues [psg.com #982] through [psg.com #991], Mark Davis
[Ltru] [psg.com #985] Specify case rules for canonical tags, Randy Presuhn
[Ltru] Issues [psg.com #982] through [psg.com #991], Randy Presuhn
[Ltru] Re: [WG I-D Submission] draft-ietf-ltru-matching-00, Martin Duerst

May 16 2005

[Ltru] Re: [WG I-D Submission] draft-ietf-ltru-matching-00, Randy Presuhn
[Ltru] [WG I-D Submission] draft-ietf-ltru-matching-00, Addison Phillips
RE: [Ltru] Re: Open points before -02, Addison Phillips
[Ltru] Re: Open points before -02, Frank Ellermann

May 14 2005

Re: [Ltru] New version of matching draft..., Randy Presuhn

May 13 2005

RE: [Ltru] New version of matching draft..., Addison Phillips
Re: [Ltru] New version of matching draft..., Randy Presuhn
[Ltru] New version of matching draft..., Addison Phillips
[Ltru] RE: sad and afflicting (was [psg.com #969]character set considerations material is contradictory), Peter Constable
[Ltru] Suspension of Jefsey until 2005-05-22, Randy Presuhn
RE: [Ltru] [psg.com #964] section 3.4 of -00 is hard to understand, JFC (Jefsey) Morfin
[Ltru] sad and afflicting (was [psg.com #969]character set considerations material is contradictory), JFC (Jefsey) Morfin
[Ltru] ltru issues 972-981, Randy Presuhn

May 12 2005

[Ltru] Re: [psg.com #967] address homograph issues insecurityconsiderations, Frank Ellermann
[Ltru] Re: [psg.com #969]character set considerations material is contradictory, Frank Ellermann
[Ltru] Re: [psg.com #970] add reference to xml schema version 1.0, Frank Ellermann
[Ltru] Re: Can someone map these comments into proposals?, Frank Ellermann
RE: [Ltru] [psg.com #967] address homograph issuesinsecurityconsiderations, Addison Phillips
RE: [Ltru] [psg.com #967] address homograph issuesinsecurityconsi derations, McDonald, Ira
RE: [Ltru] Re: [psg.com #954] all aliases must be equally supported, JFC (Jefsey) Morfin
Re: [Ltru] [psg.com #967] address homograph issues insecurityconsiderations, Randy Presuhn
RE: [Ltru] [psg.com #967] address homograph issuesinsecurityconsiderations, Addison Phillips
RE: [Ltru] [psg.com #964] section 3.4 of -00 is hard to understand, Addison Phillips
RE: [Ltru] [psg.com #967] address homograph issues insecurityconsiderations, Peter Constable
RE: [Ltru] [psg.com #967] address homograph issues insecuritycons iderations, McDonald, Ira
RE: [Ltru] [psg.com #967] address homograph issuesinsecurityconsiderations, Peter Constable
RE: [Ltru] [psg.com #964] section 3.4 of -00 is hard to understand, Peter Constable
RE: [Ltru] [psg.com #967] address homograph issues insecurityconsiderations, Misha Wolf
RE: [Ltru] [psg.com #967] address homograph issues in securityconsiderations, Addison Phillips
RE: [Ltru] [psg.com #969]character set considerations material iscontradictory, Peter Constable
RE: [Ltru] [psg.com #964] section 3.4 of -00 is hard to understand, Addison Phillips
RE: [Ltru] [psg.com #965] expectation of support for automated readingof registry, Addison Phillips
RE: [Ltru] [psg.com #963] section on registration procedure is confusing, Addison Phillips
RE: [Ltru] [psg.com #967] address homograph issues in securityconsiderations, Peter Constable
RE: [Ltru] Re: [psg.com #954] all aliases must be equally supported, Peter Constable
Re: [Ltru] [psg.com #963] section on registration procedure is confusing, John Cowan
RE: xml2rfc category (was RE: [Ltru] Re: [psg.com #938] shouldintroduction alludetointendedbcp status?), Scott Hollenbeck
Re: [Ltru] RFC 2277 - considerations, Erkki Kolehmainen
Re: [Ltru] Re: [psg.com #951] extensibility via codes not maintained by ISO, Erkki Kolehmainen
[Ltru] [psg.com #970] add reference to xml schema version 1.0, Randy Presuhn
[Ltru] [psg.com #969]character set considerations material is contradictory, Randy Presuhn
[Ltru] [psg.com #968] load on IANA server by applications, Randy Presuhn
[Ltru] [psg.com #967] address homograph issues in security considerations, Randy Presuhn
[Ltru] [psg.com #966] remove something from security considerations, Randy Presuhn
[Ltru] [psg.com #965] expectation of support for automated reading of registry, Randy Presuhn
[Ltru] [psg.com #964] section 3.4 of -00 is hard to understand, Randy Presuhn
[Ltru] [psg.com #963] section on registration procedure is confusing, Randy Presuhn
[Ltru] [psg.com #962] use CAN instead of MAY in section 3.3 of -00, Randy Presuhn
[Ltru] [psg.com #961] re-work part 3 of -00 draft, Randy Presuhn
[Ltru] Can someone map these comments into proposals?, Randy Presuhn
Re: [Ltru] [psg.com #941] determining currency of registry versions, Randy Presuhn
Re: [Ltru] [psg.com #958] move tag formation rules, Randy Presuhn
Re: [Ltru] [psg.com #959] consolidate review process instructions, Randy Presuhn
Re: jamais deux sans trois ? (was RE: [Ltru] RFC 2277 - considerations), JFC (Jefsey) Morfin
RE: [Ltru] Re: [psg.com #954] all aliases must be equally supported, JFC (Jefsey) Morfin
Re: [Ltru] Re: [psg.com #951] extensibility via codes not maintained by ISO, JFC (Jefsey) Morfin
Re: [Ltru] [psg.com #960] use ITU E.164 calling codes instead of ISO 3166 country codes, JFC (Jefsey) Morfin
Re: [Ltru] [psg.com #952] how to determine whether an ISO 639 registration request has been processed?, JFC (Jefsey) Morfin
Re: jamais deux sans trois ? (was RE: [Ltru] RFC 2277 - considerations), Martin Duerst
Re: [Ltru] Interim and Paris?, Randy Presuhn

May 11 2005

Re: [Ltru] [psg.com #952] how to determine whether an ISO 639 registration request has been processed?, Randy Presuhn
Re: xml2rfc category (was RE: [Ltru] Re: [psg.com #938] should introduction alludetointendedbcp status?), Frank Ellermann
RE: [Ltru] Re: [psg.com #954] all aliases must be equally supported, Addison Phillips
[Ltru] Re: [psg.com #954] all aliases must be equally supported, Frank Ellermann
RE: [Ltru] Re: [psg.com #938] should introduction allude tointendedbcp status?, JFC (Jefsey) Morfin
Re: [Ltru] Re: [psg.com #951] extensibility via codes not maintained by ISO, John Cowan
RE: xml2rfc category (was RE: [Ltru] Re: [psg.com #938] shouldintroduction alludetointendedbcp status?), Addison Phillips
Re: [Ltru] [psg.com #960] use ITU E.164 calling codes instead of ISO 3166 country codes, Randy Presuhn
Re: [Ltru] Interim and Paris?, JFC (Jefsey) Morfin
Re: [Ltru] [psg.com #960] use ITU E.164 calling codes instead of ISO 3166 country codes, JFC (Jefsey) Morfin
Re: [Ltru] [psg.com #952] how to determine whether an ISO 639 registration request has been processed?, JFC (Jefsey) Morfin
Re: [Ltru] Re: [psg.com #951] extensibility via codes not maintained by ISO, JFC (Jefsey) Morfin
Re: [Ltru] Re: [psg.com #954] all aliases must be equally supported, JFC (Jefsey) Morfin
xml2rfc category (was RE: [Ltru] Re: [psg.com #938] should introduction alludetointendedbcp status?), Scott Hollenbeck
[Ltru] Re: [psg.com #938] should introduction allude tointendedbcp status?, Frank Ellermann
Re: [Ltru] Re: [psg.com #957] compatibility of description format with ISO table format, Randy Presuhn
Re: [Ltru] [psg.com #951] extensibility via codes not maintained by ISO, Randy Presuhn
Re: [Ltru] Re: [psg.com #950] iso 3166 inadequate for regional variants, Randy Presuhn
RE: [Ltru] Re: [psg.com #938] should introduction allude tointendedbcp status?, Scott Hollenbeck
RE: [Ltru] Re: [psg.com #938] should introduction allude tointendedbcp status?, Addison Phillips
RE: [Ltru] Re: [psg.com #938] should introduction allude to intendedbcp status?, Addison Phillips
Re: [Ltru] Re: [psg.com #938] should introduction allude to intended bcp status?, Randy Presuhn
RE: [Ltru] Re: [psg.com #938] should introduction allude tointendedbcp status?, Scott Hollenbeck
[Ltru] Re: [psg.com #954] all aliases must be equally supported, Frank Ellermann
Re: [Ltru] [psg.com #942] clarify advice on use of subtags, Randy Presuhn
Re: [Ltru] [psg.com #952] how to determine whether an ISO 639 registration request has been processed?, Randy Presuhn
RE: [Ltru] Re: [psg.com #938] should introduction allude to intendedbcp status?, Addison Phillips
RE: [Ltru] [psg.com #952] how to determine whether an ISO 639registration request has been processed?, Peter Constable
RE: [Ltru] Re: [psg.com #954] all aliases must be equally supported, Addison Phillips
Re: [Ltru] Re: [psg.com #938] should introduction allude to intended bcp status?, Randy Presuhn
Re: [Ltru] [psg.com #952] how to determine whether an ISO 639 registration request has been processed?, Randy Presuhn
[Ltru] Re: date problem, Randy Presuhn
[Ltru] Interim and Paris?, Randy Presuhn
[Ltru] [psg.com #960] use ITU E.164 calling codes instead of ISO 3166 country codes, Randy Presuhn
[Ltru] Re: [psg.com #954] all aliases must be equally supported, Frank Ellermann
Re: [Ltru] Re: [psg.com #954] all aliases must be equally supported, John Cowan
Re: [Ltru] Re: [psg.com #954] all aliases must be equally supported, Mark Davis
[Ltru] meta (was: [psg.com #952] how to determine whether an ISO 639 registration request has been processed?), Frank Ellermann
RE: [Ltru] Re: [psg.com #951] extensibility via codes not maintained byISO, Addison Phillips
RE: [Ltru] Re: [psg.com #954] all aliases must be equally supported, Addison Phillips
[Ltru] Re: [psg.com #954] all aliases must be equally supported, Frank Ellermann
RE: [Ltru] [psg.com #941] determining currency of registry versions, Peter Constable
Re: [Ltru] Re: [psg.com #951] extensibility via codes not maintained by ISO, John Cowan
Re: [Ltru] Re: [psg.com #950] iso 3166 inadequate for regional variants, JFC (Jefsey) Morfin
[Ltru] Re: a way toward homograph resolution ?, JFC (Jefsey) Morfin
Re: [Ltru] Re: [psg.com #952] how to determine whether an ISO 639 registration request has been processed?, JFC (Jefsey) Morfin
Re: [Ltru] Re: [psg.com #952] how to determine whether an ISO 639 registration request has been processed?, JFC (Jefsey) Morfin
[Ltru] date problem, JFC (Jefsey) Morfin
Re: [Ltru] Re: [psg.com #951] extensibility via codes not maintained by ISO, JFC (Jefsey) Morfin
Re: [Ltru] Re: [psg.com #955] expand scope to include computer languages, JFC (Jefsey) Morfin
[Ltru] Re: [psg.com #952] how to determine whether an ISO 639 registration request has been processed?, Frank Ellermann
[Ltru] Re: [psg.com #952] how to determine whether an ISO 639 registration request has been processed?, Doug Ewell
[Ltru] Re: [psg.com #954] all aliases must be equally supported, Doug Ewell
Re: [Ltru] Re: [psg.com #952] how to determine whether an ISO 639 registration request has been processed?, John Cowan
Re: [Ltru] Re: [psg.com #946] use of both length and position toidentify subtag problematic, John Cowan
Re: [Ltru] BCP forever (was: [psg.com #957]), John Cowan
[Ltru] Re: [psg.com #952] how to determine whether an ISO 639 registration request has been processed?, Frank Ellermann
[Ltru] Re: [psg.com #946] use of both length and position toidentify subtag problematic, Frank Ellermann
[Ltru] BCP forever (was: [psg.com #957]), Frank Ellermann
[Ltru] Re: [psg.com #954] all aliases must be equally supported, Frank Ellermann
[Ltru] Re: [psg.com #956] document use of "" as deprecation indicator, Doug Ewell
[Ltru] Re: [psg.com #955] expand scope to include computer languages, Doug Ewell
[Ltru] Re: [psg.com #954] all aliases must be equally supported, Doug Ewell
[Ltru] Re: [psg.com #953] change process for handling registration requests, Doug Ewell
[Ltru] Re: [psg.com #952] how to determine whether an ISO 639 registration request has been processed?, Doug Ewell
[Ltru] Re: [psg.com #951] extensibility via codes not maintained by ISO, Doug Ewell
Re: [Ltru] [psg.com #941] determining currency of registry versions, Randy Presuhn
[Ltru] Re: [psg.com #950] iso 3166 inadequate for regional variants, Doug Ewell
Re: [Ltru] Re: [psg.com #937] is the word "interchange" in the abstract unclear?, JFC (Jefsey) Morfin
[Ltru] Re: RFC 2277 - considerations, Doug Ewell
[Ltru] Re: [psg.com #949] remove three-character limit in sections 2.2.2, 2.2.3 (of -00), Doug Ewell
[Ltru] Re: [psg.com #948] deprecate two-letter language codes in favor of three-letter ones, Doug Ewell
[Ltru] Re: [psg.com #947] is set of possible primary languages too constrained?, Doug Ewell
[Ltru] Re: [psg.com #946] use of both length and position to identify subtag problematic, Doug Ewell
[Ltru] Re: [psg.com #945] use "." to separate subtags, Doug Ewell
[Ltru] Re: [psg.com #944] MAY a conformant implementation impose length constraints?, Doug Ewell
[Ltru] Re: RFC 2277 - considerations, Frank Ellermann
[Ltru] Re: [psg.com #943] number of subtags SHOULD be limited to four, Doug Ewell
[Ltru] Re: [psg.com #942] clarify advice on use of subtags, Doug Ewell
[Ltru] Re: [psg.com #941] determining currency of registry versions, Doug Ewell
[Ltru] Re: [psg.com #940] is the word "recognized" unclear in the syntax section?, Doug Ewell
Re: [Ltru] Re: [psg.com #957] compatibility of description format withISO table format, Randy Presuhn
[Ltru] Re: [psg.com #939] explain difference between tags and labels, Doug Ewell
[Ltru] Re: [psg.com #938] should introduction allude to intended bcp status?, Doug Ewell
[Ltru] Re: [psg.com #937] is the word "interchange" in the abstract unclear?, Doug Ewell
[Ltru] Re: [psg.com #936] is the phrase "information object" in the abstract unclear?, Doug Ewell
Re: [Ltru] Re: [psg.com #954] all aliases must be equally supported, Randy Presuhn
[Ltru] Re: [psg.com #935] is the word "indicate" in the abstract unclear?, Doug Ewell
[Ltru] Re: [psg.com #934] repertoire for descriptions in registry entries, Doug Ewell
[Ltru] Re: [psg.com #957] compatibility of description format with ISO table format, Frank Ellermann
[Ltru] Re: [psg.com #933] Java support, Doug Ewell
[Ltru] Re: [psg.com #954] all aliases must be equally supported, Frank Ellermann
RE: [Ltru] Re: [psg.com #944] MAY a conformant implementation impose length constraints?, Addison Phillips
RE: [Ltru] [psg.com #944] MAY a conformant implementation imposelengthconstraints?, Addison Phillips
RE: [Ltru] [psg.com #941] determining currency of registry versions, Addison Phillips
[Ltru] Re: [psg.com #944] MAY a conformant implementation impose length constraints?, Frank Ellermann
Re: [Ltru] [psg.com #944] MAY a conformant implementation impose lengthconstraints?, Randy Presuhn
Re: [Ltru] Re: [psg.com #934] repertoire for descriptionsinregistryentries, Mark Davis
Re: [Ltru] [psg.com #943] number of subtags SHOULD be limited to four, Randy Presuhn
Re: [Ltru] [psg.com #941] determining currency of registry versions, Randy Presuhn
[Ltru] Re: [psg.com #934] repertoire for descriptions inregistryentries, Frank Ellermann
jamais deux sans trois ? (was RE: [Ltru] RFC 2277 - considerations), JFC (Jefsey) Morfin
Re: [Ltru] [psg.com #949] remove three-character limit in sections 2.2.2, 2.2.3 (of -00), JFC (Jefsey) Morfin
RE: [Ltru] Re: [psg.com #946] use of both length and positiontoidentify subtag problematic, Peter Constable
RE: [Ltru] Re: [psg.com #946] use of both length and positiontoidentify subtag problematic, JFC (Jefsey) Morfin
RE: [Ltru] RFC 2277 - considerations, Peter Constable

May 10 2005

RE: [Ltru] Re: [psg.com #946] use of both length and positiontoidentify subtag problematic, Peter Constable
[Ltru] [psg.com #959] consolidate review process instructions, Randy Presuhn
[Ltru] [psg.com #958] move tag formation rules, Randy Presuhn
[Ltru] [psg.com #957] compatibility of description format with ISO table format, Randy Presuhn
[Ltru] [psg.com #956] document use of "" as deprecation indicator, Randy Presuhn
[Ltru] [psg.com #955] expand scope to include computer languages, Randy Presuhn
[Ltru] [psg.com #954] all aliases must be equally supported, Randy Presuhn
Re: [Ltru] [psg.com #950] iso 3166 inadequate for regional variants, John Cowan
[Ltru] [psg.com #953] change process for handling registration requests, Randy Presuhn
[Ltru] [psg.com #952] how to determine whether an ISO 639 registration request has been processed?, Randy Presuhn
[Ltru] [psg.com #951] extensibility via codes not maintained by ISO, Randy Presuhn
[Ltru] [psg.com #950] iso 3166 inadequate for regional variants, Randy Presuhn
Re: [Ltru] RFC 2277 - considerations, JFC (Jefsey) Morfin
Re: [Ltru] [psg.com #934] repertoire for descriptions inregistryentries, JFC (Jefsey) Morfin
Re: [Ltru] RFC 2277 - considerations, JFC (Jefsey) Morfin
Re: [Ltru] [psg.com #934] repertoire for descriptions inregistryentries, Marion Gunn
Re: [Ltru] RFC 2277 - considerations, ned . freed
Re: [Ltru] RFC 2277 - considerations, ned . freed
Re: [Ltru] RFC 2277 - considerations, Mark Davis
Re: [Ltru] RFC 2277 - considerations, John Cowan
Re: [Ltru] [psg.com #934] repertoire for descriptions inregistryentries, John Cowan
RE: [Ltru] RFC 2277 - considerations, Misha Wolf
Re: [Ltru] RFC 2277 - considerations, Randy Presuhn
RE: [Ltru] [psg.com #934] repertoire for descriptions inregistryentries, Peter Constable
Re: [Ltru] [psg.com #934] repertoire for descriptions inregistryentries, Marion Gunn
Re: [Ltru] [psg.com #934] repertoire for descriptions in registryentries, Mark Davis
Re: [Ltru] [psg.com #934] repertoire for descriptions inregistryentries, John Cowan
Re: [Ltru] [psg.com #934] repertoire for descriptions inregistryentries, Marion Gunn
Re: [Ltru] [psg.com #949] remove three-character limit in sections 2.2.2, 2.2.3 (of -00), Markus Scherer
Re: [Ltru] Re: [psg.com #946] use of both length and position toidentify subtag problematic, Marion Gunn
RE: [Ltru] [psg.com #943] number of subtags SHOULD be limited to four, Addison Phillips
RE: [Ltru] [psg.com #944] MAY a conformant implementation impose lengthconstraints?, Addison Phillips
RE: [Ltru] [psg.com #941] determining currency of registry versions, Addison Phillips
Re: [Ltru] [psg.com #934] repertoire for descriptions in registryentries, John Cowan
Re: [Ltru] Re: [psg.com #946] use of both length and position to identify subtag problematic, John Cowan
Re: [Ltru] [psg.com #934] repertoire for descriptions in registryentries, Mark Davis
Re: [Ltru] [psg.com #941] determining currency of registry versions, Mark Davis
Re: [Ltru] [psg.com #944] MAY a conformant implementation impose lengthconstraints?, Mark Davis
Re: [Ltru] [psg.com #942] clarify advice on use of subtags, Mark Davis
Re: [Ltru] [psg.com #946] use of both length and position to identifysubtag problematic, Mark Davis
Re: [Ltru] [psg.com #943] number of subtags SHOULD be limited to four, Mark Davis
Re: [Ltru] RFC 2277 - considerations, JFC (Jefsey) Morfin
[Ltru] Re: [psg.com #946] use of both length and position to identify subtag problematic, Frank Ellermann
[Ltru] [psg.com #949] remove three-character limit in sections 2.2.2, 2.2.3 (of -00), Randy Presuhn
[Ltru] [psg.com #948] deprecate two-letter language codes in favor of three-letter ones, Randy Presuhn
[Ltru] [psg.com #947] is set of possible primary languages too constrained?, Randy Presuhn
[Ltru] [psg.com #946] use of both length and position to identify subtag problematic, Randy Presuhn
[Ltru] [psg.com #945] use "." to separate subtags, Randy Presuhn
[Ltru] [psg.com #944] MAY a conformant implementation impose length constraints?, Randy Presuhn
[Ltru] [psg.com #943] number of subtags SHOULD be limited to four, Randy Presuhn
[Ltru] [psg.com #942] clarify advice on use of subtags, Randy Presuhn
[Ltru] [psg.com #941] determining currency of registry versions, Randy Presuhn
[Ltru] [psg.com #940] is the word "recognized" unclear in the syntax section?, Randy Presuhn
[Ltru] [psg.com #939] explain difference between tags and labels, Randy Presuhn
[Ltru] [psg.com #938] should introduction allude to intended bcp status?, Randy Presuhn
[Ltru] [psg.com #937] is the word "interchange" in the abstract unclear?, Randy Presuhn
[Ltru] [psg.com #936] is the phrase "information object" in the abstract unclear?, Randy Presuhn
[Ltru] [psg.com #935] is the word "indicate" in the abstract unclear?, Randy Presuhn
[Ltru] [psg.com #934] repertoire for descriptions in registry entries, Randy Presuhn
[Ltru] [psg.com #933] Java support, Randy Presuhn
[Ltru] Another batch of ltru tickets in RT, Randy Presuhn
Re: [Ltru] RFC 2277 - considerations, Randy Presuhn
Re: [Ltru] RFC 2277 - considerations, JFC (Jefsey) Morfin

May 09 2005

Re: [Ltru] RFC 2277 - considerations, Randy Presuhn
Re: [Ltru] RFC 2277 - considerations, JFC (Jefsey) Morfin
Re: [Ltru] RFC 2277 - considerations, ned . freed
Re: [Ltru] RFC 2277 - considerations, JFC (Jefsey) Morfin
Re: [Ltru] RFC 2277 - considerations, Martin Duerst

May 07 2005

[Ltru] RFC 2277 - considerations, JFC (Jefsey) Morfin

May 06 2005

Re: [Ltru] Re: John Cowan's substantive commentsondraft-ietf-ltru-registry-01, Marion Gunn
[Ltru] Registration forms (was: ...substantive comments on draft-ietf-ltru-registry...), Frank Ellermann
Re: [Ltru] Re: John Cowan's substantive comments ondraft-ietf-ltru-registry-01, Doug Ewell
RE: [Ltru] Re: John Cowan's substantive comments ondraft-ietf-ltr u-registry-01, JFC (Jefsey) Morfin

May 05 2005

Re: [Ltru] Re: John Cowan's substantive comments on draft-ietf-ltru-registry-01, John Cowan
RE: [Ltru] Re: John Cowan's substantive comments ondraft-ietf-ltru-registry-01, Addison Phillips
RE: [Ltru] Re: John Cowan's substantive comments ondraft-ietf-ltr u-registry-01, McDonald, Ira
RE: [Ltru] Re: John Cowan's substantive commentsondraft-ietf-ltru-registry-01, Peter Constable
Re: [Ltru] Re: John Cowan's substantive comments ondraft-ietf-ltru-registry-01, Mark Davis
RE: [Ltru] Re: John Cowan's substantive comments ondraft-ietf-ltru-registry-01, Addison Phillips
[Ltru] Re: John Cowan's substantive comments on draft-ietf-ltru-registry-01, Doug Ewell
[Ltru] Re: ISO/TC 46 mtgs in Dublin (Ireland) next week, Marion Gunn
[Ltru] ISO/TC 46 mtgs in Dublin (Ireland) next week, Marion Gunn

May 04 2005

Re: [Ltru] Re: Last registry for now, JFC (Jefsey) Morfin
Re: [Ltru] Re: Last registry for now, JFC (Jefsey) Morfin
RE: [Ltru] Re: Last registry for now, JFC (Jefsey) Morfin
Re: [Ltru] Re: Last registry for now, JFC (Jefsey) Morfin
Re: [Ltru] Re: regionalisation, JFC (Jefsey) Morfin
RE: [Ltru] Re: Last registry for now, Peter Constable
Re: [Ltru] Re: Last registry for now, Marion Gunn
[Ltru] Re: Last registry for now, Doug Ewell
Re: [Ltru] Re: Last registry for now, Randy Presuhn
[Ltru] Re: regionalisation, Doug Ewell
[Ltru] Re: Last registry for now, Frank Ellermann
RE: [Ltru] Re: Last registry for now, JFC (Jefsey) Morfin

May 03 2005

RE: [Ltru] Re: Last registry for now, Peter Constable
Re: [Ltru] Re: Last registry for now, John Cowan
Re: [Ltru] Re: Last registry for now, JFC (Jefsey) Morfin
[Ltru] Re: Last registry for now, John Cowan

Mail converted by MHonArc