Enum Discussion Archive - Thread Index

• [Enum] More Experienced, lconroy
• [Enum] I-D ACTION:draft-ietf-enum-experiences-03.txt, Internet-Drafts
• [Enum] [Fwd: I-D submission: draft-lind-infrastructure-enum-reqs-01], Richard Shockey
  • RE: [Enum] [Fwd: I-D submission: draft-lind-infrastructure-enum-reqs-01], Douglas Ranalli
• [Enum] FW: ENUM WG I-D: draft-ietf-enum-pstn-00.txt, Livingood, Jason
• [Enum] Current Proposed Agenda for IETF 64, Richard Shockey
  • <Possible follow-ups>
  • RE: [Enum] Current Proposed Agenda for IETF 64, Pfautz, Penn L, NEO
• [Enum] "straw-person" terminology draft posted, David Meyer
• RE: [Enum] ENUM Working Group Last call on IANA Registration for Enumservice Voice, Livingood, Jason
  • RE: [Enum] ENUM Working Group Last call on IANA Registration for Enumservice Voice, Bernie Hoeneisen
  • <Possible follow-ups>
  • RE: [Enum] ENUM Working Group Last call on IANA Registration for Enumservice Voice, Livingood, Jason
    • Re: [Enum] ENUM Working Group Last call on IANA Registration for Enumservice Voice, Richard Shockey
    • Re: [Enum] ENUM Working Group Last call on IANA Registration for Enumservice Voice, Alexander Mayrhofer
      • Re: [Enum] ENUM Working Group Last call on IANA Registration for Enumservice Voice, Michael Haberler
  • RE: [Enum] ENUM Working Group Last call on IANA Registration for Enumservice Voice, Brandner, Rudolf
  • Re: [Enum] ENUM Working Group Last call on IANA Registration for Enumservice Voice, Allison Mankin
• [Enum] Last Call: 'An ENUM Registry Type for the Internet Registry Information Service' to Proposed Standard, The IESG
• [Enum] ENUM WG RECHARTER : My initial proposal V.01, Richard Shockey
  • <Possible follow-ups>
  • RE: [Enum] ENUM WG RECHARTER : My initial proposal V.01, James McEachern
    • Re: [Enum] ENUM WG RECHARTER : My initial proposal V.01, Richard Shockey
• [Enum] ENUM WG RECHARTER : My initial proposal, Richard Shockey
  • <Possible follow-ups>
  • RE: [Enum] ENUM WG RECHARTER : My initial proposal, Pfautz, Penn L, NEO
• [Enum] IETF 43 Vancouver Agenda Items, Richard Shockey
• [Enum] voipeer agenda/charter uploaded, David Meyer
  • RE: [Enum] voipeer agenda/charter uploaded, Peter Williams
  • <Possible follow-ups>
  • Re: [Enum] voipeer agenda/charter uploaded, Stastny Richard
    • Re: [Enum] voipeer agenda/charter uploaded, Peter Williams
      • Re: [Enum] voipeer agenda/charter uploaded, David Meyer
      • Re: [Enum] voipeer agenda/charter uploaded, Christian de Larrinaga
      • Re: [Enum] voipeer agenda/charter uploaded, Peter Williams
  • Re: [Enum] voipeer agenda/charter uploaded, Stastny Richard
    • Re: [Enum] voipeer agenda/charter uploaded, David Meyer
  • RE: [Enum] voipeer agenda/charter uploaded, Stastny Richard
    • Re: [Enum] voipeer agenda/charter uploaded, Christian de Larrinaga
      • Re: [Enum] voipeer agenda/charter uploaded, Peter Williams
      • Re: [Enum] voipeer agenda/charter uploaded, David Meyer
      • Re: [Enum] voipeer agenda/charter uploaded, Christian de Larrinaga
  • Re: [Enum] voipeer agenda/charter uploaded, Stastny Richard
  • Re: [Enum] voipeer agenda/charter uploaded, Stastny Richard
• [Enum] Validation of Carriers, Stastny Richard
  • Re: [Enum] Validation of Carriers, Richard Shockey
  • <Possible follow-ups>
  • RE: [Enum] Validation of Carriers, Pfautz, Penn L, NEO
    • Re: [Enum] Validation of Carriers, Alexander Mayrhofer
• [Enum] I-D ACTION:draft-ietf-enum-validation-token-00.txt, Internet-Drafts
  • RE: [Enum] I-D ACTION:draft-ietf-enum-validation-token-00.txt, Peter Williams
    • Re: [Enum] I-D ACTION:draft-ietf-enum-validation-token-00.txt, Otmar Lendl
      • Re: [Enum] I-D ACTION:draft-ietf-enum-validation-token-00.txt, Peter Williams
      • Re: [Enum] I-D ACTION:draft-ietf-enum-validation-token-00.txt, Otmar Lendl
• [Enum] [Fwd: I-D ACTION:draft-conroy-enum-edns0-00.txt], Richard Shockey
• [Enum] A proposal for Carrier ENUM, Stastny Richard
  • Re: [Enum] A proposal for Carrier ENUM, Richard Shockey
  • <Possible follow-ups>
  • RE: [Enum] A proposal for Carrier ENUM, Stastny Richard
  • RE: [Enum] A proposal for Carrier ENUM, Antoin Verschuren
  • RE: [Enum] A proposal for Carrier ENUM, Stastny Richard
  • RE: [Enum] A proposal for Carrier ENUM, Nieminen Klaus
  • RE: [Enum] A proposal for Carrier ENUM, Michael Hammer \(mhammer\)
  • RE: [Enum] A proposal for Carrier ENUM, Pfautz, Penn L, NEO
    • Re: [Enum] A proposal for Carrier ENUM, Otmar Lendl
      • Re: [Enum] A proposal for Carrier ENUM, Clive D.W. Feather
    • Re: [Enum] A proposal for Carrier ENUM, Clive D.W. Feather
  • RE: [Enum] A proposal for Carrier ENUM, Nieminen Klaus
    • Re: [Enum] A proposal for Carrier ENUM, Richard Shockey
      • Re: [Enum] A proposal for Carrier ENUM - Oops, Richard Shockey
      • Re: [Enum] A proposal for Carrier ENUM - Oops, Michael Haberler
  • RE: [Enum] A proposal for Carrier ENUM, Nieminen Klaus
  • RE: [Enum] A proposal for Carrier ENUM, Pfautz, Penn L, NEO
    • Re: [Enum] A proposal for Carrier ENUM, Otmar Lendl
      • Re: [Enum] A proposal for Carrier ENUM, Richard Shockey
  • Re: [Enum] A proposal for Carrier ENUM, Rosbotham, Paul
  • RE: [Enum] A proposal for Carrier ENUM, Stastny Richard
  • RE: [Enum] A proposal for Carrier ENUM, Stastny Richard
  • Re: [Enum] A proposal for Carrier ENUM, Lupton, Ronan
    • Re: [Enum] A proposal for Carrier ENUM, Richard Shockey
  • Re: [Enum] A proposal for Carrier ENUM, james . f . baskin
  • RE: [Enum] A proposal for Carrier ENUM, Rosbotham, Paul
  • RE: [Enum] A proposal for Carrier ENUM, James McEachern
  • RE: [Enum] A proposal for Carrier ENUM, Rosbotham, Paul
  • RE: [Enum] A proposal for Carrier ENUM, James McEachern
