ltru Discussion Archive - Thread Index

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

• [Ltru] Re: draft-ietf-ltru-matching-02, (continued)
  • [Ltru] Re: draft-ietf-ltru-matching-02, Frank Ellermann
  • RE: [Ltru] Re: draft-ietf-ltru-matching-02, Addison Phillips
    • [Ltru] Re: draft-ietf-ltru-matching-02, Frank Ellermann
• [Ltru] draft-ietf-ltru-matching-02, Frank Ellermann
  • Re: [Ltru] draft-ietf-ltru-matching-02, Mark Davis
    • [Ltru] Re: draft-ietf-ltru-matching-02, Frank Ellermann
      • Re: [Ltru] Re: draft-ietf-ltru-matching-02, Mark Davis
      • Re: [Ltru] Re: draft-ietf-ltru-matching-02, John.Cowan
      • [Ltru] Re: draft-ietf-ltru-matching-02, Frank Ellermann
  • <Possible follow-ups>
  • RE: [Ltru] draft-ietf-ltru-matching-02, Addison Phillips
    • [Ltru] Re: draft-ietf-ltru-matching-02, Frank Ellermann
• RE: [Ltru] [psg.com #1033] Written Spoken Signed, Peter Constable
  • Re: [Ltru] [psg.com #1033] Written Spoken Signed, Mark Davis
    • Re: [Ltru] [psg.com #1033] Written Spoken Signed, Martin Duerst
• [Ltru] discussion of position of script subtag, Peter Constable
  • Re: [Ltru] discussion of position of script subtag, Mark Davis
• RE: [Ltru] Re: FW: tags for written or spoken content, was Swissgerman, spoken, Addison Phillips
• RE: [Ltru] Re: FW: tags for written or spoken content, was Swiss german, spoken, McDonald, Ira
• [Ltru] Fw: Swiss german, spoken, Mark Davis
• [Ltru] Macrogeographical code 003, Doug Ewell
• [Ltru] FW: tags for written or spoken content, was Swiss german, spoken, McDonald, Ira
  • [Ltru] Re: FW: tags for written or spoken content, was Swiss german, spoken, Frank Ellermann
  • Re: [Ltru] FW: tags for written or spoken content, was Swiss german, spoken, Mark Davis
  • Re: [Ltru] [psg.com #1033] FW: tags for written or spoken content, was Swiss german, spoken, Randy Presuhn
  • <Possible follow-ups>
  • RE: [Ltru] FW: tags for written or spoken content, was Swiss german, spoken, Addison Phillips
• [Ltru] Spelling errors in draft -04, John.Cowan
• RE: [Ltru] Fw: Internet-Drafts Submission Cutoff Dates for the 63 rd IETF Meeting in Paris, France, McDonald, Ira
  • Re: [Ltru] Fw: Internet-Drafts Submission Cutoff Dates for the 63rd IETF Meeting in Paris, France, Randy Presuhn
• RE: [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jers ey, McDonald, Ira
• [Ltru] Fw: Internet-Drafts Submission Cutoff Dates for the 63rd IETF Meeting in Paris, France, Randy Presuhn
  • [Ltru] Re: Fw: Internet-Drafts Submission Cutoff Dates for the 63rd IETF Meeting in Paris, France, Frank Ellermann
    • Re: [Ltru] Re: Fw: Internet-Drafts Submission Cutoff Dates for the 63rd IETF Meeting in Paris, France, Randy Presuhn
      • [Ltru] Re: Fw: Internet-Drafts Submission Cutoff Dates for the 63rd IETF Meeting in Paris, France, Frank Ellermann
      • Re: [Ltru] Re: Fw: Internet-Drafts Submission Cutoff Dates for the63rd IETF Meeting in Paris, France, Martin Duerst
• [Ltru] I-D ACTION:draft-ietf-ltru-registry-04.txt, Internet-Drafts
• [Ltru] I-D ACTION:draft-ietf-ltru-matching-02.txt, Internet-Drafts
• RE: [Ltru] Re: #944 in draft -04, Addison Phillips
  • <Possible follow-ups>
  • RE: [Ltru] Re: #944 in draft -04, McDonald, Ira
    • [Ltru] Can we live with #944 as in draft -05?, Randy Presuhn
      • Re: [Ltru] Can we live with #944 as in draft -05? (yes, BUT), Martin Duerst
      • [Ltru] Re: Can we live with #944 as in draft -05?, Frank Ellermann
• [Ltru] Submission: LTRU Matching Draft 02, Addison Phillips
• RE: [Ltru] #944 in draft -04 (was: Confusing conformance language), Addison Phillips
  • [Ltru] Re: #944 in draft -04, Frank Ellermann
• [Ltru] Submission: LTRU Registry Draft 04, Addison Phillips
• [Ltru] Useful tool for i-d authors & editors, Randy Presuhn
• RE: [Ltru] Re: Confusing conformance language, Addison Phillips
  • Re: [Ltru] Re: Confusing conformance language, Randy Presuhn
  • [Ltru] Re: Confusing conformance language, Frank Ellermann
  • <Possible follow-ups>
  • RE: [Ltru] Re: Confusing conformance language, Addison Phillips
    • [Ltru] #944 in draft -04 (was: Confusing conformance language), Frank Ellermann
  • RE: [Ltru] Re: Confusing conformance language, Addison Phillips
  • RE: [Ltru] Re: Confusing conformance language, Addison Phillips
• RE: [Ltru] [psg.com #1027] apply ISO 11179 (metadata registry fra mework), McDonald, Ira
  • Re: [Ltru] [psg.com #1027] apply ISO 11179 (metadata registry framework), Randy Presuhn
    • Re: [Ltru] [psg.com #1027] apply ISO 11179 (metadata registry framework), Randy Presuhn
• [Ltru] Confusing conformance language, McDonald, Ira
  • RE: [Ltru] Confusing conformance language, Scott Hollenbeck
  • Re: [Ltru] Confusing conformance language, Randy Presuhn
    • Re: [Ltru] Confusing conformance language, Martin Duerst
  • <Possible follow-ups>
  • RE: [Ltru] Confusing conformance language, Addison Phillips
  • RE: [Ltru] Confusing conformance language, McDonald, Ira
  • RE: [Ltru] Confusing conformance language, Addison Phillips
  • RE: [Ltru] Confusing conformance language, McDonald, Ira
    • RE: [Ltru] Confusing conformance language, Scott Hollenbeck
      • [Ltru] Re: Confusing conformance language, Frank Ellermann
• [Ltru] Fw: An interesting sub-note for all of you using the xml tool for drafts, Randy Presuhn
• RE: [Ltru] Re: Roles, Addison Phillips
  • [Ltru] Re: Roles, Frank Ellermann
• RE: [Ltru] [psg.com #1027] apply ISO 11179 (metadata registryframework), Peter Constable
• [Ltru] Re: [psg.com #1027] apply ISO 11179 (metadata registry framework), Randy Presuhn
  • Re: [Ltru] [psg.com #1027] apply ISO 11179 (metadata registry framework), Randy Presuhn
  • RE: [Ltru] Re: [psg.com #1027] apply ISO 11179 (metadata registryframework), Debbie Garside
  • <Possible follow-ups>
  • [Ltru] Re: [psg.com #1027] apply ISO 11179 (metadata registry framework), Doug Ewell
• [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Randy Presuhn
  • Re: [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, John.Cowan
  • <Possible follow-ups>
  • [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Doug Ewell
    • [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Frank Ellermann
    • Re: [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, John.Cowan
      • [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Frank Ellermann
      • Re: [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Mark Davis
      • Re: [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Randy Presuhn
  • [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Doug Ewell
    • [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Frank Ellermann
      • Re: [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Randy Presuhn
      • [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Frank Ellermann
      • Re: [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Randy Presuhn
      • Re: [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, John.Cowan
    • Re: [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Randy Presuhn
    • Re: [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, John.Cowan
  • [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Doug Ewell
    • [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Frank Ellermann
      • Re: [Ltru] [psg.com #1026] what to do about Guernsey and Jersey, Randy Presuhn
      • [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Frank Ellermann
      • Re: [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Randy Presuhn
      • [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Frank Ellermann
  • [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Doug Ewell
    • Re: [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Randy Presuhn
  • [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Doug Ewell
  • RE: [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Peter Constable
  • [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Doug Ewell
  • RE: [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Addison Phillips
    • Re: [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Mark Davis
      • Re: [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Doug Ewell
      • [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Frank Ellermann
  • RE: [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Peter Constable
  • [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Doug Ewell
    • Re: [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Mark Davis
  • RE: [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Addison Phillips
    • [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Frank Ellermann
  • RE: [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Peter Constable
    • Re: [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Mark Davis
      • Re: [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, John.Cowan
  • RE: [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Addison Phillips
  • RE: [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Addison Phillips
  • RE: [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Addison Phillips
    • [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Frank Ellermann
  • [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Doug Ewell
  • RE: [Ltru] Re: [psg.com #1026] what to do about Guernsey and Jersey, Addison Phillips
• [Ltru] Re: Resolution of issue [psg.com #1016]: THREE extlangs?, Doug Ewell
  • Re: [Ltru] Re: Resolution of issue [psg.com #1016]: THREE extlangs?, Randy Presuhn
• [Ltru] Wrapping up the registry draft, Randy Presuhn
• [Ltru] Tag perversity text revised... (#944), Addison Phillips
  • Re: [Ltru] Tag perversity text revised... (#944), John.Cowan
    • Re: [Ltru] Tag perversity text revised... (#944), Randy Presuhn
      • Re: [Ltru] Tag perversity text revised... (#944), John.Cowan
    • Re: [Ltru] Tag perversity text revised... (#944), Mark Davis
  • Re: [Ltru] Tag perversity text revised... (#944), Mark Davis
  • <Possible follow-ups>
  • RE: [Ltru] Tag perversity text revised... (#944), Addison Phillips
    • Re: [Ltru] Tag perversity text revised... (#944), Mark Davis
  • RE: [Ltru] Tag perversity text revised... (#944), Addison Phillips
  • RE: [Ltru] Tag perversity text revised... (#944), Addison Phillips
  • RE: [Ltru] Tag perversity text revised... (#944), Addison Phillips
  • RE: [Ltru] Tag perversity text revised... (#944), Addison Phillips
    • Re: [Ltru] Tag perversity text revised... (#944), Randy Presuhn
  • RE: [Ltru] Tag perversity text revised... (#944), Addison Phillips
    • Re: [Ltru] Tag perversity text revised... (#944), Mark Davis
  • RE: [Ltru] Tag perversity text revised... (#944), Addison Phillips
    • Re: [Ltru] Tag perversity text revised... (#944), Randy Presuhn
      • Re: [Ltru] Tag perversity text revised... (#944), John.Cowan
    • [Ltru] Re: Tag perversity text revised... (#944), Frank Ellermann
      • [Ltru] Re: Tag perversity text revised... (#944), Frank Ellermann
    • Re: [Ltru] Tag perversity text revised... (#944), Mark Davis
      • Re: [Ltru] Tag perversity text revised... (#944), Mark Davis
    • Re: [Ltru] Tag perversity text revised... (#944), Erkki Kolehmainen
  • RE: [Ltru] Tag perversity text revised... (#944), Peter Constable
    • Re: [Ltru] Tag perversity text revised... (#944), Mark Davis
  • RE: [Ltru] Tag perversity text revised... (#944), Addison Phillips
  • RE: [Ltru] Tag perversity text revised... (#944), Peter Constable
  • RE: [Ltru] Tag perversity text revised... (#944), Addison Phillips
    • Re: [Ltru] Tag perversity text revised... (#944), Mark Davis
      • Re: [Ltru] Tag perversity text revised... (#944), Marion Gunn
  • RE: [Ltru] Tag perversity text revised... (#944), McDonald, Ira
  • RE: [Ltru] Tag perversity text revised... (#944), Addison Phillips
    • Re: [Ltru] Tag perversity text revised... (#944), Randy Presuhn
    • [Ltru] Re: Tag perversity text revised... (#944), Frank Ellermann
• RE: [Ltru] [psg.com #893] support incremental updates of registryshadows, Addison Phillips
  • Re: [Ltru] [psg.com #893] support incremental updates of registry shadows, Randy Presuhn
• [Ltru] Preferred-Value added to registry, Doug Ewell
  • [Ltru] Re: Preferred-Value added to registry, Frank Ellermann
    • [Ltru] Re: Preferred-Value added to registry, Frank Ellermann
      • Re: [Ltru] Re: Preferred-Value added to registry, Martin Duerst
• [Ltru] Re: The most perverse tag, plus a comment on fine-tuning, Doug Ewell
• [Ltru] Re: The most perverse tag, Doug Ewell
  • Re: [Ltru] Re: The most perverse tag, Randy Presuhn
    • [Ltru] Re: The most perverse tag, Frank Ellermann
  • <Possible follow-ups>
  • [Ltru] Re: The most perverse tag, Doug Ewell
    • [Ltru] Re: The most perverse tag, Frank Ellermann
      • Re: [Ltru] Re: The most perverse tag, Randy Presuhn
      • [Ltru] Re: The most perverse tag, Frank Ellermann
  • RE: [Ltru] Re: The most perverse tag, Addison Phillips
  • RE: [Ltru] Re: The most perverse tag, McDonald, Ira
    • [Ltru] Re: The most perverse tag, Frank Ellermann
      • Re: [Ltru] Re: The most perverse tag, Mark Davis
  • RE: [Ltru] Re: The most perverse tag, Addison Phillips
  • [Ltru] Re: The most perverse tag, Doug Ewell
  • RE: [Ltru] Re: The most perverse tag, Peter Constable
    • Re: [Ltru] Re: The most perverse tag, John.Cowan
  • RE: [Ltru] Re: The most perverse tag, Addison Phillips
    • Re: [Ltru] Re: The most perverse tag, Mark Davis
• [Ltru] The most perverse tag, Frank Ellermann
  • <Possible follow-ups>
  • RE: [Ltru] The most perverse tag, Addison Phillips
• [Ltru] I-D ACTION:draft-ietf-ltru-registry-03.txt, Internet-Drafts
• [Ltru] I-D ACTION:draft-ietf-ltru-matching-01.txt, Internet-Drafts
• [Ltru] Re: items addressed by current editor's draft, Doug Ewell
  • Re: [Ltru] [psg.com #1019] move redundant tags from draft registry to an appendix, Randy Presuhn
• [Ltru] ltru wg submission: draft-ietf-ltru-matching-01, Addison Phillips
• [Ltru] ltru wg submission: draft-ietf-ltru-registry-03, Addison Phillips
• [Ltru] items addressed by current editor's draft, Addison Phillips
  • [Ltru] Re: items addressed by current editor's draft, Frank Ellermann
  • Re: [Ltru] items addressed by current editor's draft, Randy Presuhn
    • [Ltru] #892 640 KB (was: items addressed by current editor's draft), Frank Ellermann
      • [Ltru] Roles, Randy Presuhn
      • [Ltru] Re: Roles, Frank Ellermann
  • <Possible follow-ups>
  • RE: [Ltru] items addressed by current editor's draft, Peter Constable
    • [Ltru] Resolution of issue [psg.com #1016]: THREE extlangs?, Randy Presuhn
  • RE: [Ltru] items addressed by current editor's draft, Addison Phillips
• [Ltru] Re: [psg.com #1018] Add Macro-Language field, Doug Ewell
  • <Possible follow-ups>
  • [Ltru] Re: [psg.com #1018] Add Macro-Language field, Doug Ewell
  • RE: [Ltru] Re: [psg.com #1018] Add Macro-Language field, Addison Phillips
  • RE: [Ltru] Re: [psg.com #1018] Add Macro-Language field, Addison Phillips
    • Re: [Ltru] Re: [psg.com #1018] Add Macro-Language field, John Cowan
    • Re: [Ltru] Re: [psg.com #1018] Add Macro-Language field, Randy Presuhn
  • RE: [Ltru] Re: [psg.com #1018] Add Macro-Language field, Addison Phillips
  • [Ltru] Re: [psg.com #1018] Add Macro-Language field, Doug Ewell
    • Re: [Ltru] Re: [psg.com #1018] Add Macro-Language field, Randy Presuhn
• RE: [Ltru] Re: expectation of support for automated reading of registry, Addison Phillips
• RE: [Ltru] [psg.com #1019] move redundant tags from draft registry toan appendix, Addison Phillips
• [Ltru] [psg.com #1020] stable forever != canonical forever, Randy Presuhn
  • Re: [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] Re: [psg.com #1018] Add Macro-Language field, Frank Ellermann
    • Re: [Ltru] Re: [psg.com #1018] Add Macro-Language field, Randy Presuhn
  • <Possible follow-ups>
  • RE: [Ltru] [psg.com #1018] Add Macro-Language field, Addison Phillips
    • Re: [Ltru] [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] [psg.com #1018] Add Macro-Language field, John Cowan
      • RE: [Ltru] [psg.com #1018] Add Macro-Language field, Debbie Garside
  • RE: [Ltru] [psg.com #1018] Add Macro-Language field, McDonald, Ira
  • RE: [Ltru] [psg.com #1018] Add Macro-Language field, Addison Phillips
    • Re: [Ltru] [psg.com #1018] Add Macro-Language field, John Cowan
  • RE: [Ltru] [psg.com #1018] Add Macro-Language field, Peter Constable
    • Re: [Ltru] [psg.com #1018] Add Macro-Language field, Mark Davis
  • RE: [Ltru] [psg.com #1018] Add Macro-Language field, Addison Phillips
    • [Ltru] Re: [psg.com #1018] Add Macro-Language field, Frank Ellermann
  • RE: [Ltru] [psg.com #1018] Add Macro-Language field, Addison Phillips
    • Re: [Ltru] [psg.com #1018] Add Macro-Language field, John Cowan
      • [Ltru] Re: [psg.com #1018] Add Macro-Language field, Frank Ellermann
• [Ltru] [psg.com #1017] Add Required-Prefix field, Randy Presuhn
  • Re: [Ltru] [psg.com #1017] Add Required-Prefix field, Randy Presuhn
• RE: [Ltru] Re: [psg.com #965] expectation of support for automatedreading of registry, Addison Phillips
  • [Ltru] Re: [psg.com #944] MAY a conformant implementation impose length constraints, Randy Presuhn
    • [Ltru] Meta (was: MAY a conformant implementation impose length constraints), Frank Ellermann
      • Re: [Ltru] Meta, Randy Presuhn
      • [Ltru] Re: Meta, Frank Ellermann
  • [Ltru] Re: expectation of support for automated reading of registry, Frank Ellermann
• RE: [Ltru] Re: [psg.com #944] MAY a conformant implementation imp oselength constraints?, McDonald, Ira
  • [Ltru] Re: [psg.com #965] expectation of support for automated reading of registry, Randy Presuhn
  • <Possible follow-ups>
  • 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] [psg.com #944] MAY a conformant implementation impose length constraints?, Randy Presuhn
  • <Possible follow-ups>
  • RE: [Ltru] Re: [psg.com #944] MAY a conformant implementation imposelength constraints?, Addison Phillips
  • RE: [Ltru] Re: [psg.com #944] MAY a conformant implementation imposelength constraints?, Addison Phillips
    • [Ltru] Re: [psg.com #944] MAY a conformant implementation imposelength constraints?, Frank Ellermann
  • RE: [Ltru] Re: [psg.com #944] MAY a conformant implementation imposelength constraints?, Peter Constable
• RE: [Ltru] Re: [psg.com #944] MAY a conformant implementation imp ose length constraints?, McDonald, Ira
• [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 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
  • <Possible follow-ups>
  • RE: [Ltru] [psg.com #944] MAY a conformant implementation imposelength constraints?, Addison Phillips
• RE: [Ltru] [psg.com #875] should initial registry contents be madeinto an internet-draft?, Addison Phillips
• RE: [Ltru] extlang again (was: [psg.com #1011] add suppress-region), Peter Constable
  • [Ltru] Re: extlang again, Frank Ellermann
    • Re: [Ltru] Re: extlang again, John Cowan
      • [Ltru] Re: extlang again, Frank Ellermann
      • Re: [Ltru] Re: extlang again, John Cowan
      • [Ltru] Re: extlang again, Frank Ellermann
• [Ltru] New registry to reflect draft-03 changes, Doug Ewell
• [Ltru] Re: extlang again (was: [psg.com #1011] add suppress-region), Doug Ewell
  • [Ltru] Re: extlang again, Frank Ellermann
    • Re: [Ltru] Re: extlang again, John Cowan
• [Ltru] Re: extlang again, Doug Ewell
  • <Possible follow-ups>
  • RE: [Ltru] Re: extlang again, Peter Constable
    • [Ltru] Re: extlang again, Frank Ellermann
  • [Ltru] Re: extlang again, John Cowan
    • [Ltru] [psg.com #1016] restrict the maximum number of extlang subtags to five, Randy Presuhn
• [Ltru] Re: [psg.com #966] remove something from security considerations, Doug Ewell
  • [Ltru] Re: [psg.com #966] remove something from security considerations, Frank Ellermann
• [Ltru] Re: last response, Doug Ewell
• [Ltru] Re: [psg.com #1014] make scope of applicability universal, Doug Ewell
• [Ltru] Re: [psg.com #1011] add suppress-region, Doug Ewell
  • 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 #1011] add suppress-region, Frank Ellermann
      • Re: [Ltru] Re: [psg.com #1011] add suppress-region, John Cowan
      • [Ltru] extlang again (was: [psg.com #1011] add suppress-region), Frank Ellermann
      • Re: [Ltru] extlang again (was: [psg.com #1011] add suppress-region), John Cowan
      • [Ltru] Re: extlang again, Frank Ellermann
      • Re: [Ltru] Re: extlang again, John Cowan
  • <Possible follow-ups>
  • [Ltru] Re: [psg.com #1011] add suppress-region, Doug Ewell
    • [Ltru] extlang again (was: [psg.com #1011] add suppress-region), Frank Ellermann
    • Re: [Ltru] [psg.com #1011] add suppress-region, Randy Presuhn
• Re: [Ltru] [psg.com #966] remove something from security considerations, Doug Ewell
  • [Ltru] Re: [psg.com #966] remove something from security considerations, Frank Ellermann
• [Ltru] [psg.com #1014] make scope of applicability universal, Randy Presuhn
• [Ltru] three more closed issues: 1012, 1013, and 1015, Randy Presuhn
• RE: [Ltru] [psg.com #1011] add suppress-region, Peter Constable
  • Re: [Ltru] [psg.com #1011] add suppress-region, Randy Presuhn
• [Ltru] use of region subtags, Peter Constable
  • <Possible follow-ups>
  • RE: [Ltru] use of region subtags, Addison Phillips
    • Re: [Ltru] use of region subtags, John Cowan
      • [Ltru] [psg.com #1011] add suppress-region, Randy Presuhn
    • Message not available
      • RE: [Ltru] use of region subtags, Martin Duerst
  • RE: [Ltru] use of region subtags, Addison Phillips
• [Ltru] [psg.com #1009] generic variant subtags, Randy Presuhn
• RE: [Ltru] last response (was: character set considerations materialis contradictory), Peter Constable
  • [Ltru] Re: last response, Frank Ellermann
• [Ltru] On the records (was Editorial error in BNF), JFC (Jefsey) Morfin
• [Ltru] Re: Editorial error in BNF, Doug Ewell
• RE: [Ltru] [psg.com #967] addresshomographissuesinsecurityconside rations, McDonald, Ira
• RE: [Ltru] [psg.com #967] addresshomographissuesinsecurityconsiderations, Addison Phillips
  • Re: [Ltru] [psg.com #967]addresshomographissuesinsecurityconsiderations, Mark Davis
    • [Ltru] Re: [psg.com#967]addresshomographissuesinsecurityconsiderations, Frank Ellermann
      • Re: [Ltru] [psg.com#967] address homograph issues in security considerations, Randy Presuhn
• [Ltru] issue resolutions 999 & 1000, Randy Presuhn
• [Ltru] Re: Fix for ambiguous conformance requirements, Doug Ewell
  • Re: [Ltru] Re: Fix for ambiguous conformance requirements, Randy Presuhn
    • [Ltru] Re: Fix for ambiguous conformance requirements, Frank Ellermann
      • Re: [Ltru] Re: Fix for ambiguous conformance requirements, Martin Duerst
      • [Ltru] [psg.com #1010] conformance terminology, Randy Presuhn
  • <Possible follow-ups>
  • [Ltru] Re: Fix for ambiguous conformance requirements, Doug Ewell
    • Re: [Ltru] Re: Fix for ambiguous conformance requirements, Randy Presuhn
  • RE: [Ltru] Re: Fix for ambiguous conformance requirements, Addison Phillips
  • RE: [Ltru] Re: Fix for ambiguous conformance requirements, Addison Phillips
• [Ltru] Editorial error in BNF, John Cowan
  • <Possible follow-ups>
  • RE: [Ltru] Editorial error in BNF, Addison Phillips
    • Re: [Ltru] Editorial error in BNF, Randy Presuhn
      • [Ltru] Re: Editorial error in BNF, Frank Ellermann
    • Re: [Ltru] Editorial error in BNF, Mark Davis
  • RE: [Ltru] Editorial error in BNF, Peter Constable
  • RE: [Ltru] Editorial error in BNF, Peter Constable
  • RE: [Ltru] Editorial error in BNF, Addison Phillips
    • Re: [Ltru] Editorial error in BNF, John Cowan
  • RE: [Ltru] Editorial error in BNF, Peter Constable
  • RE: [Ltru] Editorial error in BNF, McDonald, Ira
    • Message not available
      • RE: [Ltru] Editorial error in BNF, JFC (Jefsey) Morfin
  • RE: [Ltru] Editorial error in BNF, Addison Phillips
  • RE: [Ltru] Editorial error in BNF, Peter Constable
    • Re: [Ltru] Editorial error in BNF, Randy Presuhn
      • RE: [Ltru] Editorial error in BNF, Debbie Garside
      • [Ltru] [psg.com #1007] future-proofing wrt anticiapted ISO 639-6, Randy Presuhn
• RE: [Ltru] [psg.com #967] address homographissuesinsecurityconsiderations, Addison Phillips
  • Message not available
    • RE: [Ltru] [psg.com #967] addresshomographissuesinsecurityconsiderations, Martin Duerst
• [Ltru] draft of draft-03 posted..., Addison Phillips
• [Ltru] Fix for ambiguous conformance requirements, McDonald, Ira
  • <Possible follow-ups>
  • RE: [Ltru] Fix for ambiguous conformance requirements, Addison Phillips
  • RE: [Ltru] Fix for ambiguous conformance requirements, McDonald, Ira
  • RE: [Ltru] Fix for ambiguous conformance requirements, Addison Phillips
    • Re: [Ltru] Fix for ambiguous conformance requirements, Mark Davis
  • RE: [Ltru] Fix for ambiguous conformance requirements, McDonald, Ira
    • Re: [Ltru] Fix for ambiguous conformance requirements, Mark Davis
• [Ltru] Re: [psg.com #967] address homograph issues in security considerations, Doug Ewell
  • <Possible follow-ups>
  • [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] Tickets [psg.com #993] through [psg.com #996], Randy Presuhn
• [Ltru] I-D ACTION:draft-ietf-ltru-registry-02.txt, Internet-Drafts
• [Ltru] UNSD adds two new codes, Doug Ewell
  • [Ltru] Re: UNSD adds two new codes, Frank Ellermann
  • Re: [Ltru] UNSD adds two new codes, John Cowan
• [Ltru] Submission: LTRU Registry Draft 02, Addison Phillips
• [Ltru] while we're housekeeping..., Addison Phillips
  • Re: [Ltru] while we're housekeeping..., Randy Presuhn
• RE: [Ltru] [psg.com #992] provide way to alias language-variantcombination to a lang-extlang combination, 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-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] Schizophrenic treatment of grandfathered tags, John Cowan
  • [Ltru] [psg.com #998] fate of grandfathered tags when subtags registered or replacements found, Randy Presuhn
    • Re: [Ltru] [psg.com #998] fate of grandfathered tags when subtags registered or replacements found, Randy Presuhn
• RE: [Ltru] Re: [psg.com #954] all aliases must be equally support ed, McDonald, Ira
  • Re: [Ltru] [psg.com #954] all aliases must be equally supported, Randy Presuhn
  • [Ltru] Re: [psg.com #954] all aliases must be equally support ed, Frank Ellermann
  • <Possible follow-ups>
  • RE: [Ltru] Re: [psg.com #954] all aliases must be equally support ed, Misha Wolf
  • 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
    • [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 support ed, Mark Davis
      • 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 support ed, Addison Phillips
  • 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] [psg.com #954] all aliases must be equally supported, Randy Presuhn
    • [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, Addison Phillips
  • 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] Re: [psg.com #954] all aliases must be equally support ed, Mark Davis
      • [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, Addison Phillips
    • Re: [Ltru] Re: [psg.com #954] all aliases must be equally support ed, Randy Presuhn
• [Ltru] completed milestone for ltru charter, Randy Presuhn
• [Ltru] Re: grandfathered tags and generative capacity, Doug Ewell
  • [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, John Cowan
      • [Ltru] Re: [psg.com #992] provide way to alias language-variant combination to a lang-extlang combination, Frank Ellermann
• [Ltru] Re: [psg.com #985] Specify case rules for canonical tags, Doug Ewell
  • Re: [Ltru] Re: [psg.com #985] Specify case rules for canonical tags, Randy Presuhn
  • <Possible follow-ups>
  • [Ltru] Re: [psg.com #985] Specify case rules for canonical tags, Doug Ewell
    • [Ltru] Re: [psg.com #985] Specify case rules for canonical tags, Frank Ellermann
• [Ltru] grandfathered tags and generative capacity, Peter Constable
  • Re: [Ltru] grandfathered tags and generative capacity, John Cowan
• [Ltru] RE: Some comments on draft-ietf-ltru-matching-00, Addison Phillips
  • [Ltru] Re: Some comments on draft-ietf-ltru-matching-00, Frank Ellermann
  • Re: [Ltru] RE: Some comments on draft-ietf-ltru-matching-00, Randy Presuhn
• [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
• [Ltru] [psg.com #985] Specify case rules for canonical tags, Randy Presuhn
  • [Ltru] Re: [psg.com #985] Specify case rules for canonical tags, Frank Ellermann
    • Re: [Ltru] Re: [psg.com #985] Specify case rules for canonical tags, Randy Presuhn
      • [Ltru] Re: [psg.com #985] Specify case rules for canonical tags, Frank Ellermann
  • Re: [Ltru] [psg.com #985] Specify case rules for canonical tags, John Cowan
  • <Possible follow-ups>
  • 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, John Cowan
  • RE: [Ltru] [psg.com #985] Specify case rules for canonical tags, Addison Phillips
• [Ltru] Issues [psg.com #982] through [psg.com #991], Randy Presuhn
  • Re: [Ltru] Issues [psg.com #982] through [psg.com #991], Mark Davis
    • Re: [Ltru] Issues [psg.com #982] through [psg.com #991], Randy Presuhn
• [Ltru] Re: [WG I-D Submission] draft-ietf-ltru-matching-00, Randy Presuhn
  • Message not available
    • [Ltru] Re: [WG I-D Submission] draft-ietf-ltru-matching-00, Martin Duerst
• [Ltru] [WG I-D Submission] draft-ietf-ltru-matching-00, Addison Phillips
• RE: [Ltru] Re: Open points before -02, Addison Phillips
  • [Ltru] [psg.com #997[ simplify ABNF by merging field and record-jar definitions, Randy Presuhn
  • <Possible follow-ups>
  • [Ltru] Re: Open points before -02, Doug Ewell
    • Re: [Ltru] Open points before -02, Randy Presuhn
      • Re: [Ltru] Open points before -02, John Cowan
    • [Ltru] Re: Open points before -02, Frank Ellermann
  • [Ltru] Re: Open points before -02, Doug Ewell
• [Ltru] New version of matching draft..., Addison Phillips
  • Re: [Ltru] New version of matching draft..., Randy Presuhn
  • <Possible follow-ups>
  • RE: [Ltru] New version of matching draft..., Addison Phillips
    • Re: [Ltru] New version of matching draft..., Randy Presuhn
• [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
• [Ltru] ltru issues 972-981, Randy Presuhn
• RE: [Ltru] [psg.com #967] address homograph issuesinsecurityconsi derations, McDonald, Ira
• RE: [Ltru] [psg.com #967] address homograph issues insecuritycons iderations, McDonald, Ira
• RE: [Ltru] [psg.com #967] address homograph issuesinsecurityconsiderations, Peter Constable
  • <Possible follow-ups>
  • RE: [Ltru] [psg.com #967] address homograph issuesinsecurityconsiderations, Addison Phillips
  • RE: [Ltru] [psg.com #967] address homograph issuesinsecurityconsiderations, Addison Phillips
    • Re: [Ltru] [psg.com #967] address homograph issues in security considerations, Randy Presuhn
      • Re: [Ltru] [psg.com #967] address homograph issues in security considerations, John Cowan
• RE: [Ltru] [psg.com #967] address homograph issues insecurityconsiderations, Misha Wolf
  • [Ltru] Re: [psg.com #967] address homograph issues insecurityconsiderations, Frank Ellermann
  • <Possible follow-ups>
  • RE: [Ltru] [psg.com #967] address homograph issues insecurityconsiderations, Peter Constable
  • RE: [Ltru] [psg.com #967] address homograph issues insecurityconsiderations, Addison Phillips
    • Re: [Ltru] [psg.com #967] address homograph issuesinsecurityconsiderations, Randy Presuhn
    • Message not available
      • RE: [Ltru] [psg.com #967] address homograph issues insecurityconsiderations, JFC (Jefsey) Morfin
      • Re: [Ltru] [psg.com #967] address homograph issues in security considerations, Randy Presuhn
      • [Ltru] Re: [psg.com #967] address homograph issues in security considerations, Frank Ellermann
• RE: [Ltru] [psg.com #969]character set considerations material iscontradictory, Peter Constable
  • Message not available
    • [Ltru] sad and afflicting (was [psg.com #969]character set considerations material is contradictory), JFC (Jefsey) Morfin
  • Re: [Ltru] [psg.com #969] character set considerations materialis contradictory, Randy Presuhn
    • [Ltru] last response (was: character set considerations materialis contradictory), JFC (Jefsey) Morfin
      • Re: [Ltru] [psg.com #969] character set considerations, Randy Presuhn
      • [Ltru] Re: last response, Randy Presuhn
• 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] [psg.com #967] address homograph issues insecurityconsiderations, Randy Presuhn
  • <Possible follow-ups>
  • RE: [Ltru] [psg.com #967] address homograph issues in securityconsiderations, Addison Phillips
  • RE: [Ltru] [psg.com #967] address homograph issues in securityconsiderations, Peter Constable
• [Ltru] [psg.com #970] add reference to xml schema version 1.0, Randy Presuhn
  • [Ltru] Re: [psg.com #970] add reference to xml schema version 1.0, Frank Ellermann
• [Ltru] [psg.com #969]character set considerations material is contradictory, Randy Presuhn
  • [Ltru] Re: [psg.com #969]character set considerations material is contradictory, Frank Ellermann
• [Ltru] [psg.com #968] load on IANA server by applications, Randy Presuhn
  • Re: [Ltru] [psg.com #968] load on IANA server by applications, Randy Presuhn
    • Re: [Ltru] [psg.com #968] load on IANA server by applications, John.Cowan
      • Re: [Ltru] [psg.com #968] load on IANA server by applications, Randy Presuhn
    • Re: [Ltru] [psg.com #968] load on IANA server by applications, Mark Davis
  • <Possible follow-ups>
  • RE: [Ltru] [psg.com #968] load on IANA server by applications, Addison Phillips
    • Re: [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
  • Re: [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
  • <Possible follow-ups>
  • RE: [Ltru] [psg.com #964] section 3.4 of -00 is hard to understand, Addison Phillips
    • Message not available
      • RE: [Ltru] [psg.com #964] section 3.4 of -00 is hard to understand, JFC (Jefsey) Morfin
  • RE: [Ltru] [psg.com #964] section 3.4 of -00 is hard to understand, Peter Constable
  • RE: [Ltru] [psg.com #964] section 3.4 of -00 is hard to understand, Addison Phillips
• [Ltru] [psg.com #963] section on registration procedure is confusing, Randy Presuhn
  • Re: [Ltru] [psg.com #963] section on registration procedure is confusing, John Cowan
• [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
• RE: xml2rfc category (was RE: [Ltru] Re: [psg.com #938] shouldintroduction alludetointendedbcp status?), Addison Phillips
  • RE: xml2rfc category (was RE: [Ltru] Re: [psg.com #938] shouldintroduction alludetointendedbcp 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 tointendedbcp status?, Scott Hollenbeck
    • [Ltru] Re: [psg.com #938] should introduction allude tointendedbcp status?, Frank Ellermann
      • xml2rfc category (was RE: [Ltru] Re: [psg.com #938] should introduction alludetointendedbcp status?), Scott Hollenbeck
      • Re: xml2rfc category (was RE: [Ltru] Re: [psg.com #938] should introduction alludetointendedbcp status?), Frank Ellermann
    • RE: [Ltru] Re: [psg.com #938] should introduction allude tointendedbcp status?, JFC (Jefsey) Morfin
• RE: [Ltru] Re: [psg.com #938] should introduction allude to intendedbcp status?, Addison Phillips
  • RE: [Ltru] Re: [psg.com #938] should introduction allude tointendedbcp status?, Scott Hollenbeck
  • Re: [Ltru] Re: [psg.com #938] should introduction allude to intended bcp status?, Randy Presuhn
  • <Possible follow-ups>
  • 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] [psg.com #952] how to determine whether an ISO 639 registration request has been processed?, Randy Presuhn
• [Ltru] [psg.com #960] use ITU E.164 calling codes instead of ISO 3166 country codes, Randy Presuhn
  • Re: [Ltru] [psg.com #960] use ITU E.164 calling codes instead of ISO 3166 country codes, JFC (Jefsey) Morfin
    • Re: [Ltru] [psg.com #960] use ITU E.164 calling codes instead of ISO 3166 country codes, Randy Presuhn