From sumanth@cablelabs.com Wed Oct 6 20:27:48 2010 Return-Path: X-Original-To: drinks@core3.amsl.com Delivered-To: drinks@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E38FA3A6FB3 for ; Wed, 6 Oct 2010 20:27:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 3.194 X-Spam-Level: *** X-Spam-Status: No, score=3.194 tagged_above=-999 required=5 tests=[AWL=-2.236, BAYES_00=-2.599, FRT_PENIS1=3.592, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001, MANGLED_PENIS=2.3] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eYAT8dYuqz+I for ; Wed, 6 Oct 2010 20:27:39 -0700 (PDT) Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by core3.amsl.com (Postfix) with ESMTP id B44AF3A7002 for ; Wed, 6 Oct 2010 20:27:38 -0700 (PDT) Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.4/8.14.4) with ESMTP id o973SdOj022246 for ; Wed, 6 Oct 2010 21:28:39 -0600 Received: from srvxchg.cablelabs.com (10.5.0.15) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com); Wed, 6 Oct 2010 21:28:39 -0700 (MST) X-Virus-Status: clean(F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com) Received: from srvxchg.cablelabs.com ([10.5.0.15]) by srvxchg ([10.5.0.15]) with mapi; Wed, 6 Oct 2010 21:28:39 -0600 From: Sumanth Channabasappa To: "Drinks@ietf.org" Date: Wed, 6 Oct 2010 21:28:36 -0600 Thread-Topic: Notes from the Interim Meeting Thread-Index: Actlz7pWgPrjNX1EQKSQQhpWAR7K1g== Message-ID: <76AC5FEF83F1E64491446437EA81A61F7D201D8FB3@srvxchg> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_76AC5FEF83F1E64491446437EA81A61F7D201D8FB3srvxchg_" MIME-Version: 1.0 X-Approved: ondar Subject: [drinks] Notes from the Interim Meeting X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Oct 2010 03:27:49 -0000 --_000_76AC5FEF83F1E64491446437EA81A61F7D201D8FB3srvxchg_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Folks, Thanks again to everyone who participated in the DRINKS Interim meeting a c= ouple of weeks ago. Please find enclosed the notes below. - Alex and Sumanth IETF DRINKS DESIGN INTERIM MEETING =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D September 15, 2010 (Wednesday); 0900 - 1630 (Mountain Daylight Time) / 1500= - 2230 (UTC) Participants =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D [In-Person] - Jean-Francois Mule - Ken Cartwright - Syed Ali - Sumanth Channabasappa [Remote; note: some participants were in and out] - Alexander Mayrhofer - David Schwartz - Otmar Lendl - Manjul Maharishi - Penn Ffautz - Gonzalo Camarillo ACTION ITEMS =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D I-D Changes ----------- [Ken C] - come up with a way to make the source identity types enumeration extensib= le, and add client certificate type - commit changes to linearize bulk requests, and add informative text to c= larify that the order of processing is the same as the order in the request= . - make agreed upon XML Schema changes (see below) [Syed] - to add informative text regarding COR claim operation - make agreed upon XML Schema changes (see below) [Alex] - review requirements section [Sumanth] - Propose re-use of existing data types within the XML Schema Others ------ [David S] may volunteer to propose the third case (continue through entire = request and note down all errors during bulk provisioning. [Otmar] propose separate prefix type for open numbering plan [DONE] [Penn] is requested to keep the team informed of the Global SPID I-D AGENDA =3D=3D=3D=3D=3D=3D 0. Administrivia 1. WG & document status 2 & 3. Protocol Document Link: http://tools.ietf.org/wg/drinks/draft-ietf-drinks-spprov/ 4. Use Cases & Requirements Draft Link: http://tools.ietf.org/wg/drinks/draft-ietf-drinks-usecases-require= ments/ 5. Transport Document Link: http://tools.ietf.org/wg/drinks/draft-ietf-drinks-sppp-over-soap/ 6. Wrap-up NOTES =3D=3D=3D=3D=3D 0. Administrivia ---------------- - Participants were welcomed, and we went over the 'Note Well', 'Agenda' an= d 'Meeting Logistics' - The following volunteered as 'official' note takers: Syed A, Alex M - Sumanth volunteered to be the Jabber scribe; however, given the lack of a= ttendance on Jabber no discussions were noted there. 1. WG & document status ----------------------- + We discussed the revised milestones (http://tools.ietf.org/wg/drinks/cha= rters) - Sep 2010: Request Publication of Usecases draft - Dec 2010: Request Publication of Protocol & Transport draft - Current goal: shutdown WG after/in Prague + We also briefly touched on the related efforts, specifically the Global S= PID - Penn is working on an I-D that is currently in internal review and will u= se IANA enterprise numbers (by the end of Sep) - FYI, this is not going to be a DRINKS WG document 2 & 3 Protocol Document - Link: http://tools.ietf.org/wg/drinks/draft-ietf-drinks-spprov/ - The discussions started with a quick overview of the document by Ken Cart= wright, and a list of all the changes made by the authors (Ken, Syed, Jean-= Francois); see emails prior to the interim for details + During the process we identified the following open issues a) Partial success; bulk processing b) Source based routing and source identity (Section 6.1) c) Synchronous and asynchronous COR claims d) Bulk Provisioning changes e) Response code structure -- we did not discuss this f) XML Schema review ~~~ A) Partial success - Brief overview: If you are provisioning a large data set with multiple en= tries into the Registry and an error is found, you have the following optio= ns: 1) Stop when you find the first error and rollback 2) Stop when you find the first error and commit everything until then -> t= his is termed Partial Success 3) Continue through the entire request, and note down all the errors Question: Which ones should we support? - Resolution: The general agreement was to support 1) and 2). However, the= re was discussion on 3), which we agreed to not support in the current vers= ion. David S volunteered to come with an extension (independent of the curr= ent protocol I-D) for consideration by the team and ascertain interest. ~~~ B) Source based routing and source identity type Source Based Routing: The question was whether we should support this. There was significant dis= cussion among the participants ranging from whether routing information sho= uld be made available to the particular querying organization to the relati= onships between the various entities (e.g., should we have a relationship b= etween the destination group to the peer and not just the Route Group). We = realized a few things, such as: - we are missing the ability to associate relationships at an organization= al level in addition to egress and ingress points (which may be fine) - there are various factors that one may consider beyond the criteria we ar= e speaking about, such as time of day, IP address etc. - we don't want to control on a per-organization basis as to which routes c= an be seen Resolution: Given the additional complexity this may introduce we decided n= ot to make any changes to the I-D. Source Identity Types: - We reviewed the existing source identity types to see if they were suffic= ient or not. Resolution: Two suggestions were provided: add client certificates as a typ= e, and figure out a way to make the enumeration extensible. ~~~ C) Synchronous and Asynchronous COR claim Background: When the provisioning entity requests the addition of a PI, it= can claim to be the COR. The question is: should we support synchronous an= d asynchronous operations? Today it is asynchronous. An example of synchron= ous operations is in Section 9.3 of the document titled "sp_example.txt", s= ent by Syed via email on on 9/15 (~midnight Eastern time) Resolution: After much discussion we decided not to support synchronous COR= claims. In addition, Syed will add informative text regarding COR claim op= eration to explain this. AIs: Syed to add informative text regarding COR claim operation (we will on= ly support asynchronous operations; see discussion below for details). ~~~ D) Bulk Requests Ken proposed a way to simplify bulk requests where you have a linear set of= requests rather than a gathering of linear requests as is documented in th= e submitted version of the I-D. Resolution: We agreed to the changes. In addition Ken will add informative = text to clarify that the order of processing is the same as the order in th= e request. ~~~ E) Response Code Structure - We did not get to discuss this; David to follow-up on the design team cal= ls. ~~~ F) XML Schema + We then reviewed the XML Schema and came up with a few recommendations; s= ome of which are captured here (others were captured by the authors) - Remove transactional attribute from the 'spppUpdateRequest' element - Modify 'spppb:ObjectResult' to reflect the suggested changes - Associate PI <-> NAPTR - Re-use well-known data types (AI: Sumanth to send suggestions) + We also had some open discussions - Open numbering plan: Otmar proposed a separate prefix type (see email fro= m 9/15) - Email from: http://www.ietf.org/mail-archive/web/drinks/current/msg00766.= html > The main issue is that everywhere in the document, we are free of the r= esolution protocols, except in the case where we use a NAPTR. Why do we nee= d it? > Based on the discussions from a few months ago, the reason for NAPTR is= that it is well understood and implemented > Otmar indicated that a URI type cannot be resolved if we stick to just = NAPTR AI: Otmar to check the discussions on this from a few months ago and re-a= sk the question if the responses do not provide clarity - Metadata? For example, Security attributes for a phone number, capacity i= n the SIP Routing Group. The rank associated with the destination group is = currently in the route record - can we place it on the route group? > Resolution: This is out of scope for now AI: (Alex) Requirements Section 4. Use Cases & Requirements Draft --------------------------------- Link: http://tools.ietf.org/wg/drinks/draft-ietf-drinks-usecases-requiremen= ts/ - We are awaiting feedback from the volunteer reviewers (Jon P, Sohel K) - Once we get and incorporate comments, we will request WGLC 5. Transport Document --------------------- Link: http://tools.ietf.org/wg/drinks/draft-ietf-drinks-sppp-over-soap/ - No updates on this document; we briefly discussed that we should make som= e progress later in the year to get this done in a timely manner 6. Wrap-up ---------- - Summary of action items; see AI list at the beginning + Next steps - Make the discussed updates (I-D authors) and submit a revision to the pro= tocol I-D in the next couple of weeks - Prepare for Beijing --_000_76AC5FEF83F1E64491446437EA81A61F7D201D8FB3srvxchg_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Folks,
 