• RE: [Enum] My personal definitions, Nieminen Klaus
• [Enum] This is notth final agenda .., Richard Shockey
• [Enum] [Fwd: Internet-Drafts Submission Cutoff Dates for the 64th IETF Meeting in Vancouver, British Columbia, Canada], Richard Shockey
• [Enum] How to provision wildcard NAPTRs using RFC4114?, Alexander Mayrhofer
  • <Possible follow-ups>
  • RE: [Enum] How to provision wildcard NAPTRs using RFC4114?, Hollenbeck, Scott
• Re: [voipeer] Re: [Enum] What is a Carrier and who has the right to enternumbers in Carrier ENUM?, Stastny Richard
  • <Possible follow-ups>
  • RE: [voipeer] Re: [Enum] What is a Carrier and who has the right to enternumbers in Carrier ENUM?, Antoin Verschuren
    • [Enum] My personal definitions, Richard Shockey
      • RE: [Enum] My personal definitions, Peter Williams
      • RE: [Enum] My personal definitions, Michael Haberler
      • RE: [Enum] My personal definitions, Peter Williams
      • Re: [Enum] My personal definitions, Christian de Larrinaga
• RE: [voipeer] Re: [Enum] What is a Carrier and who has the right to enternumbers in Carrier ENUM?, Vince Humphries
  • <Possible follow-ups>
  • RE: [voipeer] Re: [Enum] What is a Carrier and who has the right to enternumbers in Carrier ENUM?, Vince Humphries
• Re: [Enum] What is a Carrier and who has the right to enternumbers in Carrier ENUM?, Stastny Richard
• [Enum] I-D ACTION:draft-ietf-enum-validation-arch-00.txt, Internet-Drafts
• Re: [Enum] What is a Carrier and who has the right to enter numbers in Carrier ENUM?, james . f . baskin
• [Enum] RE: [voipeer] What is a Carrier and who has the right to enter numbers in Carrier ENUM?, Pfautz, Penn L, NEO
  • <Possible follow-ups>
  • [Enum] Re: [voipeer] What is a Carrier and who has the right to enter numbers in Carrier ENUM?, Stastny Richard
  • [Enum] RE: [voipeer] What is a Carrier and who has the right to enter numbers in Carrier ENUM?, Pfautz, Penn L, NEO
  • [Enum] Re: [voipeer] What is a Carrier and who has the right to enter numbers in Carrier ENUM?, Stastny Richard
• [Enum] What is a Carrier and who has the right to enter numbers in Carrier ENUM?, Stastny Richard
• [Enum] ENUM and E911, Voipers Portugal
  • <Possible follow-ups>
  • Re: [Enum] ENUM and E911, Stastny Richard
• [Enum] [Fwd: I-D ACTION:draft-mayrhofer-enum-vcard-00.txt], Richard Shockey
• [Enum] Its that time again .... Agenda Items for IETF Vancouver, Richard Shockey
  • Re: [Enum] Its that time again .... Agenda Items for IETF Vancouver, lconroy
    • Message not available
      • Re: [Enum] Its that time again .... Agenda Items for IETF Vancouver, Richard Shockey
  • <Possible follow-ups>
  • Re: [Enum] Its that time again .... Agenda Items for IETF Vancouver, Stastny Richard
    • Re: [Enum] Its that time again .... Agenda Items for IETF Vancouver, Richard Shockey
  • re: [Enum] Its that time again .... Agenda Items for IETF Vancouver, Stastny Richard
    • Re: [Enum] Its that time again .... Agenda Items for IETF Vancouver, David Meyer
      • Re: [Enum] Its that time again .... Agenda Items for IETF Vancouver, Richard Shockey
      • Re: [Enum] Its that time again .... Agenda Items for IETF Vancouver, David Meyer
• [Enum] [Fwd: I-D ACTION:draft-stein-great-00.txt], Richard Shockey
• [Enum] Request for Publication - draft-ietf-enum-iris-ereg-02.txt, Richard Shockey
• [Enum] Request for Publication - draftoietf-enum-voice-00.txt, Richard Shockey
• Re: [Enum] Neustar and GSM create alternate ROOT - add, Stastny Richard
  • <Possible follow-ups>
  • RE: [Enum] Neustar and GSM create alternate ROOT - add, Nieminen Klaus
• [Enum] Neustar and GSM create alternate ROOT, Stastny Richard
  • Re: [Enum] Neustar and GSM create alternate ROOT, Tom-PT Taylor
  • Re: [Enum] Neustar and GSM create alternate ROOT, Patrik Fältström
  • <Possible follow-ups>
  • Re: [Enum] Neustar and GSM create alternate ROOT, Stastny Richard
    • Re: [Enum] Neustar and GSM create alternate ROOT, Christian de Larrinaga
  • Re: [Enum] Neustar and GSM create alternate ROOT, Stastny Richard
  • RE: [Enum] Neustar and GSM create alternate ROOT, Fullbrook Kim \(UK\)
  • RE: [Enum] Neustar and GSM create alternate ROOT, Stastny Richard
  • RE: [Enum] Neustar and GSM create alternate ROOT, Fullbrook Kim \(UK\)
    • Re: [Enum] Neustar and GSM create alternate ROOT, lconroy
  • RE: [Enum] Neustar and GSM create alternate ROOT, Stastny Richard
• [Enum] Nominations for ENUM WG Secretary, Richard Shockey
• [Enum] [Fwd: Possible new Real-Time Applications and Infrastucture (RAI) Area], Richard Shockey
• [Enum] A note for the Implementers Draft, Richard Shockey
  • Re: [Enum] A note for the Implementers Draft, lconroy
    • Re: [Enum] A note for the Implementers Draft, Jim Reid
      • Re: [Enum] A note for the Implementers Draft, Richard Shockey
      • Re: [Enum] A note for the Implementers Draft, Jim Reid
      • Re: [Enum] A note for the Implementers Draft, Peter Williams
      • Re: [Enum] A note for the Implementers Draft, lconroy
      • Re: [Enum] A note for the Implementers Draft, Peter Williams
      • Re: [Enum] A note for the Implementers Draft, Jim Reid
      • Re: [Enum] A note for the Implementers Draft, Jim Reid
      • Re: [Enum] A note for the Implementers Draft, lconroy
      • Re: [Enum] A note for the Implementers Draft, Jim Reid
      • Re: [Enum] A note for the Implementers Draft, lconroy
      • Re: [Enum] A note for the Implementers Draft, Jim Reid
      • Re: [Enum] A note for the Implementers Draft, lconroy
  • <Possible follow-ups>
  • Re: [Enum] A note for the Implementers Draft, Stastny Richard
