E.212 ENUMService Type Definition E.212 Parameters for the "tel" URI

Slides:



Advertisements
Similar presentations
International Telecommunication Union ENUM Issues and Solutions Houlin Zhao Director Telecommunication Standardization Bureau International Telecommunication.
Advertisements

Rfc4474bis-01 IETF 89 (London) STIR WG Jon & Cullen.
S3 Useful Expressions.
Why Join the Church? Keith Drury. I. First, a few thoughts… A. There are two ways of speaking of the church …the invisible church …the visible church.
19 April 2012 Impact of M2M Communications to E.212 Resources (IMSI) Jukka Rakkolainen / ECO.
1 IETF – ENUM US Government Briefing Richard Shockey IETF ENUM Work Group Chair Senior Technical Industry Liaison NeuStar, Inc Vermont Avenue N.W.
19 March E.212 ENUMService Type Definition E.212 Parameters for the "tel" URI Edward Lewis NeuStar IETF 68 ENUM WG meeting.
ENUM Update for voipeer BOF Richard Shockey ENUM co-chair IETF 63 Paris.
NARFE Configuration Advisory Board (CAB) Web Page.
GSM Network Structure Lance Westberg.
1.NET Web Forms Business Forms © 2002 by Jerry Post.
INFO 424 Week 11 INFO 424 Team Project Practicum Week 1 Glenn Booker.
Page 1IETF 65 ENUM WG IETF 65 – ENUM WG IANA Registration for an Enumservice and “tel” Parameter for Calling Name Delivery (CNAM) Information 20 March.
Mtivity Client Support System Quick start guide. Mtivity Client Support System We are very pleased to announce the launch of a new Client Support System.
Rfc4474bis-01 IETF 90 (Toronto) STIR WG Jon. First principles (yet again) Separating the work into two buckets: 1) Signaling – What fields are signed,
HPD Updates By Eric Heflin, Co-Chair ITI PC
Patrik Fältström. ITU Tutorial Workshop on ENUM. Feb 8, 2002, Geneva Explanation of ENUM (RFC 2916) Patrik Fältström Area Director, Applications Area,
IETF 67 – SIMPLE WG SIMPLE Problem Statement Draft-rang-simple-problem-statement-01 Tim Rang - Microsoft Avshalom Houri – IBM Edwin Aoki – AOL.
Polling and Voting Adrian Farrel Routing Area Director Maastricht, July 2010.
© 2015 albert-learning.com How to talk to your boss How to talk to your boss!!
Page 1I IETF ENUM WG IETF 70 – ENUM WG Enumservices for Voice and Video Messaging 4 Dec 2007 Co-Authors: Jason Livingood Don Troshynski Contributors: Rich.
Facebook. You need a facebook account before you set up a facebook page.
REPUTE and URI Templates Murray S. Kucherawy. The Story So Far draft-kucherawy-reputation-query-http specified, given a hostname where a reputation service.
What’s the matter with the boy? =What’s wrong with the boy? He has too much homework to do.
Informal letter or Writing skills Informal letter or .
Andrew(amwallis) Classes!
Please log on a computer Open the web and then Open four tabs…
(A love/hate mutually beneficial relationship)
THIS IS THE WAY ENUM Variants Jim McEachern
Enum dip indicator draft-stastny-iptel-tel-enumdi-00
STIR WG / IETF 94 Yokohama, Nov 2015 Jon
Interface extensions YANG & VLAN sub-interface YANG Status update
Hitchhikers Guide to SIP
EBSCO eBooks.
draft-ietf-simple-message-session-09
Addressing Pushback from Patients
Request-URI Param Delivery
GROWTH MINDSET.
SIP and ENUM Old draft-ietf-sipping-e has been split into child drafts
Some useful language and examples
Phrases For Business English
Fast Action Links extension A love letter to CiviCRM
IETF 64 – ENUM WG IANA Registration for an Enumservice Containing PSTN Signaling Information 8 November 2005 Co-Authors:
iSIP: iTIP over SIP and Using iCalendar with SIP
Research preferred A levels for law
PET (Preliminary English Test) Speaking Guide
Academic Communication Lesson 3
Business Communication
What's Wrong with this Slide
doc.: IEEE <doc#>
Implementation of ENUM on telecommunication networks
Doc.: IEEE /XXXr0 10 May 2011 Sep 19, 2007 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs)‏ Submission Title:
Submitting through Turnitin
WELCOME TO NCA! TEACHERS ORIENTATION.
Doc.: IEEE /XXXr0 10 May 2011 Sep 19, 2007 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs)‏ Submission Title:
Quarter 1.
PET (Preliminary English Test) Speaking Guide
Networking Workshop (2)
REPUTE Document Status
Lectures….and how to make them work for you
What's Wrong with this Slide
Regulatory ad-hoc Chairman (Vic Hayes)
draft-ietf-dtn-bpsec-06
Writing Groups and Revision Strategies
BPSec: AD Review Comments and Responses
Summary of the IEEE 802 Coexistence Process Discussion
ISIS Extensions for FlexE Link Advertisement
Interface extensions YANG & VLAN sub-interface YANG Status update
Interoperabilty Cipher Suites
Commenting on Artifacts
Presentation transcript:

E.212 ENUMService Type Definition E.212 Parameters for the "tel" URI Edward Lewis NeuStar IETF 68 ENUM WG meeting 19 March 2007 ed.lewis@neustar.biz

Back-to-Back Items draft-lewis-enum-enumservice-e212-00.txt To register "E2U+E212" as enumservice Indicates NAPTR has ITU E.212 infomation draft-lewis-enum-teluri-e212-00.txt To define parameters in tel: for E.212 19 March 2007 ed.lewis@neustar.biz

Plans for the two Go over comments received so far, get more while here Edit the documents in the coming week(s) post IETF68 Submit again as directed (WG or not) 19 March 2007 ed.lewis@neustar.biz

E.212 for IETF'ers E.212 is an ITU document/standard defining meta-data for a mobile-phone telephone number MCC (Mobile Country Code) MNC (Mobile Network Code) MSIN (Mobile Subscriber Identification #) IMSI (International Mobile Subscriber Identity) - the concatenation of the other 3 19 March 2007 ed.lewis@neustar.biz

A diagram MCC MNC MSIN IMSI MCC - 3 digits MNC - 2 or 3 digits MSIN - up to 10 digits IMSI - up to 15 digits 19 March 2007 ed.lewis@neustar.biz

Why IETF documents? This is about ENUM Wanting to store the ITU-defined parameters in ENUM This isn't so much about E.212, 'cept that that is the "payload" 19 March 2007 ed.lewis@neustar.biz

draft-lewis-enum-enumservice-e212-00.txt First, it's a -00 individual, happy to make it a WG document Fills in an ENUM service "application" E2U+E212 means the NAPTR RR has a tel: URI (with extensions in the other draft) 19 March 2007 ed.lewis@neustar.biz

Comments on that one Would like a good use case Fair enough, the draft is minimal and am happy to add that. Still in the process of writing it. Is it worth getting a non-SIP ENUM extension defined? Suggestion to use an experimental (x-) but really want a "real" definition 19 March 2007 ed.lewis@neustar.biz

More comments What about "aux-info:e212"? Although workable, a few reservations We/WG don't have other "aux-info's" in mind, I don't like to generalize from a single case E.212 is subjectively significant enough to stand on its own, and is reliant on an external (ITU) definition Linking in other (unknown) types would likely slow this process 19 March 2007 ed.lewis@neustar.biz

First doc question to WG Should this be adopted as WG item? What is missing from the application and supporting document? Sub-note: I couldn't find a reliable "how to" to follow when submitting these drafts, so I "undercut" the submission draft-ietf-enum-enumservices-guide-03.txt 19 March 2007 ed.lewis@neustar.biz

draft-lewis-enum-teluri-e212-00.txt This document defines parameters for the tel: URI to hold the E.212 data In the spirit of RFC 4694, but for different data Four parameters are defined, as per earlier slide (MCC, MNC, MSIN, IMSI) 19 March 2007 ed.lewis@neustar.biz

My goal I am interested in retrieving the MCC and MNC for a telephone number via ENUM The draft includes MSIN and IMSI parameters for completeness 19 March 2007 ed.lewis@neustar.biz

Comments This draft ought to go to IPTEL What's E.212? No response to that yet from me What's E.212? Should this draft explain it or just refer to the ITU document (now freely available)? When I prepared the draft, I went for not including an explanation but can be convinced otherwise 19 March 2007 ed.lewis@neustar.biz

More comments Need an illustrative use case The ABNF is wrong Working on that, went for brevity in the -00 The ABNF is wrong A few pointed this out, you are all right, I'll fix that The URI is wrong Sorry - sigh, I wrote the draft on an airplane and it shows ;) (Goes for the ABNF too.) 19 March 2007 ed.lewis@neustar.biz

Yet more comments MCC+MNC xor IMSI? Should the syntax require either both MCC and MNC be present or the IMSI be present? My response is - that's the probable use case, but does this have to be encoded in the syntax rules? I prefer to let the syntax be freer than the use 19 March 2007 ed.lewis@neustar.biz

And more comments... Isn't it unwise to have the IMSI, MSIN, and maybe even the MCC and MNC in a public database? I'd agree with that, but the drafts are just providing a means to put this in ENUM and not saying that the data would be public Not all DNS servers are on public networks 19 March 2007 ed.lewis@neustar.biz

Second doc questions Should this be an ENUM WG doc or go ask IPTEL WG to adopt this? 19 March 2007 ed.lewis@neustar.biz

Well, I'm out of slides Discussion? 19 March 2007 ed.lewis@neustar.biz