Thanks again to = everyone=20 who participated in the DRINKS Interim meeting a couple of weeks ago.= =20 Please find enclosed the notes below.
 
- Alex and=20 Sumanth
 
 
 
IETF DRINKS DESIGN INTERIM=20 MEETING
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
September 15, 2010 (Wedne= sday); 0900 -=20 1630 (Mountain Daylight Time) / 1500 - 2230 =20 (UTC)
 
 
Participants
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D
[In-Person]
-=20 Jean-Francois Mule
- Ken Cartwright
- Syed Ali
- Sumanth Channabas= appa=20
 

[Remote; note: some participants were in and out]
- Alexander=20 Mayrhofer
- David Schwartz
- Otmar Lendl
- Manjul Maharishi
- P= enn=20 Ffautz
- Gonzalo Camarillo
 
    
ACT= ION=20 ITEMS
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
 

I-D Changes
-----------
 
[Ken C]
- come up with a way to make the source identity types=20 enumeration extensible, and add client certificate type
- commit changes= to=20 linearize bulk requests, and  add informative text to clarify that the= =20 order of processing is the same as the order in the request.
- make agre= ed=20 upon XML Schema changes (see below)
 
[Syed]
- to add informative text regarding COR claim operation
= -=20 make agreed upon XML Schema changes (see below)
 
[Alex]
- review requirements section
 
[Sumanth]
- Propose re-use of existing data types within the XML=20 Schema
 
Others
------
 
[David S] may volunteer to propose the third case (continue through en= tire=20 request and note down all errors during bulk provisioning.
 
[Otmar] propose separate prefix type for open numbering plan [DONE]
 

[Penn] is requested to keep the team informed of the Global SPID I= -D=20
 

AGENDA
=3D=3D=3D=3D=3D=3D
0. Administrivia
 
1. WG & document status 
 

2 & 3. Protocol Document
   Link: http://t= ools.ietf.org/wg/drinks/draft-ietf-drinks-spprov/
 

4. Use Cases & Requirements Draft
   Link: http://tools.ietf.org/wg/drinks/draft-ietf-drinks-usecases-requireme= nts/
 
       
5. Transport=20 Document
   Link: = http://tools.ietf.org/wg/drinks/draft-ietf-drinks-sppp-over-soap/
 

6. Wrap-up
 
 
 
NOTES
=3D=3D=3D=3D=3D
0. Administrivia
----------------
 
- Participants were welcomed, and we went over the 'Note Well', 'Agend= a'=20 and 'Meeting Logistics'
- The following volunteered as 'official' note=20 takers: Syed A, Alex M
- Sumanth volunteered to be the Jabber scribe;=20 however, given the lack of attendance on Jabber no discussions were noted t= here.=20
 

1. WG & document status
-----------------------
 
+ We discussed the revised milestones  (http://tools.ietf.org/wg/= drinks/charters)
-=20 Sep 2010: Request Publication of Usecases draft
- Dec 2010: Request=20 Publication of Protocol & Transport draft
- Current goal: shutdown W= G=20 after/in Prague
 
+ We also briefly touched on the related efforts, specifically the Glo= bal=20 SPID
- Penn is working on an I-D that is currently in internal review an= d=20 will use IANA enterprise numbers (by the end of Sep)
- FYI, this is not = going=20 to be a DRINKS WG document
 

2 & 3  Protocol Document
- Link: http://t= ools.ietf.org/wg/drinks/draft-ietf-drinks-spprov/
 
- The discussions started with a quick overview of the document by Ken= =20 Cartwright, and a list of all the changes made by the authors (Ken, Syed,=20 Jean-Francois); see emails prior to the interim for details
 
+ During the process we identified the following open issues
 = a)=20 Partial success; bulk processing
 b) Source based routing and sourc= e=20 identity (Section 6.1)
 c) Synchronous and asynchronous COR=20 claims
 d) Bulk Provisioning changes 
 e) Response co= de=20 structure -- we did not discuss this
  f) XML Schema review
 

~~~
A) Partial success
 
- Brief overview: If you are provisioning a large data set with multip= le=20 entries into the Registry and an error is found, you have the following=20 options:
1) Stop when you find the first error and rollback
2) Stop w= hen=20 you find the first error and commit everything until then -> this is ter= med=20 Partial Success
3) Continue through the entire request, and note down a= ll=20 the errors
 
Question: Which ones should we support? 
 

 - Resolution: The general agreement was to support 1) and 2)= .=20 However, there was discussion on 3), which we agreed to not support in the= =20 current version. David S volunteered to come with an extension (independent= of=20 the current protocol I-D) for consideration by the team and ascertain=20 interest.
 
~~~
 
B) Source based routing and source identity type
 
Source Based Routing:
 The question was whether we should supp= ort=20 this. There was significant discussion among the participants ranging from= =20 whether routing information should be made available to the particular quer= ying=20 organization to the relationships between the various entities (e.g., shoul= d we=20 have a relationship between the destination group to the peer and not just = the=20 Route Group). We realized a few things, such as:
-  we are missing = the=20 ability to associate relationships at an organizational level in addition t= o=20 egress and ingress points (which may be fine)
- there are various factor= s=20 that one may consider beyond the criteria we are speaking about, such as ti= me of=20 day, IP address etc.
- we don't want to control on a per-organization ba= sis=20 as to which routes can be seen
 