• [Enum] ENUM Working Group Last call on IRIS EREG, Richard Shockey
• [Enum] ENUM Working Group Last call on IANA Registration for Enumservice Voice, Richard Shockey
• [Enum] GnuGK works with ENUM and H.323-URLs, Bernie Hoeneisen
• [Enum] IRIS ereg and voice 00 documents, Richard Shockey
• [Enum] Carrier ENUM an applet of Voipeer (IP Interconnect), Stastny Richard
  • Re: [Enum] Carrier ENUM an applet of Voipeer (IP Interconnect), Kewin Stoeckigt
  • <Possible follow-ups>
  • [Enum] Carrier ENUM an applet of Voipeer (IP Interconnect), Stastny Richard
  • RE: [Enum] Carrier ENUM an applet of Voipeer (IP Interconnect), Schiefner, Carsten
  • Re: [Enum] Carrier ENUM an applet of Voipeer (IP Interconnect), Stastny Richard
    • Re: [Enum] Carrier ENUM an applet of Voipeer (IP Interconnect), Klaus Darilion
  • Re: [Enum] Carrier ENUM an applet of Voipeer (IP Interconnect), Stastny Richard
  • Re: [Enum] Carrier ENUM an applet of Voipeer (IP Interconnect), Stastny Richard
  • RE: [Enum] Carrier ENUM an applet of Voipeer (IP Interconnect), Fullbrook Kim \(UK\)
    • Re: [Enum] Carrier ENUM an applet of Voipeer (IP Interconnect), lconroy
  • Re: [Enum] Carrier ENUM an applet of Voipeer (IP Interconnect), Stastny Richard
  • Re: [Enum] Carrier ENUM an applet of Voipeer (IP Interconnect), Stastny Richard
• [Enum] I-D ACTION:draft-ietf-enum-voice-00.txt, Internet-Drafts
• [Enum] I-D ACTION:draft-ietf-enum-iris-ereg-02.txt, Internet-Drafts
• [Enum] Re: Erratum in RFC 4114 (fwd), Alice Hagens
• [Enum] WG action items..., Richard Shockey
  • Re: [Enum] WG action items..., Andrew Newton
  • <Possible follow-ups>
  • RE: [Enum] WG action items..., Stastny Richard
• [Enum] VoIP Identification and location, minor thesis, Graham Leslie Galea
  • <Possible follow-ups>
  • RE: [Enum] VoIP Identification and location, minor thesis, Michael Hammer \(mhammer\)
  • Re: [Enum] VoIP Identification and location, minor thesis, Stastny Richard
• [Enum] I-D ACTION:draft-ietf-enum-validation-epp-00.txt, Internet-Drafts
• AW: [Enum] ENUM silence - how's the re-charter coming?, Stastny Richard
  • Re: AW: [Enum] ENUM silence - how's the re-charter coming?, Richard Shockey
    • Re: AW: [Enum] ENUM silence - how's the re-charter coming?, Robert Schafer
      • Re: AW: [Enum] ENUM silence - how's the re-charter coming?, Richard Shockey
• [Enum] ENUM silence - how's the re-charter coming?, Pfautz, Penn L, NEO
  • Message not available
    • Re: [Enum] ENUM silence - how's the re-charter coming?, Michael Haberler
  • Re: [Enum] ENUM silence - how's the re-charter coming?, Bernie Hoeneisen
    • Re: [Enum] ENUM silence - how's the re-charter coming?, Patrik Fältström
  • <Possible follow-ups>
  • RE: [Enum] ENUM silence - how's the re-charter coming?, Stastny Richard
  • RE: [Enum] ENUM silence - how's the re-charter coming?, Stastny Richard
• [Enum] IETF-63 Proceedings Submission - ENUM WG Meeting Minutes - FINAL, Richard Shockey
• Re: [Enum] Re: [voipeer] Re: [Geopriv] Re: [Simple] tel URIs in common policy, Mpierce1
  • Re: [Enum] Re: [voipeer] Re: [Geopriv] Re: [Simple] tel URIs in common policy, David Meyer
    • Re: [Enum] Re: [voipeer] Re: [Geopriv] Re: [Simple] tel URIs in common policy, lconroy
  • <Possible follow-ups>
  • Re: [Enum] Re: [voipeer] Re: [Geopriv] Re: [Simple] tel URIs in common policy, Stastny Richard
• RE: [Enum] RE: [voipeer] Re: [Geopriv] Re: [Simple] tel URIs in commonpolicy, Brian Rosen
  • <Possible follow-ups>
  • RE: [Enum] RE: [voipeer] Re: [Geopriv] Re: [Simple] tel URIs in commonpolicy, Brian Rosen
    • RE: [Enum] RE: [voipeer] Re: [Geopriv] Re: [Simple] tel URIs incommonpolicy, Peter Williams
  • RE: [Enum] RE: [voipeer] Re: [Geopriv] Re: [Simple] tel URIs in commonpolicy, Henry Sinnreich
  • RE: [Enum] RE: [voipeer] Re: [Geopriv] Re: [Simple] tel URIs in commonpolicy, Henry Sinnreich
• [Enum] Re: [voipeer] Re: [Geopriv] Re: [Simple] tel URIs in common policy, Stastny Richard
  • [Enum] RE: [voipeer] Re: [Geopriv] Re: [Simple] tel URIs in common policy, Henry Sinnreich
  • <Possible follow-ups>
  • [Enum] RE: [voipeer] Re: [Geopriv] Re: [Simple] tel URIs in common policy, Stastny Richard
• [Enum] ENUM WG Meeting Minutes IETF 63 Paris - PRELIMINARY Version 3, Richard Shockey
  • [Enum] Clarification of WG Actions from IETF63 - modest proposal/experiences, lconroy
    • Re: [Enum] Clarification of WG Actions from IETF63 - modest proposal/experiences, Richard Shockey
• RE: [Enum] Re: [voipeer] Re: [Geopriv] Re: [Simple]telURIsin commonpolicy, Dolly, Martin C, ALABS
• Re: [Enum] ENUM WG Meeting Minutes IETF 63 Paris - PRELIMINARY Version 2, Stastny Richard
  • Re: [Enum] ENUM WG Meeting Minutes IETF 63 Paris - PRELIMINARY Version 2, Richard Shockey
• [Enum] Discussion and acceptance of Carrier / Private ENUM items dependent on WG recharter., Richard Shockey
• [Enum] ENUM WG Meeting Minutes IETF 63 Paris - PRELIMINARY Version 2, Richard Shockey
• RE: [Enum] Re: [voipeer] Re: [Geopriv] Re: [Simple] telURIsin commonpolicy, Michael Hammer \(mhammer\)
• [Enum] ENUM WG Document Authors Please Note ..., Richard Shockey
• Re: [Enum] Re: [voipeer] Re: [Geopriv] Re: [Simple] tel URIsincommonpolicy, Stastny Richard
  • <Possible follow-ups>
  • RE: [Enum] RE: [voipeer] Re: [Geopriv] Re: [Simple] tel URIsincommonpolicy, Michael Hammer \(mhammer\)
    • RE: [Enum] RE: [voipeer] Re: [Geopriv] Re: [Simple] telURIsincommonpolicy, Peter Williams
      • RE: [Enum] RE: [voipeer] Re: [Geopriv] Re: [Simple] telURIsincommonpolicy, Peter Williams
• [Enum] ENUM WG Meeting Minutes IETF 63 Paris - PRELIMINARY, Richard Shockey
  • <Possible follow-ups>
  • Re: [Enum] ENUM WG Meeting Minutes IETF 63 Paris - PRELIMINARY, Stastny Richard
    • Re: [Enum] ENUM WG Meeting Minutes IETF 63 Paris - PRELIMINARY, Richard Shockey
      • Re: [Enum] ENUM WG Meeting Minutes IETF 63 Paris - PRELIMINARY, Bernie Hoeneisen
  • RE: [Enum] ENUM WG Meeting Minutes IETF 63 Paris - PRELIMINARY, Pfautz, Penn L, NEO
    • Re: [Enum] ENUM WG Meeting Minutes IETF 63 Paris - PRELIMINARY, Tom-PT Taylor
  • RE: [Enum] ENUM WG Meeting Minutes IETF 63 Paris - PRELIMINARY, Michael Hammer \(mhammer\)
  • Re: [Enum] ENUM WG Meeting Minutes IETF 63 Paris - PRELIMINARY, Stastny Richard
    • Re: [Enum] ENUM WG Meeting Minutes IETF 63 Paris - PRELIMINARY, Richard Shockey
  • RE: [Enum] ENUM WG Meeting Minutes IETF 63 Paris - PRELIMINARY, Pfautz, Penn L, NEO
• Re: [Enum] Re: [voipeer] Re: [Geopriv] Re: [Simple] tel URIsin commonpolicy, Mpierce1
  • <Possible follow-ups>
  • Re: [Enum] Re: [voipeer] Re: [Geopriv] Re: [Simple] tel URIsin commonpolicy, Stastny Richard
    • RE: [Enum] Re: [voipeer] Re: [Geopriv] Re: [Simple] tel URIsincommonpolicy, Brian Rosen
• Re: [Enum] Re: [voipeer] Re: [Geopriv] Re: [Simple] tel URIsin commonpolicy, Stastny Richard
  • Re: [Enum] Re: [voipeer] Re: [Geopriv] Re: [Simple] tel URIsin commonpolicy, Jonathan Rosenberg
  • <Possible follow-ups>
  • Re: [Enum] Re: [voipeer] Re: [Geopriv] Re: [Simple] tel URIsin commonpolicy, Stastny Richard
• RE: [Enum] Re: [voipeer] Re: [Geopriv] Re: [Simple] tel URIs incommonpolicy, Stastny Richard
  • <Possible follow-ups>
  • RE: [Enum] RE: [voipeer] Re: [Geopriv] Re: [Simple] tel URIs incommonpolicy, Stastny Richard
• [Enum] Re: [Geopriv] Re: [Simple] tel URIs in common policy, Stastny Richard
  • [Enum] Re: [Geopriv] Re: [Simple] tel URIs in common policy, Jonathan Rosenberg
    • [Enum] Re: [voipeer] Re: [Geopriv] Re: [Simple] tel URIs in common policy, Otmar Lendl
      • RE: [Enum] Re: [voipeer] Re: [Geopriv] Re: [Simple] tel URIs in commonpolicy, Brian Rosen
      • Re: [Enum] Re: [voipeer] Re: [Geopriv] Re: [Simple] tel URIs in commonpolicy, Jonathan Rosenberg
      • [Enum] RE: [voipeer] Re: [Geopriv] Re: [Simple] tel URIs in common policy, Henry Sinnreich
      • RE: [Enum] RE: [voipeer] Re: [Geopriv] Re: [Simple] tel URIs in commonpolicy, Brian Rosen
  • <Possible follow-ups>
  • [Enum] Re: [Geopriv] Re: [Simple] tel URIs in common policy, Stastny Richard
  • [Enum] RE: [Geopriv] Re: [Simple] tel URIs in common policy, Stastny Richard
    • Re: [Enum] RE: [Geopriv] Re: [Simple] tel URIs in common policy, Tom-PT Taylor
      • RE: [Enum] RE: [Geopriv] Re: [Simple] tel URIs in common policy, Peter Williams
  • [Enum] Re: [Geopriv] Re: [Simple] tel URIs in common policy, James M. Polk
  • RE: [Enum] RE: [Geopriv] Re: [Simple] tel URIs in common policy, Pfautz, Penn L, NEO
  • RE: [Enum] Re: [Geopriv] Re: [Simple] tel URIs in common policy, Michael Hammer \(mhammer\)
    • Re: [Enum] Re: [Geopriv] Re: [Simple] tel URIs in common policy, Paul Kyzivat
  • RE: [Enum] Re: [Geopriv] Re: [Simple] tel URIs in common policy, Michael Hammer \(mhammer\)
  • RE: [Enum] Re: [Geopriv] Re: [Simple] tel URIs in common policy, Michael Hammer \(mhammer\)
    • Re: [Enum] Re: [Geopriv] Re: [Simple] tel URIs in common policy, Paul Kyzivat
  • Re: [Enum] Re: [Geopriv] Re: [Simple] tel URIs in common policy, Stastny Richard
• RE: [Enum] Now that carrier enum is seperate, will user enumever be deployed?, Pfautz, Penn L, NEO
• [Enum] Now that carrier enum is seperate, will user enum ever be deployed?, Michael Mealling
  • Re: [Enum] Now that carrier enum is seperate, will user enum ever be deployed?, Michael Haberler
  • Re: [Enum] Now that carrier enum is seperate, will user enum ever be deployed?, lconroy
  • <Possible follow-ups>
  • Re: [Enum] Now that carrier enum is seperate, will user enum ever be deployed?, Stastny Richard