Resolution: Given the additional complexity this may introduce we deci= ded=20 not to make any changes to the I-D.
 
Source Identity Types:
- We reviewed the existing source identity t= ypes=20 to see if they were sufficient or not.
 
Resolution: Two suggestions were provided: add client certificates as = a=20 type, and figure out a way to make the enumeration extensible.
 
~~~
 
C) Synchronous and Asynchronous COR claim
 
Background:  When the provisioning entity requests the addition o= f a=20 PI, it can claim to be the COR. The question is: should we support synchron= ous=20 and asynchronous operations? Today it is asynchronous. An example of synchr= onous=20 operations is in Section 9.3 of the document titled "sp_example.txt", sent = by=20 Syed via email on on 9/15 (~midnight Eastern time)
 
Resolution: After much discussion we decided not to support synchronou= s COR=20 claims. In addition, Syed will add informative text regarding COR claim=20 operation to explain=20 this.          
 
AIs: Syed to add informative text regarding COR claim operation (we wi= ll=20 only support asynchronous operations; see discussion below for details).
 
~~~
 
D) Bulk Requests
Ken proposed a way to simplify bulk requests where= you=20 have a linear set of requests rather than a gathering of linear requests as= is=20 documented in the submitted version of the I-D.
Resolution: We agreed to= the=20 changes. In addition Ken will add informative text to clarify that the orde= r of=20 processing is the same as the order in the request.
 
 
 
~~~
 
E) Response Code Structure
- We did not get to discuss this; David = to=20 follow-up on the design team calls.
 
~~~
 
 
F) XML Schema
+ We then reviewed the XML Schema and came = up=20 with a few recommendations; some of which are captured here (others were=20 captured by the authors)
- Remove transactional attribute from the=20 'spppUpdateRequest' element
- Modify 'spppb:ObjectResult' to reflect the= =20 suggested changes
- Associate PI <-> NAPTR
- Re-use well-known= data=20 types (AI: Sumanth to send suggestions)
 
+ We also had some open discussions
- Open numbering plan: Otmar=20 proposed a separate prefix type (see email from 9/15)
- Email from: = http://www.ietf.org/mail-archive/web/drinks/current/msg00766.html
&n= bsp;=20 > The main issue is that everywhere in the document, we are free of the= =20 resolution protocols, except in the case where we use a NAPTR. Why do we ne= ed=20 it?
  > Based on the discussions from a few months ago, the reas= on=20 for NAPTR is that it is well understood and implemented
  > Otma= r=20 indicated that a URI type cannot be resolved if we stick to just NAPTR
 
  AI: Otmar to check the discussions on this from a few months ag= o and=20 re-ask the question if the responses do not provide clarity
 
- Metadata? For example, Security attributes for a phone number, capac= ity=20 in the SIP Routing Group. The rank associated with the destination group is= =20 currently in the route record - can we place it on the route=20 group?
   > Resolution: This is out of scope for=20 now
 
 
AI: (Alex) Requirements Section
 
 
 
4. Use Cases & Requirements=20 Draft
---------------------------------
 
Link: http://tools.ietf.org/wg/drinks/draft-ietf-drinks-usecases-requireme= nts/
-=20 We are awaiting feedback from the volunteer reviewers (Jon P, Sohel K)
-= Once=20 we get and incorporate comments, we will request WGLC
 
       
5. Transport=20 Document
---------------------
Link: = http://tools.ietf.org/wg/drinks/draft-ietf-drinks-sppp-over-soap/
-= =20 No updates on this document; we briefly discussed that we should make some= =20 progress later in the year to get this done in a timely manner
 

6. Wrap-up
----------
- Summary of action items; see AI list= at=20 the beginning
 