• [Enum] Just in casy you needed a early WG meeting report., Richard Shockey
• [Enum] brief summary of the voipeer BOF, David Meyer
• [Enum] RE: [Sipping] voipeer BOF scheduling update, Romascanu, Dan \(Dan\)
  • [Enum] Re: [Sipping] voipeer BOF scheduling update, Hisham Khartabil
  • <Possible follow-ups>
  • [Enum] RE: [Sipping] voipeer BOF scheduling update, Khan, Sohel Q [NTK]
  • [Enum] RE: [Sipping] voipeer BOF scheduling update, Romascanu, Dan \(Dan\)
• RE: : [Enum] I-D ACTION:draft-ietf-enum-iris-ereg-01.txt, Pfautz, Penn L, NEO
• [Enum] voipeer BOF presentations, David Meyer
  • RE: [Enum] voipeer BOF presentations, John Horrocks
  • [Enum] Re: [voipeer] voipeer BOF presentations, Bob Briscoe
• [Enum] Presentations for Friday, Richard Shockey
• [Enum] voipeer BOF scheduling update, David Meyer
• [Enum] RE: COMMENTS on draft-ra-shin-enum-mobileweb-01.txt, Tim Moss
  • [Enum] Re: COMMENTS on draft-ra-shin-enum-mobileweb-01.txt, lconroy
  • <Possible follow-ups>
  • [Enum] RE: COMMENTS on draft-ra-shin-enum-mobileweb-01.txt, Tim Moss
    • Re: [Enum] RE: COMMENTS on draft-ra-shin-enum-mobileweb-01.txt, Otmar Lendl
    • Re: [Enum] RE: COMMENTS on draft-ra-shin-enum-mobileweb-01.txt, Clive D.W. Feather
  • RE: [Enum] RE: COMMENTS on draft-ra-shin-enum-mobileweb-01.txt, Tim Moss
• RE: [Enum] Fwd: I-D ACTION:draft-livingood-shockey-enum-npd-00.txt, Michael Hammer \(mhammer\)
• RE: [Enum] Fwd: I-D ACTION:draft-livingood-shockey-enum-npd-00.txt, Livingood, Jason
  • <Possible follow-ups>
  • RE: [Enum] Fwd: I-D ACTION:draft-livingood-shockey-enum-npd-00.txt, Michael Hammer \(mhammer\)
    • Message not available
      • RE: [Enum] Fwd: I-D ACTION:draft-livingood-shockey-enum-npd-00.txt, Ray Anderson
      • Re: [Enum] Fwd: I-D ACTION:draft-livingood-shockey-enum-npd-00.txt, Richard Shockey
  • Re: [Enum] Fwd: I-D ACTION:draft-livingood-shockey-enum-npd-00.txt, Stastny Richard
  • RE: [Enum] Fwd: I-D ACTION:draft-livingood-shockey-enum-npd-00.txt, McCandless, Kevin
• RE: Carrier ENUM Definition (was RE: [Enum] Agenda items forIETFParis), James McEachern
  • <Possible follow-ups>
  • RE: Carrier ENUM Definition (was RE: [Enum] Agenda items forIETFParis), Pfautz, Penn L, NEO
  • RE: Carrier ENUM Definition (was RE: [Enum] Agenda items forIETFParis), Rosbotham, Paul
  • RE: Carrier ENUM Definition (was RE: [Enum] Agenda items forIETFParis), Michael Hammer \(mhammer\)
• [Enum] Enum and Bind?, Arnold Ligtvoet
  • <Possible follow-ups>
  • Re: [Enum] Enum and Bind?, Arnold Ligtvoet
    • Message not available
      • Re: [Enum] Enum and Bind?, Arnold Ligtvoet
• [Enum] Generic Enumservices required?, Stastny Richard
• [Enum] updated voipeer BOF agenda for IETF 63, David Meyer
  • [Enum] (updated) updated voipeer BOF agenda for IETF 63, David Meyer
• [Enum] [Fwd: IESG response to appeal regarding draft-ietf-lemonade-mms-mapping-04], Richard Shockey
  • Re: [Enum] [Fwd: IESG response to appeal regarding draft-ietf-lemonade-mms-mapping-04], lconroy
• [Enum] COMMENTS on draft-ra-shin-enum-mobileweb-01.txt, Ray Anderson
• [Enum] Required reading for IETF Paris, Richard Shockey
  • <Possible follow-ups>
  • RE: [Enum] Required reading for IETF Paris, Stastny Richard
    • Re: [Enum] Required reading for IETF Paris, Richard Shockey
  • RE: [Enum] Required reading for IETF Paris, Robert . Shaw
• [Enum] A shameless plug for my new job., Richard Shockey
  • <Possible follow-ups>
  • Re: [Enum] A shameless plug for my new job., Stastny Richard
    • Re: [Enum] A shameless plug for my new job., Richard Shockey
    • RE: [Enum] A shameless plug for my new job., henry
  • Re: [Enum] A shameless plug for my new job., Stastny Richard
    • Re: [Enum] A shameless plug for my new job., Richard Shockey
  • RE: [Enum] A shameless plug for my new job., Michael Hammer \(mhammer\)
• [Enum] [voipeer] updated voipeer BOF agenda for IETF 63, David Meyer
• RE: Death to whois! (was Re: [Enum] E.164 communicationassumptions/requirements), Pfautz, Penn L, NEO
• [Enum] I-D ACTION:draft-ietf-enum-iris-ereg-01.txt, Internet-Drafts
  • Question: [Enum] I-D ACTION:draft-ietf-enum-iris-ereg-01.txt, Richard Shockey
    • Re: Question: [Enum] I-D ACTION:draft-ietf-enum-iris-ereg-01.txt, Andrew Newton
      • Re: Question: [Enum] I-D ACTION:draft-ietf-enum-iris-ereg-01.txt, Otmar Lendl
      • Re: Question: [Enum] I-D ACTION:draft-ietf-enum-iris-ereg-01.txt, Jaap Akkerhuis
      • Re: Question: [Enum] I-D ACTION:draft-ietf-enum-iris-ereg-01.txt, Andrew Newton
      • Re: Question: [Enum] I-D ACTION:draft-ietf-enum-iris-ereg-01.txt, Otmar Lendl
• [Enum] VoIP Peering BoF - Naming and Addressing Issues, Stastny Richard
  • <Possible follow-ups>
  • RE: [Enum] VoIP Peering BoF - Naming and Addressing Issues, Michael Hammer \(mhammer\)