+ Next steps
- Make the discussed updates (I-D authors) and submit = a=20 revision to the protocol I-D in the next couple of weeks
- Prepare for=20 Beijing
 
 
--_000_76AC5FEF83F1E64491446437EA81A61F7D201D8FB3srvxchg_-- From sumanth@cablelabs.com Thu Oct 7 09:33:05 2010 Return-Path: X-Original-To: drinks@core3.amsl.com Delivered-To: drinks@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C98B83A6C24 for ; Thu, 7 Oct 2010 09:33:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.337 X-Spam-Level: X-Spam-Status: No, score=0.337 tagged_above=-999 required=5 tests=[AWL=0.800, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qDF8swGmc1Pm for ; Thu, 7 Oct 2010 09:33:01 -0700 (PDT) Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by core3.amsl.com (Postfix) with ESMTP id 20D2E3A6FD0 for ; Thu, 7 Oct 2010 09:33:00 -0700 (PDT) Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.4/8.14.4) with ESMTP id o97GY12j015720 for ; Thu, 7 Oct 2010 10:34:01 -0600 Received: from srvxchg.cablelabs.com (10.5.0.15) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com); Thu, 7 Oct 2010 10:34:01 -0700 (MST) X-Virus-Status: clean(F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com) Received: from srvxchg.cablelabs.com ([10.5.0.15]) by srvxchg ([10.5.0.15]) with mapi; Thu, 7 Oct 2010 10:34:01 -0600 From: Sumanth Channabasappa To: "Drinks@ietf.org" Date: Thu, 7 Oct 2010 10:34:00 -0600 Thread-Topic: Rough Notes and AI list from the call on 10/7 Thread-Index: ActQMdwXrcsFb0LURMebPnHWJtIGmQQyesrgAVBYIVA= Message-ID: <76AC5FEF83F1E64491446437EA81A61F7D201D9007@srvxchg> References: <76AC5FEF83F1E64491446437EA81A61F7D1FF40829@srvxchg> <76AC5FEF83F1E64491446437EA81A61F7D201D8C3C@srvxchg> In-Reply-To: <76AC5FEF83F1E64491446437EA81A61F7D201D8C3C@srvxchg> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Approved: ondar Subject: [drinks] Rough Notes and AI list from the call on 10/7 X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Oct 2010 16:33:06 -0000 IETF DRINKS DESIGN TEAM CALL=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D 10/7/2010, 10:00a-10:45a (Eastern)/8:00a-8:45a (Mountain) =20 Participants =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D - Ken Cartwright - David Schwartz - Syed Ali - Jean-Francois Mule (latter part of the call) - Sumanth Channabasappa=20 =20 =20 ACTION ITEMS=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D [Tokens for editing the protocol I-D] (Syed) Today (10/7)=20 (Jean-Francois) Tomorrow (10/8) [Authors] Submit a revision with the recent changes this week/weekend AGENDA =3D=3D=3D=3D=3D=3D 1. Updates from the authors (Ken, Syed, Jean-Francois)=20 2. Submission plans for the next version of the protocol I-D=20 3. Open issues NOTES =3D=3D=3D=3D=3D 1/ Updates from the authors (Ken, Syed, Jean-Francois)=20 - Ken is done with his updates, which he shared last week and earlier this = week - Syed has made most of his changes, but requested another day to complete = it =20 2/ Submission plans for the next version of the protocol I-D=20 - Once Syed and Jean-Francois make their changes, we will be submitting thi= s over the weekend 3/ Open issues + We discussed a couple of topics - [Syed] asked if he should work on separating the delete operations, which= are now within sub-sections. Based on Ken's explanation there will be no c= hange. - [Ken] raised the question of the Open Numbering Plan, which resulted in a= few discussions, mostly around whether the prefix should be considered a s= pecial case of a TN Range (as authored today) or should we look at an alter= native approach (e.g., see Otmar's recommendation from 9/15). In the end we= agreed that the specific solution did not matter. However, we will go ahea= d and submit it as written in the document today and we can have further di= scussions after the submission. =20 - We ([David], [Jean-Francois]) also briefly discussed Penn's proposed I-D = that was shared with the design team yesterday. This is due to be submitted= soon (according to Penn). = From syed.ali@neustar.biz Thu Oct 7 22:43:31 2010 Return-Path: X-Original-To: drinks@core3.amsl.com Delivered-To: drinks@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0B7D63A67E9 for ; Thu, 7 Oct 2010 22:43:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.853 X-Spam-Level: X-Spam-Status: No, score=-0.853 tagged_above=-999 required=5 tests=[AWL=1.746, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZPtPDj31GoIw for ; Thu, 7 Oct 2010 22:43:29 -0700 (PDT) Received: from neustar.com (mx2.neustar.com [156.154.25.104]) by core3.amsl.com (Postfix) with ESMTP id AB89F3A6817 for ; Thu, 7 Oct 2010 22:43:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=neustar.biz; s=neustarbiz; t=1286516671; x=1601872667; q=dns/txt; h=From:Date:Subject:Message-ID:Content-Language: Content-Type:Content-Transfer-Encoding; bh=VeeWS3p/XuopA+UBfStta gRoOhmRU6QmQp6xjhfprO4=; b=bbTIVD2+pHTfDOmLAJ4n5FepK5KUdyQLOdei5 hnFTt/NWLKWwpejHsfnalSbt4beJNAFooX7sxCEa7zneqDhww== Received: from ([10.31.13.229]) by chihiron1.nc.neustar.com with ESMTP with TLS id 5202942.32253206; Fri, 08 Oct 2010 01:44:30 -0400 Received: from STNTEXCH01.cis.neustar.com ([fe80::31b6:4d09:2ada:e6c0]) by STNTEXCHHT02.cis.neustar.com ([::1]) with mapi; Fri, 8 Oct 2010 01:44:29 -0400 From: "Ali, Syed Wasim" To: Otmar Lendl , IETF DRINKS WG Date: Fri, 8 Oct 2010 01:44:27 -0400 Thread-Topic: [drinks] TN / TNRange / TNPrefix Thread-Index: ActVFiUPszsPM8czRS6uJOCKZmQ1KARlbmGk Message-ID: In-Reply-To: <4C912EFF.2090304@nic.at> Accept-Language: en-US Content-Language: en X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US x-ems-proccessed: R64IxjzeHPwwd+efoj3ZcA== x-ems-stamp: n2Ne/iMtM33D+YeHZnY8mA== Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [drinks] TN / TNRange / TNPrefix X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Oct 2010 05:43:31 -0000 Otmar, Thanks for your suggestion and a quick follow-up on the action item. On yesterday's call, we caught up on this issue and had a lively discussion. Introducing a new type TNPrefix will make it clear that the included "tn" parameter is a fragment and not a subscriber number. This is potentially useful for not only ONP, but also for regions or national significant numbers that qualify for closed number plan (e.g. TNPrefix=3D{+1201} ). Another option that we discussed was to re-use TNRange for this purpose and make the 'endTn' parameter optional. And while this will do the job, the TNPrefix makes the intent clear and IMHO a better way to go. If we do adopt the new TNPrefix, the only update to the XML schema will be the definition of the new structure as below, thanks, -Syed On 9/15/10 4:39 PM, "Otmar Lendl" wrote: >=20 >=20 > I just picked up an action item during the interim: >=20 > We were talking about how to denote prefixes (esp. for open numbering > plan), and David and I suggested that it's better and less likely to caus= e > confusion if there were an explicit prefix object, and not just a TNRange > with some attribute to flag it's actually a prefix. >=20 > Here is an off-the-cuff xsd proposal: >=20 > > > > > > > > > >=20 > > > > > > > > > > >=20 > > > > > > > > > > > >=20 > cheers, >=20 > otmar > -- > // Otmar Lendl , T: +43 1 5056416 - 33, F: - 933 // > _______________________________________________ > drinks mailing list > drinks@ietf.org > https://www.ietf.org/mailman/listinfo/drinks From root@core3.amsl.com Tue Oct 12 14:45:03 2010 Return-Path: X-Original-To: drinks@ietf.org Delivered-To: drinks@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 3174F3A6869; Tue, 12 Oct 2010 14:45:02 -0700 (PDT) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20101012214503.3174F3A6869@core3.amsl.com> Date: Tue, 12 Oct 2010 14:45:02 -0700 (PDT) Cc: drinks@ietf.org Subject: [drinks] I-D Action:draft-ietf-drinks-spprov-02.txt X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Oct 2010 21:45:03 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Data for Reachability of Inter/tra-NetworK SIP Working Group of the IETF. Title : Session Peering Provisioning Protocol Author(s) : J. Mule, et al. Filename : draft-ietf-drinks-spprov-02.txt Pages : 97 Date : 2010-10-12 This document defines a protocol for provisioning session establishment data into Session Data Registries and SIP Service Provider data stores. The provisioned data is typically used by various network elements for session peering. This document describes the Session Peering Provisioning Protocol used by clients to provision registries. The document provides a set of guiding principles for the design of this protocol including extensibility and independent transport definitions, a basic data model and an XML Schema Document. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-drinks-spprov-02.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-drinks-spprov-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2010-10-12143557.I-D@ietf.org> --NextPart-- From sumanth@cablelabs.com Thu Oct 14 08:33:18 2010 Return-Path: X-Original-To: drinks@core3.amsl.com Delivered-To: drinks@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1BDB13A6987 for ; Thu, 14 Oct 2010 08:33:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.307 X-Spam-Level: X-Spam-Status: No, score=0.307 tagged_above=-999 required=5 tests=[AWL=0.770, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rgyg0FpQmQYJ for ; Thu, 14 Oct 2010 08:33:17 -0700 (PDT) Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by core3.amsl.com (Postfix) with ESMTP id 991CA3A695D for ; Thu, 14 Oct 2010 08:33:00 -0700 (PDT) Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.4/8.14.4) with ESMTP id o9EFYIW0003087 for ; Thu, 14 Oct 2010 09:34:18 -0600 Received: from srvxchg.cablelabs.com (10.5.0.15) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com); Thu, 14 Oct 2010 09:34:18 -0700 (MST) X-Virus-Status: clean(F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com) Received: from srvxchg.cablelabs.com ([10.5.0.15]) by srvxchg ([10.5.0.15]) with mapi; Thu, 14 Oct 2010 09:34:18 -0600 From: Sumanth Channabasappa To: "Drinks@ietf.org" Date: Thu, 14 Oct 2010 09:34:17 -0600 Thread-Topic: Rough Notes and AI list from the call on 10/14 Thread-Index: ActQMdwXrcsFb0LURMebPnHWJtIGmQQyesrgAVBYIVABXfP+AA== Message-ID: <76AC5FEF83F1E64491446437EA81A61F7D201D949B@srvxchg> References: <76AC5FEF83F1E64491446437EA81A61F7D1FF40829@srvxchg> <76AC5FEF83F1E64491446437EA81A61F7D201D8C3C@srvxchg> <76AC5FEF83F1E64491446437EA81A61F7D201D9007@srvxchg> In-Reply-To: <76AC5FEF83F1E64491446437EA81A61F7D201D9007@srvxchg> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Approved: ondar Subject: [drinks] Rough Notes and AI list from the call on 10/14 X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Oct 2010 15:33:18 -0000 IETF DRINKS DESIGN TEAM CALL=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D 10/14/2010, 10:00a-10:40a (Eastern)/8:00a-8:40a (Mountain) =20 Participants =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D - Jean-Francois Mule - Ken Cartwright - Syed Ali - Sumanth Channabasappa=20 =20 =20 ACTION ITEMS=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D + [Authors] Review the I-D and see if it requires any changes; - [Syed] Make progress regarding the TNPrefix data structure=20 - [Ken] Submit a revision to the transport-specific I-D=20 AGENDA =3D=3D=3D=3D=3D=3D 1. What did not make it into the current revision (Ken, Syed, Jean-Francois= )=20 2. Next steps and plan for Beijing NOTES =3D=3D=3D=3D=3D 1. What did not make it into the current revision (Ken, Syed, Jean-Francois= )=20 + The following are items we still need to discuss a) [Ken] Data validation rules for the specified data elements b) [Ken] File based protocol c) [Syed] Support for Global SPID=20 d) [Syed] TNPrefix (see email exchange between Syed and Otmar) Discussions led to the following agreements: - a) and b) can be independent of the current I-D - Nothing needs to be done about c) at this point in time - We should discuss and resolve d) (Syed volunteered to complete this; e= xpect follow-up emails on the DRINKS mailing list) 2. Next steps and plan for Beijing =20 - The next step for the protocol document is for the authors to see if ther= e are any final changes (in addition to #d, above) and produce a revision. = After this, the design team may request WGLC - Alex has made changes to the use cases document to incorporate comments r= eceived thus far. Sumanth to collaborate on this, and submit an update befo= re the cutoff - Sumanth requested agenda items for Beijing; the general recommendation wa= s to make the protocol work the primary focus = From sumanth@cablelabs.com Thu Oct 14 08:38:23 2010 Return-Path: X-Original-To: drinks@core3.amsl.com Delivered-To: drinks@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7B6393A69A6 for ; Thu, 14 Oct 2010 08:38:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.279 X-Spam-Level: X-Spam-Status: No, score=0.279 tagged_above=-999 required=5 tests=[AWL=0.741, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zB669v7JsY8p for ; Thu, 14 Oct 2010 08:38:22 -0700 (PDT) Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by core3.amsl.com (Postfix) with ESMTP id 5D48D3A6997 for ; Thu, 14 Oct 2010 08:38:22 -0700 (PDT) Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.4/8.14.4) with ESMTP id o9EFdem6004012 for ; Thu, 14 Oct 2010 09:39:40 -0600 Received: from srvxchg.cablelabs.com (10.5.0.15) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com); Thu, 14 Oct 2010 09:39:40 -0700 (MST) X-Virus-Status: clean(F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com) Received: from srvxchg.cablelabs.com ([10.5.0.15]) by srvxchg ([10.5.0.15]) with mapi; Thu, 14 Oct 2010 09:39:40 -0600 From: Sumanth Channabasappa To: "Drinks@ietf.org" Date: Thu, 14 Oct 2010 09:39:39 -0600 Thread-Topic: Update to the protocol document Thread-Index: ActrtgOFL8MNbrg0RzKGHejgo6YJPw== Message-ID: <76AC5FEF83F1E64491446437EA81A61F7D201D94A0@srvxchg> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_76AC5FEF83F1E64491446437EA81A61F7D201D94A0srvxchg_" MIME-Version: 1.0 X-Approved: ondar Subject: [drinks] Update to the protocol document X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Oct 2010 15:38:24 -0000 --_000_76AC5FEF83F1E64491446437EA81A61F7D201D94A0srvxchg_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Folks, The protocol I-D authors have submitted a revision to the I-D: https://datatracker.ietf.org/doc/draft-ietf-drinks-spprov/ This is based on the resolutions at the interim F2F (notes shared on 10/6),= comments and discussions on the mailing list and the design team discussio= ns (notes have been shared on the call). The authors believe that most issu= es have been resolved, and comments incorporated. They will follow-up with = any unresolved comments (e.g., the TNPrefix data structure) on this mailing= list. Please review and share your thoughts and comments. Thanks! - S --_000_76AC5FEF83F1E64491446437EA81A61F7D201D94A0srvxchg_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Folks,
 
The protocol I-D= authors=20 have submitted a revision to the I-D:
 
https:/= /datatracker.ietf.org/doc/draft-ietf-drinks-spprov/
 
 
This is based on= the=20 resolutions at the interim F2F (notes shared on 10/6), comments and discuss= ions=20 on the mailing list and the design team discussions (notes have been shared= on=20 the call). The authors believe that most issues have been resolved, and=20 comments incorporated. They will follow-up with=20 any unresolved comments (e.g., the TNPrefix data structure) on th= is=20 mailing list. 
 
Please review an= d share=20 your thoughts and comments.
 
Thanks!
- S
 
--_000_76AC5FEF83F1E64491446437EA81A61F7D201D94A0srvxchg_-- From sumanth@cablelabs.com Wed Oct 20 14:56:17 2010 Return-Path: X-Original-To: drinks@core3.amsl.com Delivered-To: drinks@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 688B63A6916 for ; Wed, 20 Oct 2010 14:56:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.181 X-Spam-Level: * X-Spam-Status: No, score=1.181 tagged_above=-999 required=5 tests=[AWL=-0.215, BAYES_20=-0.74, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OwmfAsS9ty6m for ; Wed, 20 Oct 2010 14:56:16 -0700 (PDT) Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by core3.amsl.com (Postfix) with ESMTP id A88BB3A65A5 for ; Wed, 20 Oct 2010 14:56:16 -0700 (PDT) Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.4/8.14.4) with ESMTP id o9KLvod7002685 for ; Wed, 20 Oct 2010 15:57:50 -0600 Received: from srvxchg.cablelabs.com (10.5.0.15) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com); Wed, 20 Oct 2010 15:57:49 -0700 (MST) X-Virus-Status: clean(F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com) Received: from srvxchg.cablelabs.com ([10.5.0.15]) by srvxchg ([10.5.0.15]) with mapi; Wed, 20 Oct 2010 15:57:50 -0600 From: Sumanth Channabasappa To: "Drinks@ietf.org" Date: Wed, 20 Oct 2010 15:57:47 -0600 Thread-Topic: FYI: DRINKS will now meet on WED instead of FRI Thread-Index: ActwodTjlr0C6xnnQma4ClpBfbT04w== Message-ID: <76AC5FEF83F1E64491446437EA81A61F7D20315592@srvxchg> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Approved: ondar Subject: [drinks] FYI: DRINKS will now meet on WED instead of FRI X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Oct 2010 21:56:17 -0000 Folks, =20 As an FYI, the DRINKS WG meeting in Beijing has been rescheduled for WED, i= nstead of FRI. =20 --- DRINKS Session 1 (2 hours) Wednesday, Morning Session I 0900-1130 Room Name: Valley Ballroom B --- =20 - S From syed.ali@neustar.biz Thu Oct 21 08:16:18 2010 Return-Path: X-Original-To: drinks@core3.amsl.com Delivered-To: drinks@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A26A83A68AD for ; Thu, 21 Oct 2010 08:16:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.751 X-Spam-Level: X-Spam-Status: No, score=-0.751 tagged_above=-999 required=5 tests=[AWL=1.295, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bXXiplo67qNV for ; Thu, 21 Oct 2010 08:16:17 -0700 (PDT) Received: from neustar.com (keys.neustar.biz [156.154.17.104]) by core3.amsl.com (Postfix) with ESMTP id EE39F3A67CF for ; Thu, 21 Oct 2010 08:16:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=neustar.biz; s=neustarbiz; t=1287674270; x=1603032711; q=dns/txt; h=From:Date:Subject:Message-ID:Content-Language: Content-Type:Content-Transfer-Encoding; bh=JXPMlI2mPEOCTpGvDJkFy 6kApxSCVRE/teZnqe7p7AM=; b=o+aDXR1MUyMHUGi+lflMIwNVuFmZzWBfAT405 YsppfnzOT/IAyiMcvWdncKDcL2pZdeFiS48Xa0Hf8y4X+Jawg== Received: from ([10.31.13.229]) by stihiron1.va.neustar.com with ESMTP with TLS id G6K7MJ1.15714009; Thu, 21 Oct 2010 11:17:49 -0400 Received: from STNTEXCH01.cis.neustar.com ([fe80::31b6:4d09:2ada:e6c0]) by STNTEXCHHT02.cis.neustar.com ([::1]) with mapi; Thu, 21 Oct 2010 11:17:49 -0400 From: "Ali, Syed Wasim" To: Otmar Lendl , IETF DRINKS WG Date: Thu, 21 Oct 2010 11:14:23 -0400 Thread-Topic: [drinks] TN / TNRange / TNPrefix Thread-Index: ActVFiUPszsPM8czRS6uJOCKZmQ1KARlbmGkAqGxcqA= Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US x-ems-proccessed: R64IxjzeHPwwd+efoj3ZcA== x-ems-stamp: ECWcozw/eXxu5/YMAtYuHQ== Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [drinks] TN / TNRange / TNPrefix X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Oct 2010 15:16:18 -0000 Otmar, Just a quick update on where things stand at the moment. The following changes went through a review in the design team and they will be part of the next spprov revision. - Introduced the TN prefix definition called TNPType in the schema. The nam= e is consistent with the choice of name for TN range as TNRType. - Based on earlier consensus (from Denver interim meeting f2f), TNRType now extends PubIdType and not TNType. - Pub ID operations section now has coverage for TNPType - The TNRType examples in the examples sections are updated to reflect the change from element name to . - A new example is added to show use of TNPType. thanks, -Syed On 10/8/10 1:44 AM, "Syed Ali" wrote: >=20 >=20 > Otmar, >=20 > Thanks for your suggestion and a quick follow-up on the action item. On > yesterday's call, we caught up on this issue and had a lively discussion. > Introducing a new type TNPrefix will make it clear that the included "tn" > parameter is a fragment and not a subscriber number. This is potentially > useful for not only ONP, but also for regions or national significant > numbers that qualify for closed number plan (e.g. TNPrefix=3D{+1201} ). >=20 > Another option that we discussed was to re-use TNRange for this purpose a= nd > make the 'endTn' parameter optional. And while this will do the job, the > TNPrefix makes the intent clear and IMHO a better way to go. >=20 > If we do adopt the new TNPrefix, the only update to the XML schema will b= e > the definition of the new structure as below, >=20 > > > > > >=20 > thanks, >=20 > -Syed >=20 >=20 > On 9/15/10 4:39 PM, "Otmar Lendl" wrote: >=20 >>=20 >>=20 >> I just picked up an action item during the interim: >>=20 >> We were talking about how to denote prefixes (esp. for open numbering >> plan), and David and I suggested that it's better and less likely to cau= se >> confusion if there were an explicit prefix object, and not just a TNRang= e >> with some attribute to flag it's actually a prefix. >>=20 >> Here is an off-the-cuff xsd proposal: >>=20 >> >> >> >> >> >> >> >> >> >>=20 >> >> >> >> >> >> >> >> >> >> >>=20 >> >> >> >> >> >> >> >> >> >> >> >>=20 >> cheers, >>=20 >> otmar >> -- >> // Otmar Lendl , T: +43 1 5056416 - 33, F: - 933 // >> _______________________________________________ >> drinks mailing list >> drinks@ietf.org >> https://www.ietf.org/mailman/listinfo/drinks >=20 > _______________________________________________ > drinks mailing list > drinks@ietf.org > https://www.ietf.org/mailman/listinfo/drinks From sumanth@cablelabs.com Thu Oct 21 10:01:39 2010 Return-Path: X-Original-To: drinks@core3.amsl.com Delivered-To: drinks@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 14F693A6A3D for ; Thu, 21 Oct 2010 10:01:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.559 X-Spam-Level: X-Spam-Status: No, score=0.559 tagged_above=-999 required=5 tests=[AWL=0.422, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, J_CHICKENPOX_26=0.6] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id epq++CmnymmS for ; Thu, 21 Oct 2010 10:01:38 -0700 (PDT) Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by core3.amsl.com (Postfix) with ESMTP id 0669F3A6A4E for ; Thu, 21 Oct 2010 10:01:37 -0700 (PDT) Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.4/8.14.4) with ESMTP id o9LH3D7j005051 for ; Thu, 21 Oct 2010 11:03:13 -0600 Received: from srvxchg.cablelabs.com (10.5.0.15) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com); Thu, 21 Oct 2010 11:03:13 -0700 (MST) X-Virus-Status: clean(F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com) Received: from srvxchg.cablelabs.com ([10.5.0.15]) by srvxchg ([10.5.0.15]) with mapi; Thu, 21 Oct 2010 11:03:13 -0600 From: Sumanth Channabasappa To: "Drinks@ietf.org" Date: Thu, 21 Oct 2010 11:03:12 -0600 Thread-Topic: Rough Notes and AI list from the call on 10/21 Thread-Index: ActQMdwXrcsFb0LURMebPnHWJtIGmQQyesrgAVBYIVABXfP+AAFjMzQw Message-ID: <76AC5FEF83F1E64491446437EA81A61F7D203155ED@srvxchg> References: <76AC5FEF83F1E64491446437EA81A61F7D1FF40829@srvxchg> <76AC5FEF83F1E64491446437EA81A61F7D201D8C3C@srvxchg> <76AC5FEF83F1E64491446437EA81A61F7D201D9007@srvxchg> <76AC5FEF83F1E64491446437EA81A61F7D201D949B@srvxchg> In-Reply-To: <76AC5FEF83F1E64491446437EA81A61F7D201D949B@srvxchg> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Approved: ondar Subject: [drinks] Rough Notes and AI list from the call on 10/21 X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Oct 2010 17:01:39 -0000 IETF DRINKS DESIGN TEAM CALL=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D 10/21/2010, 10:00a-10:30a (Eastern)/8:00a-8:30a (Mountain) =20 Participants =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D - Syed Ali - Jean-Francois Mule - Manjul Maharishi - Ken Cartwright - Sumanth Channabasappa=20 =20 =20 ACTION ITEMS=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D - [Syed] Submit updated protocol I-D - [Ken] Submit a revision to the transport-specific I-D=20 - [Sumanth] Submit a revision to the use cases I-D=20 AGENDA =3D=3D=3D=3D=3D=3D 1. Final changes to the protocol (see the email from Syed on 10/18 related = to the TNPrefix) 2. Update regarding Beijing NOTES =3D=3D=3D=3D=3D 1. Final changes to the protocol (see the email from Syed on 10/18 related = to the TNPrefix) =3D Syed presented the following changes related to the TNPrefix discuss= ion on the mailing list. - Introduced the TN prefix definition called TNPType in the schema. T= he name is consistent with the choice for TN range as TNRType. - Updated the model diagram to show "TNP" as well. - TNPType extends PubIdType and its only mandatory member is "tnPrefi= x" of type xs:string. - TNRType extends PubIdType as well and the start tn of the TN range = is called "startTn". - Pub ID operations section has been modified to include TN prefix de= scription. The TN range references have been updated as well. - The TNRType examples in the examples sections are updated to reflec= t the change from element name to . - A new example is added to show use of TNPType. Resolution: The design team agreed with the changes, Syed will also presen= t this on the mailing list for any further comments. =3D Syed questioned the removal of svcs field from the egress route obje= ct - Ken explained the changes from a few weeks ago (see notes from 9/3= 0), where we associated egress routes directly with the record routes, remo= ving the necessity for the svcs field.=20 - Based on the explanation, this is not an issue. Resolution: No changes 2. Update regarding Beijing =3D The WG meeting will be held on WED, as shared on the WG mailing list =3D The design team plans to discuss presentations, review feedback and = such in the weekly calls leading up to the meeting. = From root@core3.amsl.com Fri Oct 22 11:15:29 2010 Return-Path: X-Original-To: drinks@ietf.org Delivered-To: drinks@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 1DC353A6920; Fri, 22 Oct 2010 11:15:05 -0700 (PDT) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20101022181508.1DC353A6920@core3.amsl.com> Date: Fri, 22 Oct 2010 11:15:05 -0700 (PDT) Cc: drinks@ietf.org Subject: [drinks] I-D Action:draft-ietf-drinks-spprov-03.txt X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Oct 2010 18:15:31 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Data for Reachability of Inter/tra-NetworK SIP Working Group of the IETF. Title : Session Peering Provisioning Protocol Author(s) : J. Mule, et al. Filename : draft-ietf-drinks-spprov-03.txt Pages : 99 Date : 2010-10-22 This document defines a protocol for provisioning session establishment data into Session Data Registries and SIP Service Provider data stores. The provisioned data is typically used by various network elements for session peering. This document describes the Session Peering Provisioning Protocol used by clients to provision registries. The document provides a set of guiding principles for the design of this protocol including extensibility and independent transport definitions, a basic data model and an XML Schema Document. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-drinks-spprov-03.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-drinks-spprov-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2010-10-22110410.I-D@ietf.org> --NextPart-- From kcartwright@tnsi.com Mon Oct 25 11:34:50 2010 Return-Path: X-Original-To: drinks@core3.amsl.com Delivered-To: drinks@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D2CFF3A6867 for ; Mon, 25 Oct 2010 11:34:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.4 X-Spam-Level: X-Spam-Status: No, score=-0.4 tagged_above=-999 required=5 tests=[AWL=2.199, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pNH5JYdLqvak for ; Mon, 25 Oct 2010 11:34:49 -0700 (PDT) Received: from tnsi.com (relayus.tnsi.com [208.224.248.44]) by core3.amsl.com (Postfix) with ESMTP id 1356E3A66B4 for ; Mon, 25 Oct 2010 11:34:48 -0700 (PDT) Received: from ([172.17.7.231]) by relayus.tnsi.com with ESMTP with TLS id 4440551.48907192; Mon, 25 Oct 2010 14:36:31 -0400 Received: from TNS-MAIL-NA.win2k.corp.tnsi.com ([172.17.7.219]) by MAIL-HUB-NA.win2k.corp.tnsi.com ([172.17.7.231]) with mapi; Mon, 25 Oct 2010 14:36:31 -0400 From: "Cartwright, Ken" To: "Drinks@ietf.org" Date: Mon, 25 Oct 2010 14:36:30 -0400 Thread-Topic: New Version Notification for draft-ietf-drinks-sppp-over-soap-01 Thread-Index: Act0c2UZld7igIKeTMCSzW4yrQk36gAAB93g Message-ID: <754963199212404AB8E9CFCA6C3D0CDA260B3C0A60@TNS-MAIL-NA.win2k.corp.tnsi.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [drinks] FW: New Version Notification for draft-ietf-drinks-sppp-over-soap-01 X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Oct 2010 18:34:50 -0000 Fyi. -----Original Message----- From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org] Sent: Monday, October 25, 2010 2:34 PM To: Cartwright, Ken Subject: New Version Notification for draft-ietf-drinks-sppp-over-soap-01 A new version of I-D, draft-ietf-drinks-sppp-over-soap-01.txt has been succ= essfully submitted by Kenneth Cartwright and posted to the IETF repository. Filename: draft-ietf-drinks-sppp-over-soap Revision: 01 Title: SPPP Over SOAP and HTTP Creation_date: 2010-10-25 WG ID: drinks Number_of_pages: 17 Abstract: The Session Peering Provisioning Protocol (SPPP) is an XML protocol that exists to enable the provisioning of session establishment data into Session Data Registries or SIP Service Provider data stores. Sending XML data structures over Simple Object Access Protocol (SOAP) and HTTP(s) is a widely used, de-facto standard for messaging between elements of provisioning systems. Therefore the combination of SOAP and HTTP(s) as a transport for SPPP is a natural fit. The obvious benefits include leveraging existing industry expertise, leveraging existing standards, and a higher probability that existing provisioning systems can be more easily integrated with this protocol. This document describes the specification for transporting SPPP XML structures over SOAP and HTTP(s). The IETF Secretariat. This e-mail message is for the sole use of the intended recipient(s)and may contain confidential and privileged information of Transaction Network Serv= ices. Any unauthorised review, use, disclosure or distribution is prohibited. If = you are not the intended recipient, please contact the sender by reply e-mail a= nd destroy all copies of the original message. From root@core3.amsl.com Mon Oct 25 11:45:01 2010 Return-Path: X-Original-To: drinks@ietf.org Delivered-To: drinks@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 9921C3A63D3; Mon, 25 Oct 2010 11:45:01 -0700 (PDT) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20101025184501.9921C3A63D3@core3.amsl.com> Date: Mon, 25 Oct 2010 11:45:01 -0700 (PDT) Cc: drinks@ietf.org Subject: [drinks] I-D Action:draft-ietf-drinks-sppp-over-soap-01.txt X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Oct 2010 18:45:01 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Data for Reachability of Inter/tra-NetworK SIP Working Group of the IETF. Title : SPPP Over SOAP and HTTP Author(s) : K. Cartwright Filename : draft-ietf-drinks-sppp-over-soap-01.txt Pages : 17 Date : 2010-10-25 The Session Peering Provisioning Protocol (SPPP) is an XML protocol that exists to enable the provisioning of session establishment data into Session Data Registries or SIP Service Provider data stores. Sending XML data structures over Simple Object Access Protocol (SOAP) and HTTP(s) is a widely used, de-facto standard for messaging between elements of provisioning systems. Therefore the combination of SOAP and HTTP(s) as a transport for SPPP is a natural fit. The obvious benefits include leveraging existing industry expertise, leveraging existing standards, and a higher probability that existing provisioning systems can be more easily integrated with this protocol. This document describes the specification for transporting SPPP XML structures over SOAP and HTTP(s). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-drinks-sppp-over-soap-01.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-drinks-sppp-over-soap-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2010-10-25113336.I-D@ietf.org> --NextPart-- From sumanth@cablelabs.com Mon Oct 25 12:47:53 2010 Return-Path: X-Original-To: drinks@core3.amsl.com Delivered-To: drinks@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 995783A67AD for ; Mon, 25 Oct 2010 12:47:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.245 X-Spam-Level: X-Spam-Status: No, score=0.245 tagged_above=-999 required=5 tests=[AWL=0.708, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GTcrh5ntJqRv for ; Mon, 25 Oct 2010 12:47:39 -0700 (PDT) Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by core3.amsl.com (Postfix) with ESMTP id 4D4793A68D3 for ; Mon, 25 Oct 2010 12:47:39 -0700 (PDT) Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.4/8.14.4) with ESMTP id o9PJnOV3032530 for ; Mon, 25 Oct 2010 13:49:24 -0600 Received: from srvxchg.cablelabs.com (10.5.0.15) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com); Mon, 25 Oct 2010 13:49:24 -0700 (MST) X-Virus-Status: clean(F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com) Received: from srvxchg.cablelabs.com ([10.5.0.15]) by srvxchg ([10.5.0.15]) with mapi; Mon, 25 Oct 2010 13:49:24 -0600 From: Sumanth Channabasappa To: "Drinks@ietf.org" Date: Mon, 25 Oct 2010 13:49:23 -0600 Thread-Topic: New Version Notification for draft-ietf-drinks-usecases-requirements-04 Thread-Index: Act0fXphS6PIcareQdeLzNKLX+prXwAAC5CA Message-ID: <76AC5FEF83F1E64491446437EA81A61F7D203157D7@srvxchg> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Approved: ondar Subject: [drinks] FW: New Version Notification for draft-ietf-drinks-usecases-requirements-04 X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Oct 2010 19:47:53 -0000 FYI, we will follow-up with the specific changes in the next couple of days= ... - S -----Original Message----- From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]=20 Sent: Monday, October 25, 2010 1:46 PM To: Sumanth Channabasappa Subject: New Version Notification for draft-ietf-drinks-usecases-requiremen= ts-04=20 A new version of I-D, draft-ietf-drinks-usecases-requirements-04.txt has be= en successfully submitted by Sumanth Channabasappa and posted to the IETF r= epository. Filename: draft-ietf-drinks-usecases-requirements Revision: 04 Title: DRINKS Use cases and Protocol Requirements Creation_date: 2010-10-25 WG ID: drinks Number_of_pages: 24 Abstract: This document captures the use cases and associated requirements for interf= aces that provision session establishment data into SIP Service Provider co= mponents, to assist with session routing. Specifically, the current versio= n of this document focuses on the provisioning of one such element, termed = the registry. = =20 The IETF Secretariat. From root@core3.amsl.com Mon Oct 25 13:00:02 2010 Return-Path: X-Original-To: drinks@ietf.org Delivered-To: drinks@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 7C9873A6ACC; Mon, 25 Oct 2010 13:00:02 -0700 (PDT) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20101025200002.7C9873A6ACC@core3.amsl.com> Date: Mon, 25 Oct 2010 13:00:02 -0700 (PDT) Cc: drinks@ietf.org Subject: [drinks] I-D Action:draft-ietf-drinks-usecases-requirements-04.txt X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Oct 2010 20:00:02 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Data for Reachability of Inter/tra-NetworK SIP Working Group of the IETF. Title : DRINKS Use cases and Protocol Requirements Author(s) : S. Channabasappa Filename : draft-ietf-drinks-usecases-requirements-04.txt Pages : 24 Date : 2010-10-25 This document captures the use cases and associated requirements for interfaces that provision session establishment data into SIP Service Provider components, to assist with session routing. Specifically, the current version of this document focuses on the provisioning of one such element, termed the registry. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-drinks-usecases-requirements-04.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-drinks-usecases-requirements-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2010-10-25124547.I-D@ietf.org> --NextPart-- From syed.ali@neustar.biz Mon Oct 25 19:45:16 2010 Return-Path: X-Original-To: drinks@core3.amsl.com Delivered-To: drinks@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9BCB23A6A11 for ; Mon, 25 Oct 2010 19:45:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.348 X-Spam-Level: X-Spam-Status: No, score=-1.348 tagged_above=-999 required=5 tests=[AWL=1.251, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QYGtRMEYA7xo for ; Mon, 25 Oct 2010 19:44:58 -0700 (PDT) Received: from neustar.com (mx1.neustar.com [156.154.17.104]) by core3.amsl.com (Postfix) with ESMTP id 6CD303A6933 for ; Mon, 25 Oct 2010 19:44:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=neustar.biz; s=neustarbiz; t=1288061200; x=1603409023; q=dns/txt; h=From:Date:Subject:Message-ID:Content-Language: Content-Type:Content-Transfer-Encoding; bh=VkQcYbitJPDw4Zb8Ts9sn V2rGQ7kxAtGoiFjC/lE/S8=; b=PkvLqn9Q2n84116getp72l+Aj8jT78idxk3O4 xutM0TtYBdwa5OPqfyhyRdkPth3+02T0gW06Ox8PDJYGp/gRg== Received: from ([10.31.13.229]) by stihiron2.va.neustar.com with ESMTP with TLS id 5202732.38655663; Mon, 25 Oct 2010 22:46:39 -0400 Received: from STNTEXCH01.cis.neustar.com ([fe80::31b6:4d09:2ada:e6c0]) by STNTEXCHHT02.cis.neustar.com ([::1]) with mapi; Mon, 25 Oct 2010 22:46:39 -0400 From: "Ali, Syed Wasim" To: "drinks@ietf.org" Date: Mon, 25 Oct 2010 22:44:22 -0400 Thread-Topic: New Version Notification for draft-ietf-drinks-spprov-03 Thread-Index: ActyE8WqBev3DkZ/SpCl8V3TNGs5uQCo+vip Message-ID: <31582FA079F2AC4FBC8BA78B67C32AA7066611AE69@STNTEXCH01.cis.neustar.com> References: <20101022180411.1F97E3A6920@core3.amsl.com> In-Reply-To: <20101022180411.1F97E3A6920@core3.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US x-ems-proccessed: R64IxjzeHPwwd+efoj3ZcA== x-ems-stamp: ZIw4a87U4Czo5751O/JTVg== Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [drinks] FW: New Version Notification for draft-ietf-drinks-spprov-03 X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2010 02:45:17 -0000 Hi, New version of spprov ID was successfully posted on 10/22. Here are the cha= nges for this version: - Introduced the TN prefix definition called TNPType in the schema. The nam= e is consistent with the choice of name for TN range as TNRType. - Based on earlier consensus (from Denver interim meeting f2f), TNRType now extends PubIdType and not TNType. - Pub ID operations section now has coverage for TNPType - The TNRType examples in the examples sections are updated to reflect the change from element name to . - A new example is added to show use of TNPType. thanks, -Syed ________________________________________ From: IETF I-D Submission Tool [idsubmission@ietf.org] Sent: Friday, October 22, 2010 2:04 PM To: Ali, Syed Wasim Cc: jfm@cablelabs.com; kcartwright@tnsi.com; alexander.mayrhofer@enum.at Subject: New Version Notification for draft-ietf-drinks-spprov-03 A new version of I-D, draft-ietf-drinks-spprov-03.txt has been successfully= submitted by Syed Ali and posted to the IETF repository. Filename: draft-ietf-drinks-spprov Revision: 03 Title: Session Peering Provisioning Protocol Creation_date: 2010-10-22 WG ID: drinks Number_of_pages: 99 Abstract: This document defines a protocol for provisioning session establishment data into Session Data Registries and SIP Service Provider data stores. The provisioned data is typically used by various network elements for session peering. This document describes the Session Peering Provisioning Protocol used by clients to provision registries. The document provides a set of guiding principles for the design of this protocol including extensibility and independent transport definitions, a basic data model and an XML Schema Document. The IETF Secretariat.=