• RE: combined User and Carrier ENUM (was RE: [Enum] Agenda items forIETF Paris), Michael Hammer \(mhammer\)
• [Enum] Fwd: I-D ACTION:draft-lind-infrastructure-enum-reqs-00.txt, Richard Shockey
• [Enum] ENUM-Event Europe Frankfurt/Germany, Daniel Schoettler
• [Enum] Comments on ID on new ENUM service "mobileweb", Russell, Nick, VF UK - Technology \(TS\)
  • Re: [Enum] Comments on ID on new ENUM service "mobileweb", Ray Anderson
  • <Possible follow-ups>
  • RE: [Enum] Comments on ID on new ENUM service "mobileweb", Fullbrook Kim \(UK\)
    • Re: [Enum] Comments on ID on new ENUM service "mobileweb", Jim Reid
      • Re: [Enum] Comments on ID on new ENUM service "mobileweb", lconroy
      • Re: [Enum] Comments on ID on new ENUM service "mobileweb", Peter Koch
      • Re: [Enum] Comments on ID on new ENUM service "mobileweb", lconroy
  • RE: [Enum] Comments on ID on new ENUM service "mobileweb", Russell, Nick, VF UK - Technology \(TS\)
  • RE: [Enum] Comments on ID on new ENUM service "mobileweb", Fullbrook Kim \(UK\)
    • Re: [Enum] Comments on ID on new ENUM service "mobileweb", Jim Reid
  • RE: [Enum] Comments on ID on new ENUM service "mobileweb", Fullbrook Kim \(UK\)
    • Re: [Enum] Comments on ID on new ENUM service "mobileweb", Peter Koch
      • Re: [Enum] Comments on ID on new ENUM service "mobileweb", Ray Anderson
    • Re: [Enum] Comments on ID on new ENUM service "mobileweb", Jim Reid
  • RE: [Enum] Comments on ID on new ENUM service "mobileweb", Michael Hammer \(mhammer\)
  • Re: [Enum] Comments on ID on new ENUM service "mobileweb", Ray Anderson
• [Enum] E.164 communication assumptions/requirements, james . f . baskin
  • Message not available
    • Re: [Enum] E.164 communication assumptions/requirements, Ray Anderson
  • <Possible follow-ups>
  • RE: [Enum] E.164 communication assumptions/requirements, Pfautz, Penn L, NEO
    • Message not available
      • RE: [Enum] E.164 communication assumptions/requirements, Ray Anderson
  • RE: [Enum] E.164 communication assumptions/requirements, Ray Anderson
    • Re: [Enum] E.164 communication assumptions/requirements, Thomas Jauch
      • Death to whois! (was Re: [Enum] E.164 communication assumptions/requirements), Jim Reid
      • Re: Death to whois! (was Re: [Enum] E.164 communication assumptions/requirements), Richard Shockey
      • Re: Death to whois! (was Re: [Enum] E.164 communication assumptions/requirements), Andrew Newton
      • Re: Death to whois! (was Re: [Enum] E.164 communication assumptions/requirements), Bernie Hoeneisen
      • Re: [Enum] E.164 communication assumptions/requirements, Ray Anderson
      • Re: [Enum] E.164 communication assumptions/requirements, Thomas Jauch
      • RE: [Enum] E.164 communication assumptions/requirements, Peter Williams
      • Re: [Enum] E.164 communication assumptions/requirements, Peter Williams
      • Re: [Enum] E.164 communication assumptions/requirements, Ray Anderson
    • RE: [Enum] E.164 communication assumptions/requirements, Michael Haberler
  • RE: [Enum] E.164 communication assumptions/requirements, FOUQUART Philippe RD-CORE-ISS
  • Re: [Enum] E.164 communication assumptions/requirements, Stastny Richard
    • Re: [Enum] E.164 communication assumptions/requirements, Bernie Hoeneisen
  • Re: [Enum] E.164 communication assumptions/requirements, Stastny Richard
  • RE: [Enum] E.164 communication assumptions/requirements, FOUQUART Philippe RD-CORE-ISS
  • Re: [Enum] E.164 communication assumptions/requirements, Stastny Richard
  • RE: [Enum] E.164 communication assumptions/requirements, Michael Hammer \(mhammer\)
  • RE: [Enum] E.164 communication assumptions/requirements, Stastny Richard
  • Re: [Enum] E.164 communication assumptions/requirements, Ray Anderson
  • RE: [Enum] E.164 communication assumptions/requirements, James McEachern
  • Re: [Enum] E.164 communication assumptions/requirements, Stastny Richard
  • RE: [Enum] E.164 communication assumptions/requirements, James McEachern
  • RE: [Enum] E.164 communication assumptions/requirements, Pfautz, Penn L, NEO
  • Re: [Enum] E.164 communication assumptions/requirements, Stastny Richard
  • Re: [Enum] E.164 communication assumptions/requirements, Stastny Richard
  • RE: [Enum] E.164 communication assumptions/requirements, Pfautz, Penn L, NEO
  • Re: [Enum] E.164 communication assumptions/requirements, Stastny Richard
    • Re: [Enum] E.164 communication assumptions/requirements, Otmar Lendl
      • Re: [Enum] E.164 communication assumptions/requirements, Peter Williams
      • Re: [Enum] E.164 communication assumptions/requirements, Jim Reid
      • Re: [Enum] E.164 communication assumptions/requirements, Clive D.W. Feather
  • RE: [Enum] E.164 communication assumptions/requirements, Pfautz, Penn L, NEO
  • RE: [Enum] E.164 communication assumptions/requirements, James McEachern
  • RE: [Enum] E.164 communication assumptions/requirements, James McEachern
  • RE: [Enum] E.164 communication assumptions/requirements, Pfautz, Penn L, NEO
  • RE: [Enum] E.164 communication assumptions/requirements, Fullbrook Kim \(UK\)
  • RE: [Enum] E.164 communication assumptions/requirements, Pfautz, Penn L, NEO
  • RE: [Enum] E.164 communication assumptions/requirements, James McEachern
    • Re: [Enum] E.164 communication assumptions/requirements, Alexander Mayrhofer
  • Re: [Enum] E.164 communication assumptions/requirements, Stastny Richard
  • Re: [Enum] E.164 communication assumptions/requirements, james . f . baskin
    • Message not available
      • Re: [Enum] E.164 communication assumptions/requirements, Ray Anderson
  • RE: [Enum] E.164 communication assumptions/requirements, Michael Hammer \(mhammer\)
    • Message not available
      • RE: [Enum] E.164 communication assumptions/requirements, Michael Haberler
  • Re: [Enum] E.164 communication assumptions/requirements, Stastny Richard
  • Re: [Enum] E.164 communication assumptions/requirements, Stastny Richard
• [Enum] Final Agenda items for IETF 63 Paris, Richard Shockey
  • Re: [Enum] Final Agenda items for IETF 63 Paris, lconroy
    • [Enum] COMMENTS on draft-ra-shin-enum-mobileweb-01.txt, Ray Anderson
• [Enum] draft I-D on Infrastructure ENUM Requirements, Lind, Steven D, ALABS
  • <Possible follow-ups>
  • Re: [Enum] draft I-D on Infrastructure ENUM Requirements, Stastny Richard
  • Re: [Enum] draft I-D on Infrastructure ENUM Requirements, Stastny Richard
• [Enum] draft voipeer BOF agenda, David Meyer
• [Enum] Clarification on Carrier ENUM discussions, Stastny Richard
  • <Possible follow-ups>
  • RE: [Enum] Clarification on Carrier ENUM discussions, Pfautz, Penn L, NEO
  • RE: [Enum] Clarification on Carrier ENUM discussions, Michael Hammer \(mhammer\)
    • Message not available
      • RE: [Enum] Clarification on Carrier ENUM discussions, Michael Haberler
  • Re: [Enum] Clarification on Carrier ENUM discussions, Stastny Richard
  • RE: [Enum] Clarification on Carrier ENUM discussions, Michael Hammer \(mhammer\)
  • Re: [Enum] Clarification on Carrier ENUM discussions, Stastny Richard
  • RE: [Enum] Clarification on Carrier ENUM discussions, Pfautz, Penn L, NEO
  • RE: [Enum] Clarification on Carrier ENUM discussions, Michael Hammer \(mhammer\)
  • RE: [Enum] Clarification on Carrier ENUM discussions, Michael Hammer \(mhammer\)
  • RE: [Enum] Clarification on Carrier ENUM discussions, Nieminen Klaus
  • RE: [Enum] Clarification on Carrier ENUM discussions, Michael Hammer \(mhammer\)
• [Enum] combined user/carrier ENUM proposal - proof of concept implementation, Michael Haberler
• RE: [Enum] code and maintainence complexity of combined user/carrierENUM proposal, Michael Hammer \(mhammer\)
  • Message not available
    • RE: [Enum] code and maintainence complexity of combined user/carrierENUM proposal, Michael Haberler
• RE: combined User and Carrier ENUM (was RE: [Enum] Agenda items for IETF Paris), Michael Hammer \(mhammer\)
  • Re: combined User and Carrier ENUM (was RE: [Enum] Agenda items for IETF Paris), Otmar Lendl
  • Re: combined User and Carrier ENUM (was RE: [Enum] Agenda items for IETF Paris), Jim Reid
  • <Possible follow-ups>
  • RE: combined User and Carrier ENUM (was RE: [Enum] Agenda items for IETF Paris), Michael Hammer \(mhammer\)
• [Enum] Fwd: I-D ACTION:draft-lendl-enum-validation-token-00.txt, Richard Shockey
• [Enum] Fwd: I-D ACTION:draft-mayrhofer-enum-validation-arch-00.txt, Richard Shockey
• [Enum] Fwd: I-D ACTION:draft-haberler-carrier-enum-00.txt, Richard Shockey
• [Enum] New I/D concerning ENUM validation architecture submitted, Bernie Hoeneisen
• [Enum] code and maintainence complexity of combined user/carrier ENUM proposal, Michael Haberler
  • Re: [Enum] code and maintainence complexity of combined user/carrier ENUM proposal, Jim Reid
    • Re: [Enum] code and maintainence complexity of combined user/carrier ENUM proposal, Michael Haberler
      • Re: [Enum] code and maintainence complexity of combined user/carrier ENUM proposal, lconroy
• Re: [Enum] Horizontal vs Vertical - not just carriers, Stastny Richard
• [Enum] Nearly Final Agenda items for IETF 63 Paris, Richard Shockey
• [Enum] Horizontal vs Vertical, Stastny Richard
  • RE: [Enum] Horizontal vs Vertical, Peter Williams
  • <Possible follow-ups>
  • RE: [Enum] Horizontal vs Vertical, Michael Hammer \(mhammer\)
    • Message not available
      • RE: [Enum] Horizontal vs Vertical - not just carriers, Ray Anderson
  • Re: [Enum] Horizontal vs Vertical, Stastny Richard
• [Enum] Fwd: I-D ACTION:draft-livingood-shockey-enum-npd-00.txt, Richard Shockey
  • <Possible follow-ups>
  • Re: [Enum] Fwd: I-D ACTION:draft-livingood-shockey-enum-npd-00.txt, Stastny Richard
  • RE: [Enum] Fwd: I-D ACTION:draft-livingood-shockey-enum-npd-00.txt, Stastny Richard
    • Re: [Enum] Fwd: I-D ACTION:draft-livingood-shockey-enum-npd-00.txt, Richard Shockey
  • Re: [Enum] Fwd: I-D ACTION:draft-livingood-shockey-enum-npd-00.txt, Stastny Richard
    • Re: [Enum] Fwd: I-D ACTION:draft-livingood-shockey-enum-npd-00.txt, Richard Shockey
  • RE: [Enum] Fwd: I-D ACTION:draft-livingood-shockey-enum-npd-00.txt, Michael Hammer \(mhammer\)
    • Re: [Enum] Fwd: I-D ACTION:draft-livingood-shockey-enum-npd-00.txt, Richard Shockey
  • Re: [Enum] Fwd: I-D ACTION:draft-livingood-shockey-enum-npd-00.txt, Stastny Richard
  • Re: [Enum] Fwd: I-D ACTION:draft-livingood-shockey-enum-npd-00.txt, Stastny Richard
  • RE: [Enum] Fwd: I-D ACTION:draft-livingood-shockey-enum-npd-00.txt, Michael Hammer \(mhammer\)
  • RE: [Enum] Fwd: I-D ACTION:draft-livingood-shockey-enum-npd-00.txt, Michael Hammer \(mhammer\)
  • Re: [Enum] Fwd: I-D ACTION:draft-livingood-shockey-enum-npd-00.txt, Stastny Richard
  • RE: [Enum] Fwd: I-D ACTION:draft-livingood-shockey-enum-npd-00.txt, Livingood, Jason
  • Re: [Enum] Fwd: I-D ACTION:draft-livingood-shockey-enum-npd-00.txt, Stastny Richard
  • RE: [Enum] Fwd: I-D ACTION:draft-livingood-shockey-enum-npd-00.txt, Michael Hammer \(mhammer\)
    • Re: [Enum] Fwd: I-D ACTION:draft-livingood-shockey-enum-npd-00.txt, Richard Shockey
  • RE: [Enum] Fwd: I-D ACTION:draft-livingood-shockey-enum-npd-00.txt, Michael Hammer \(mhammer\)
  • RE: [Enum] Fwd: I-D ACTION:draft-livingood-shockey-enum-npd-00.txt, Michael Hammer \(mhammer\)
    • Message not available
      • RE: [Enum] Fwd: I-D ACTION:draft-livingood-shockey-enum-npd-00.txt, Ray Anderson
  • RE: [Enum] Fwd: I-D ACTION:draft-livingood-shockey-enum-npd-00.txt, McCandless, Kevin
    • Message not available
      • RE: [Enum] Fwd: I-D ACTION:draft-livingood-shockey-enum-npd-00.txt, Michael Haberler
  • RE: [Enum] Fwd: I-D ACTION:draft-livingood-shockey-enum-npd-00.txt, Michael Hammer \(mhammer\)
  • RE: [Enum] Fwd: I-D ACTION:draft-livingood-shockey-enum-npd-00.txt, McCandless, Kevin
• Re: Carrier ENUM Definition (was RE: [Enum] Agenda items forIETF Paris), Stastny Richard
  • Message not available
    • Re: Carrier ENUM Definition (was RE: [Enum] Agenda items forIETF Paris), Richard Shockey
  • <Possible follow-ups>
  • Re: Carrier ENUM Definition (was RE: [Enum] Agenda items forIETF Paris), Stastny Richard
    • Re: Carrier ENUM Definition (was RE: [Enum] Agenda items forIETF Paris), Patrik Fältström
  • RE: Carrier ENUM Definition (was RE: [Enum] Agenda items forIETF Paris), Michael Hammer \(mhammer\)
    • Message not available
      • RE: Carrier ENUM Definition (was RE: [Enum] Agenda items forIETF Paris), Michael Haberler
  • RE: Carrier ENUM Definition (was RE: [Enum] Agenda items forIETF Paris), Michael Hammer \(mhammer\)
    • Message not available
      • RE: Carrier ENUM Definition (was RE: [Enum] Agenda items forIETF Paris), Michael Haberler
  • RE: Carrier ENUM Definition (was RE: [Enum] Agenda items forIETF Paris), Michael Hammer \(mhammer\)
    • Message not available
      • RE: Carrier ENUM Definition (was RE: [Enum] Agenda items forIETF Paris), Michael Haberler
      • Re: Carrier ENUM Definition (was RE: [Enum] Agenda items forIETF Paris), Clive D.W. Feather
  • RE: Carrier ENUM Definition (was RE: [Enum] Agenda items forIETF Paris), Michael Hammer \(mhammer\)
    • Re: Carrier ENUM Definition (was RE: [Enum] Agenda items forIETF Paris), Clive D.W. Feather
  • RE: Carrier ENUM Definition (was RE: [Enum] Agenda items forIETF Paris), James McEachern
    • Re: Carrier ENUM Definition (was RE: [Enum] Agenda items forIETF Paris), Otmar Lendl
  • RE: Carrier ENUM Definition (was RE: [Enum] Agenda items forIETF Paris), Michael Hammer \(mhammer\)
    • Re: Carrier ENUM Definition (was RE: [Enum] Agenda items forIETF Paris), Otmar Lendl
• RE: Carrier ENUM Definition (was RE: [Enum] Agenda items for IETFParis), Livingood, Jason
• [Enum] For context around the carrier enum discussion - voip peering BoF in Paris, Allison Mankin
  • Re: [Enum] For context around the carrier enum discussion - voip peering BoF in Paris, Richard Shockey
• Re: Carrier ENUM Definition (was RE: [Enum] Agenda items for IETF Paris), Stastny Richard
  • <Possible follow-ups>
  • RE: Carrier ENUM Definition (was RE: [Enum] Agenda items for IETF Paris), Michael Hammer \(mhammer\)
• Carrier ENUM Definition (was RE: [Enum] Agenda items for IETF Paris), Fullbrook Kim \(UK\)
  • Re: Carrier ENUM Definition (was RE: [Enum] Agenda items for IETF Paris), Richard Shockey
    • RE: Carrier ENUM Definition (was RE: [Enum] Agenda items forIETF Paris), Peter Williams
      • Re: Carrier ENUM Definition (was RE: [Enum] Agenda items forIETF Paris), Patrik Fältström
    • Re: Carrier ENUM Definition (was RE: [Enum] Agenda items for IETF Paris), Patrik Fältström
      • Re: Carrier ENUM Definition (was RE: [Enum] Agenda items for IETF Paris), Richard Shockey
      • Re: Carrier ENUM Definition (was RE: [Enum] Agenda items for IETF Paris), Patrik Fältström
      • Re: Carrier ENUM Definition (was RE: [Enum] Agenda items for IETF Paris), Richard Shockey
• [Enum] Fwd: I-D ACTION:draft-brandner-enum-voice-00.txt, Richard Shockey
• [Enum] Fwd: I-D ACTION:draft-ra-shin-enum-mobileweb-00.txt, Richard Shockey
• [Enum] Re: Submission of new I-D regarding ENUM on mobile-web, Sungwoo Shin
  • <Possible follow-ups>
  • RE: [Enum] Re: Submission of new I-D regarding ENUM on mobile-web, Russell, Nick, VF UK - Technology \(TS\)
• [Enum] Fwd: I-D ACTION:draft-conroy-enum-modestproposal-00.txt, lconroy
  • <Possible follow-ups>
  • [Enum] Fwd: I-D ACTION:draft-conroy-enum-modestproposal-00.txt, Richard Shockey
  • [Enum] Fwd: I-D ACTION:draft-conroy-enum-modestproposal-00.txt, Richard Shockey
• [Enum] Submission of new I-D regarding ENUM on mobile-web, Sungwoo Shin
  • <Possible follow-ups>
  • RE: [Enum] Submission of new I-D regarding ENUM on mobile-web, Livingood, Jason
• [Enum] Agenda items for IETF Paris, Richard Shockey
  • Re: [Enum] Agenda items for IETF Paris, Bernie Hoeneisen
  • <Possible follow-ups>
  • RE: [Enum] Agenda items for IETF Paris, Livingood, Jason
    • Re: [Enum] Agenda items for IETF Paris, Patrik Fältström
  • Re: [Enum] Agenda items for IETF Paris, Stastny Richard
    • Message not available
      • Re: [Enum] Agenda items for IETF Paris, Richard Shockey
  • RE: [Enum] Agenda items for IETF Paris, Michael Hammer \(mhammer\)
    • Message not available
      • RE: [Enum] Agenda items for IETF Paris, Richard Shockey
    • Message not available
      • RE: [Enum] Agenda items for IETF Paris, Michael Haberler
  • Re: [Enum] Agenda items for IETF Paris, Stastny Richard
  • RE: [Enum] Agenda items for IETF Paris, Michael Hammer \(mhammer\)
  • Re: [Enum] Agenda items for IETF Paris, Stastny Richard
  • RE: [Enum] Agenda items for IETF Paris, Michael Hammer \(mhammer\)
    • Re: [Enum] Agenda items for IETF Paris, Jim Reid