Subject: Re: [PEPPERMINT] FW: I-DACTION:draft-schwartz-speermint-provisioning-problem-00.txt
From: David Schwartz <[email-masked]>
To: "Elwell, John" <[email-masked]>
Cc: [email-masked]
Date: Sun, 25 Nov 2007 00:26:33 +0200
List-Id: Provisioning Extensions in Peering Registries for Multimedia INTerconnection <peppermint.ietf.org>

Hi john.

inline...

On Nov 21, 2007, at 7:02 PM, Elwell, John wrote:

> David,
>
> From an initial read, I am rather confused. There is a clearly defined
> split between SPEERMINT work and ENUM work, with ENUM converting a
> telephone number into a SIP URI,

DS: The draft is trying among other to point out that the exact  
meaning of the SIP URI returned in the response is vague and open to  
interpretation. Defining the meaning and context of data that is  
passed using the ENUM protocol is an open issue and one may argue  
that this belongs in the ENUM group. I am not convinced. As to  
whether or not this should be in the SPEERMINT group, this too is an  
open issue and it was my understanding that the BOF was formed to  
discuss this.

As a side point, using a SIP 302 redirect mechanism for said  
resolution is completely valid approach (in fact used quite often in  
practice) and has nothing to do with ENUM or NAPTR records so the  
relevance of ENUM is somewhat unclear.

> and SPEERMINT finding a SIP server, policy, etc.
> for the domain indicated in the SIP URI.

DS: I would like to quote from the charter as there seems to be some  
confusion. "... More specifically, SPEERMINT focuses on real-time  
session routing architectures and their associated use cases.  
Deliverables here include the specification of the various types of  
application flows, such as signaling and media flows, in such  
networks, and includes both trunking and peer-to-peer flows... The  
most focused deliverables of SPEERMINT are best current practices  
regarding exchange of real-time sessions among VoIP and other real- 
time application service providers and, in particular, how such calls  
are routed...  While the the ENUM Working Group is primarily  
concerned with the structure and lookup of data for the translation  
of E.164 numbers into URIs (RFC3761), SPEERMINT is concerned with the  
use of the resulting URI data, as well as non-ENUM-derived URI data,  
for use in signaling and routing of real-time sessions. "

While the charter does mention that SPEERMINT is concerned with "the  
use of the resulting URI data" none of the work to date has addressed  
this issue and it is unclear when and if it will. While I fully  
understand and support the current efforts with SPEERMINT to define  
the architectures and use cases as a foundation for future peering  
work I feel that the context, meaning and data model of the E.164  
resolution data as well as the provisioning of this data may well be  
out of scope for SPEERMINT.

> However, the draft
> seems to approach provisioning without due regard for that split,  
> i.e.,
> it seems to tackle provisioning in a way that allows a VSP to take a
> phone number as input and directly obtain the information it needs to
> route to an appropriate terminating VSP. Shouldn't we try to keep the
> two stages separate? Or have I misunderstood something?
>
> John
>
>> -----Original Message-----
>> From: Richard Shockey [mailto:[email-masked]]
>> Sent: 13 November 2007 20:21
>> To: [email-masked]
>> Subject: [PEPPERMINT] FW:
>> I-DACTION:draft-schwartz-speermint-provisioning-problem-00.txt
>>
>> I believe this is a document we will be discussing in
>> Vancouver at the BOF.
>> The references to spearmint was, I'm told somewhat
>> inadvertent on the part
>> of the authors.
>>
>>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>>
>>
>> 	Title		: Managing Client Voice Peering Provisioning
>> 	Author(s)	: D. Schwartz, et al.
>> 	Filename	:
>> draft-schwartz-speermint-provisioning-problem-00.txt
>> 	Pages		: 8
>> 	Date		: 2007-11-13
>> 	
>>    This document describes the type of data provisioned among Voice
>>    Service Providers.  This is in support of the service provider
>>    peering as defined by the Speermint WG.
>>
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-schwartz-speermint-p
>> rovisioning-pr
>> oblem-00.txt
>>
>> To remove yourself from the I-D Announcement list, send a message to
>> [email-masked] with the word unsubscribe in
>> the body of
>> the message.
>> You can also visit
>> https://www1.ietf.org/mailman/listinfo/I-D-announce
>> to change your subscription settings.
>>
>> Internet-Drafts are also available by anonymous FTP. Login with the
>> username "anonymous" and a password of your e-mail address. After
>> logging in, type "cd internet-drafts" and then
>> "get draft-schwartz-speermint-provisioning-problem-00.txt".
>>
>> A list of Internet-Drafts directories can be found in
>> http://www.ietf.org/shadow.html
>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>
>> Internet-Drafts can also be obtained by e-mail.
>>
>> Send a message to:
>> 	[email-masked].
>> In the body type:
>> 	"FILE
>> /internet-drafts/draft-schwartz-speermint-provisioning-problem
>> -00.txt".
>> 	
>> NOTE:	The mail server at ietf.org can return the document in
>> 	MIME-encoded form by using the "mpack" utility.  To use this
>> 	feature, insert the command "ENCODING mime" before the "FILE"
>> 	command.  To decode the response(s), you will need "munpack" or
>> 	a MIME-compliant mail reader.  Different MIME-compliant
>> mail readers
>> 	exhibit different behavior, especially when dealing with
>> 	"multipart" MIME messages (i.e. documents which have been split
>> 	up into multiple messages), so check your local documentation on
>> 	how to manipulate these messages.
>>
>> Below is the data which will enable a MIME compliant mail reader
>> implementation to automatically retrieve the ASCII version of the
>> Internet-Draft.
>>
>>
>> _______________________________________________
>> PEPPERMINT mailing list
>> [email-masked]
>> https://www1.ietf.org/mailman/listinfo/peppermint
>>

_______________________________________________
PEPPERMINT mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/peppermint

From: "Richard Shockey" <[email-masked]>
To: <[email-masked]>
Date: Fri, 23 Nov 2007 10:43:05 -0500
Subject: [PEPPERMINT] FINAL AGENDA PEPPERMINT BOF IETF 70

1 Hour -- I can accept last minute additions but time is short.

IETF 70 PEPPERMINT BOF Agenda

PEPPERMINT Session 1 (1 hour)
Thursday, Afternoon Session II 1510-1610 Room Name: Salon 2

Chair(s):

Richard Shockey <[email-masked]>
Tom Creighton  <[email-masked]>

RAI Director(s):

Jon Peterson [email-masked]
Cullen Jennings [email-masked]

Agenda Bashing. 

Presentation of the proposed charter. <Shockey> 10 min

1. Review of peppermint problem statement ( David Schwartz )

	Title		: Managing Client Voice Peering Provisioning
	Author(s)	: D. Schwartz, et al.
	Filename	:
draft-schwartz-speermint-provisioning-problem-00.txt
	Pages		: 8
	Date		: 2007-11-13
	
   This document describes the type of data provisioned among Voice
   Service Providers.  This is in support of the service provider
   peering as defined by the Speermint WG.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-schwartz-speermint-provisioning-pr
oblem-00.txt

2. 	Title		: ENUM Registry Interface Requirements
	Author(s)	: E. Lewis
	Filename	: draft-lewis-peppermint-enum-reg-if-01.txt
	Pages		: 0
	Date		: 2007-11-16
	
An ENUM registry interacts with various elements to maintain what is
essentially a telephone number to uniform (or a more modern version)
resource identifier.  The interfaces needed are identified in this
requirements document, as well as the requirements for the more generic
interfaces.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-lewis-peppermint-enum-reg-if-01.tx
t

3. Review of existing provisioning protocols in IETF especially RFC 4114
(S.Hollenbeck)

4. 4114 Experiences Joonhyung Lim [mailto:[email-masked]] 

General Discussion

The Usual Questions.

A. Is this a problem that the IETF needs to work on?

B. Who wants to work on this problem.

************

Peppermint BOF

Provisioning Extensions in Peering Registries for Multimedia
Interconnection.

Mailing Lists: 

  [email-masked]

General information about the mailing list is at:

  https://www1.ietf.org/mailman/listinfo/peppermint

Temporary Area Directorate: Real Time Applications (RAI)

Ultimate Area Directorate: TBD

BOF Purpose.

The ENUM and SPEERMINT working groups are working on various aspects of
Multi Media Interconnection. ENUM is specifically chartered to develop
protocols that involve the translation of E.164 numbers to URI's. 
 
SPEERMINT has been chartered to develop best current practices among
real-time application service providers and how such services interconnect
across domain boundaries.

It is clear from discussions in both working groups that Multi-Media
Interconnection will require various forms of data to be exchanged among
administrative domains outside the normal scope of establishing various
forms of a SIP session.

Such data exchanges might be provisioning of various forms of Registries
containing mappings of phone numbers to URI, policies surrounding the
admission to points of network interconnection,  trunking data and the
distribution of Registry data to various types of databases. 

Provisioning may include PBX to service provider data exchanges as well.

The purpose of the BOF is to determine the need and scope for such data
exchanges, what existing protocols need to be adapted to meet those needs
and the appropriate schema and queries are needed to facilitate such
exchanges.

The IETF has in the past done significant work on data exchanges among
various administrative entities. In particular the PROVREG working group
developed various schema and query mechanisms to facilitate the exchange of
data among domain name registries and registrars.

The ENUM Working group has adapted PROVREG working group protocols to
develop RFC 4114, which facilitates the provisioning of ENUM data in the DNS
tree.  However, there has been little adoption of RFC 4114, and many of the
participants of the SPEERMINT working group require both data models and
protocol features not found in RFC 4114.

The proposed PEPPERMINT working group will build upon the knowledge gained
from those efforts, and the intent of this proposed working group is to find
a provisioning solution for peering as defined by SPEERMINT. The final work
product(s) from this working group will be based upon XML.
   
Additionally, bias will be given to re-using either EPP, HTTP/REST,
HTTP/XML-RPC, or HTTP/SOAP.

Proposed Deliverables

Requirements for PEPPERMINT data exchanges.

Provisioning of PEPPERMINT data registries.

Provisioning of PEPPERMINT/ENUM data caches.

Richard Shockey
Director, Member of the Technical Staff
NeuStar
46000 Center Oak Plaza - Sterling, VA 20166
PSTN Office +1 571.434.5651 
PSTN Mobile: +1 703.593.2683
<mailto:richard(at)shockey.us> 
<mailto:richard.shockey(at)neustar.biz>

_______________________________________________
PEPPERMINT mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/peppermint

Date: Wed, 21 Nov 2007 17:02:45 +0000
From: "Elwell, John" <[email-masked]>
Subject: RE: [PEPPERMINT] FW: I-DACTION:draft-schwartz-speermint-provisioning-problem-00.txt
To: [email-masked], David Schwartz <[email-masked]>
Content-class: urn:content-classes:message
Cc: 

David,

>From an initial read, I am rather confused. There is a clearly defined
split between SPEERMINT work and ENUM work, with ENUM converting a
telephone number into a SIP URI, and SPEERMINT finding a SIP server,
policy, etc. for the domain indicated in the SIP URI. However, the draft
seems to approach provisioning without due regard for that split, i.e.,
it seems to tackle provisioning in a way that allows a VSP to take a
phone number as input and directly obtain the information it needs to
route to an appropriate terminating VSP. Shouldn't we try to keep the
two stages separate? Or have I misunderstood something?

John

> -----Original Message-----
> From: Richard Shockey [mailto:[email-masked]] 
> Sent: 13 November 2007 20:21
> To: [email-masked]
> Subject: [PEPPERMINT] FW: 
> I-DACTION:draft-schwartz-speermint-provisioning-problem-00.txt
> 
> I believe this is a document we will be discussing in 
> Vancouver at the BOF.
> The references to spearmint was, I'm told somewhat 
> inadvertent on the part
> of the authors.
> 
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> 
> 
> 	Title		: Managing Client Voice Peering Provisioning
> 	Author(s)	: D. Schwartz, et al.
> 	Filename	:
> draft-schwartz-speermint-provisioning-problem-00.txt
> 	Pages		: 8
> 	Date		: 2007-11-13
> 	
>    This document describes the type of data provisioned among Voice
>    Service Providers.  This is in support of the service provider
>    peering as defined by the Speermint WG.
> 
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-schwartz-speermint-p
> rovisioning-pr
> oblem-00.txt
> 
> To remove yourself from the I-D Announcement list, send a message to 
> [email-masked] with the word unsubscribe in 
> the body of 
> the message. 
> You can also visit 
> https://www1.ietf.org/mailman/listinfo/I-D-announce 
> to change your subscription settings.
> 
> Internet-Drafts are also available by anonymous FTP. Login with the 
> username "anonymous" and a password of your e-mail address. After 
> logging in, type "cd internet-drafts" and then 
> "get draft-schwartz-speermint-provisioning-problem-00.txt".
> 
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html 
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> Internet-Drafts can also be obtained by e-mail.
> 
> Send a message to:
> 	[email-masked].
> In the body type:
> 	"FILE
> /internet-drafts/draft-schwartz-speermint-provisioning-problem
> -00.txt".
> 	
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant 
> mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
> 
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> 
> 
> _______________________________________________
> PEPPERMINT mailing list
> [email-masked]
> https://www1.ietf.org/mailman/listinfo/peppermint
> 

_______________________________________________
PEPPERMINT mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/peppermint

From: "Richard Shockey" <[email-masked]>
To: <[email-masked]>
Date: Fri, 16 Nov 2007 12:55:04 -0500
Subject: [PEPPERMINT] FW: I-D ACTION:draft-lewis-peppermint-enum-reg-if-01.txt 

One additional document etc.

-----Original Message-----
From: [email-masked] [mailto:[email-masked]] 
Sent: Friday, November 16, 2007 12:15 PM
To: [email-masked]
Subject: I-D ACTION:draft-lewis-peppermint-enum-reg-if-01.txt 

A New Internet-Draft is available from the on-line Internet-Drafts
directories.

	Title		: ENUM Registry Interface Requirements
	Author(s)	: E. Lewis
	Filename	: draft-lewis-peppermint-enum-reg-if-01.txt
	Pages		: 0
	Date		: 2007-11-16
	
An ENUM registry interacts with various elements to maintain what is
essentially a telephone number to uniform (or a more modern version)
resource identifier.  The interfaces needed are identified in this
requirements document, as well as the requirements for the more generic
interfaces.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-lewis-peppermint-enum-reg-if-01.tx
t

To remove yourself from the I-D Announcement list, send a message to 
[email-masked] with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-lewis-peppermint-enum-reg-if-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	[email-masked].
In the body type:
	"FILE /internet-drafts/draft-lewis-peppermint-enum-reg-if-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

_______________________________________________
PEPPERMINT mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/peppermint

Date: Fri, 16 Nov 2007 13:57:25 +0800
To: [email-masked]
From: Edward Lewis <[email-masked]>
Cc: 
Subject: [PEPPERMINT] resubmitting a requirements draft

FYI -

I'm going to resubmit the following draft without edits because it has expired.

http://tools.ietf.org/html/draft-lewis-peppermint-enum-reg-if-00

The first time around there were a few comments made on the draft, 
for the most part summarized the following links. I should 
incorporate them but given the "perfect storm" of the BoF being 
schedule, the submission deadline, and a vacation, I haven't...

http://www1.ietf.org/mail-archive/web/peppermint/current/msg00022.html
http://www1.ietf.org/mail-archive/web/peppermint/current/msg00058.html

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis                                                +1-571-434-5468
NeuStar

Think glocally.  Act confused.

_______________________________________________
PEPPERMINT mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/peppermint

From: "Richard Shockey" <[email-masked]>
To: <[email-masked]>
Date: Wed, 14 Nov 2007 14:18:05 -0500
Subject: [PEPPERMINT] Agenda as of 14 November 2007

IETF 70 PEPPERMINT BOF Agenda

PEPPERMINT Session 1 (1 hour)
Thursday, Afternoon Session II 1510-1610 Room Name: Salon 2

Chair(s):

Richard Shockey <[email-masked]>
Tom Creighton  <[email-masked]>

RAI Director(s):

Jon Peterson [email-masked]
Cullen Jennings [email-masked]

Agenda Bashing. 

Presentation of the proposed charter. <Shockey> 10 min

1. Review of peppermint problem statement ( David Schwartz )

	Title		: Managing Client Voice Peering Provisioning
	Author(s)	: D. Schwartz, et al.
	Filename	:
draft-schwartz-speermint-provisioning-problem-00.txt
	Pages		: 8
	Date		: 2007-11-13
	
   This document describes the type of data provisioned among Voice
   Service Providers.  This is in support of the service provider
   peering as defined by the Speermint WG.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-schwartz-speermint-provisioning-pr
oblem-00.txt

2. Review of existing provisioning protocols in IETF especially RFC 4114
(S.Hollenbeck)

3. 4114 Experiences Joonhyung Lim [mailto:[email-masked]] 

General Discussion

The Usual Questions.

A. Is this a problem that the IETF needs to work on?

B. Who wants to work on this problem.

************

Peppermint BOF

Provisioning Extensions in Peering Registries for Multimedia
Interconnection.

Mailing Lists: 

  [email-masked]

General information about the mailing list is at:

  https://www1.ietf.org/mailman/listinfo/peppermint

Temporary Area Directorate: Real Time Applications (RAI)

Ultimate Area Directorate: TBD

BOF Purpose.

The ENUM and SPEERMINT working groups are working on various aspects of
Multi Media Interconnection. ENUM is specifically chartered to develop
protocols that involve the translation of E.164 numbers to URI's. 
 
SPEERMINT has been chartered to develop best current practices among
real-time application service providers and how such services interconnect
across domain boundaries.

It is clear from discussions in both working groups that Multi-Media
Interconnection will require various forms of data to be exchanged among
administrative domains outside the normal scope of establishing various
forms of a SIP session.

Such data exchanges might be provisioning of various forms of Registries
containing mappings of phone numbers to URI, policies surrounding the
admission to points of network interconnection,  trunking data and the
distribution of Registry data to various types of databases. 

Provisioning may include PBX to service provider data exchanges as well.

The purpose of the BOF is to determine the need and scope for such data
exchanges, what existing protocols need to be adapted to meet those needs
and the appropriate schema and queries are needed to facilitate such
exchanges.

The IETF has in the past done significant work on data exchanges among
various administrative entities. In particular the PROVREG working group
developed various schema and query mechanisms to facilitate the exchange of
data among domain name registries and registrars.

The ENUM Working group has adapted PROVREG working group protocols to
develop RFC 4114, which facilitates the provisioning of ENUM data in the DNS
tree.  However, there has been little adoption of RFC 4114, and many of the
participants of the SPEERMINT working group require both data models and
protocol features not found in RFC 4114.

The proposed PEPPERMINT working group will build upon the knowledge gained
from those efforts, and the intent of this proposed working group is to find
a provisioning solution for peering as defined by SPEERMINT. The final work
product(s) from this working group will be based upon XML.
   
Additionally, bias will be given to re-using either EPP, HTTP/REST,
HTTP/XML-RPC, or HTTP/SOAP.

Proposed Deliverables

Richard Shockey
Director, Member of the Technical Staff
NeuStar
46000 Center Oak Plaza - Sterling, VA 20166
PSTN Office +1 571.434.5651 
PSTN Mobile: +1 703.593.2683
<mailto:richard(at)shockey.us> 
<mailto:richard.shockey(at)neustar.biz>

_______________________________________________
PEPPERMINT mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/peppermint

From: "Richard Shockey" <[email-masked]>
To: <[email-masked]>
Subject: FW: [PEPPERMINT] VERSION 00 PEPPERMINT BOF AGENDA
Date: Wed, 14 Nov 2007 10:37:34 -0500

This is a multipart message in MIME format.

--===============1427654896==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0D28_01C826AA.5EC51810"
Content-Language: en-us

This is a multipart message in MIME format.

------=_NextPart_000_0D28_01C826AA.5EC51810
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I think we can have a short presentation on this .very short since we only
have 1 hour.

  _____  

From: Joonhyung Lim [mailto:[email-masked]] 
Sent: Monday, November 12, 2007 12:47 AM
To: [email-masked]; [email-masked]
Subject: Re: [PEPPERMINT] VERSION 00 PEPPERMINT BOF AGENDA

Dear Richard

I'm really happy to comment on this BOF that I've been waiting for, since I
noticed some needs from industries through KR infrastructure ENUM trial in
2006. 

About a charter, IMHO, I think it would be better adding a example on
paragraph below, to clarify differences between 4114 and new one. 

>However, there has been little adoption of RFC 4114, and many of the
>participants of the SPEERMINT working group require both data models and
>protocol features not found in RFC 4114."

"However, there has been little adoption of RFC 4114, and many of the
participants of the SPEERMINT working group require both data models and
protocol features not found in RFC 4114, such as provisioning number prefix
or number blocks"

Actually, this example also mentioned in "PEPPERMINT Problem Statement"
draft. 

And if there is ok, I might have short presentation about provisioning issue
when we used 4114 during KR ENUM trial in 2006. It mostly leans to comments
from several players such as KR VSPs, PSTN carriers, and etc.

Thanks.

Joonhyung Lim, NIDA

-------------------------------------------------------------

 

COMMENTS PLEASE ESPECIALLY ON THE PROPOSED CHARTER

If anyone wants to present anyting let me or Tom know.

**********************************

IETF 70 PEPPERMINT BOF Agenda

PEPPERMINT Session 1 (1 hour)
Thursday, Afternoon Session II 1510-1610 Room Name: Salon 2

Chair(s):

Richard Shockey <richard.shockey at neustar.biz>
Tom Creighton  <tom_creighton at cable.comcast.com>

RAI Director(s):

Jon Peterson jon.peterson at neustar.biz
Cullen Jennings fluffy at cisco.com

Agenda Bashing. 

Presentation of the proposed charter. <Shockey> 10 min

1. Review of existing provisioning protocols in IETF especially RFC 4114
(S.Hollenbeck)

2. Review of peppermint problem statement ( David Schwartz )  ID
forthcoming.

General Discussion

The Usual Questions.

A. Is this a problem that the IETF needs to work on?

B. Are people willing to work on this problem?

************

Peppermint BOF

Provisioning Extensions in Peering Registries for Multimedia
Interconnection.

Mailing Lists: 

  peppermint at ietf.org

General information about the mailing list is at:

  https://www1.ietf.org/mailman/listinfo/peppermint

Temporary Area Directorate: Real Time Applications (RAI)

Ultimate Area Directorate: TBD

BOF Purpose.

The ENUM and SPEERMINT working groups are working on various aspects of
Multi Media Interconnection. ENUM is specifically chartered to develop
protocols that involve the translation of E.164 numbers to URI's. 

SPEERMINT has been chartered to develop best current practices among
real-time application service providers and how such services interconnect
across domain boundaries.

It is clear from discussions in both working groups that Multi-Media
Interconnection will require various forms of data to be exchanged among
administrative domains outside the normal scope of establishing various
forms of a SIP session.

Such data exchanges might be provisioning of various forms of Registries
containing mappings of phone numbers to URI, policies surrounding the
admission to points of network interconnection,  trunking data and the
distribution of Registry data to various types of databases. 

Provisioning may include PBX to service provider data exchanges as well.

The purpose of the BOF is to determine the need and scope for such data
exchanges, what existing protocols need to be adapted to meet those needs
and the appropriate schema and queries are needed to facilitate such
exchanges.

The IETF has in the past done significant work on data exchanges among
various administrative entities. In particular the PROVREG working group
developed various schema and query mechanisms to facilitate the exchange of
data among domain name registries and registrars.

The ENUM Working group has adapted PROVREG working group protocols to
develop RFC 4114, which facilitates the provisioning of ENUM data in the DNS
tree.  However, there has been little adoption of RFC 4114, and many of the
participants of the SPEERMINT working group require both data models and
protocol features not found in RFC 4114.

The proposed PEPPERMINT working group will build upon the knowledge gained
from those efforts, and the intent of this proposed working group is to find
a provisioning solution for peering as defined by SPEERMINT. The final work
product(s) from this working group will be based upon XML.
   
Additionally, bias will be given to re-using either EPP, HTTP/REST,
HTTP/XML-RPC, or HTTP/SOAP.

Proposed Deliverables

Requirements for PEPPERMINT data exchanges.

Provisioning of PEPPERMINT data registries.

Provisioning of PEPPERMINT/ENUM data caches.

Richard Shockey
Director, Member of the Technical Staff
NeuStar
46000 Center Oak Plaza - Sterling, VA 20166
PSTN Office +1 571.434.5651 
PSTN Mobile: +1 703.593.2683
<mailto:richard(at)shockey.us> 
<mailto:richard.shockey(at)neustar.biz>

------=_NextPart_000_0D28_01C826AA.5EC51810
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body bgcolor=3Dwhite lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I think we can have a short presentation on this =
&#8230;very short
since we only have 1 hour.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><o:p>&nbsp;</o:p></p>

<div class=3DMsoNormal align=3Dcenter =
style=3D'margin-left:.5in;text-align:center'>

<hr size=3D3 width=3D"100%" align=3Dcenter>

</div>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:0in;margin-right:0in;margin-bottom:
12.0pt;margin-left:.5in'><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Joonhyung =
Lim
[mailto:[email-masked]] <br>
<b>Sent:</b> Monday, November 12, 2007 12:47 AM<br>
<b>To:</b> [email-masked]; [email-masked]<br>
<b>Subject:</b> Re: [PEPPERMINT] VERSION 00 PEPPERMINT BOF =
AGENDA</span><o:p></o:p></p>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'>Dear =
Richard<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'>&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'>I'm really happy to =
comment on this
BOF that I've been waiting for, since I noticed some needs from =
industries
through KR infrastructure ENUM trial in 2006.&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'>&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'>About a charter, IMHO, I =
think it
would be better&nbsp;adding a example on paragraph below, to clarify
differences between 4114 and&nbsp;new one.&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'>&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'>&gt;However, there has =
been little
adoption of RFC 4114, and many of the<br>
&gt;participants of the SPEERMINT working group require both data models =
and<br>
&gt;protocol features not found in RFC 4114.&quot;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'>&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'>&quot;However, there has =
been
little adoption of RFC 4114, and many of the<br>
participants of the SPEERMINT working group require both data models =
and<br>
protocol features not found in RFC 4114, such as provisioning number =
prefix or
number blocks&quot;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'>&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'>Actually, this example =
also
mentioned&nbsp;in &quot;PEPPERMINT Problem Statement&quot; =
draft.&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'>&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'>And if there is ok, I =
might have
short presentation about provisioning issue when&nbsp;we used&nbsp;4114
during&nbsp;KR ENUM trial in 2006.&nbsp;It mostly leans to comments from
several players such as KR VSPs, PSTN carriers, and etc.<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'>&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'>Thanks.<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'>&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'>Joonhyung Lim, =
NIDA<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'>&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'><span =
style=3D'font-size:10.0pt'>----------------------------------------------=
---------------</span><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'>&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'>&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'>&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:0in;margin-right:0in;margin-bottom:
12.0pt;margin-left:.5in'>COMMENTS PLEASE ESPECIALLY ON THE PROPOSED =
CHARTER<br>
<br>
If anyone wants to present anyting let me or Tom know.<br>
<br>
**********************************<br>
<br>
<br>
IETF 70 PEPPERMINT BOF Agenda<br>
<br>
PEPPERMINT Session 1 (1 hour)<br>
Thursday, Afternoon Session II 1510-1610 Room Name: Salon 2<br>
<br>
Chair(s):<br>
<br>
Richard Shockey &lt;richard.shockey at neustar.biz&gt;<br>
Tom Creighton&nbsp; &lt;tom_creighton at cable.comcast.com&gt;<br>
<br>
<br>
RAI Director(s):<br>
<br>
Jon Peterson jon.peterson at neustar.biz<br>
Cullen Jennings fluffy at cisco.com<br>
<br>
<br>
<br>
Agenda Bashing. <br>
<br>
Presentation of the proposed charter. &lt;Shockey&gt; 10 min<br>
<br>
1. Review of existing provisioning protocols in IETF especially RFC =
4114<br>
(S.Hollenbeck)<br>
<br>
2. Review of peppermint problem statement ( David Schwartz )&nbsp; =
ID<br>
forthcoming.<br>
<br>
<br>
General Discussion<br>
<br>
The Usual Questions.<br>
<br>
A. Is this a problem that the IETF needs to work on?<br>
<br>
B. Are people willing to work on this problem?<br>
<br>
<br>
************<br>
<br>
Peppermint BOF<br>
<br>
Provisioning Extensions in Peering Registries for Multimedia<br>
Interconnection.<br>
<br>
Mailing Lists: <br>
<br>
&nbsp; peppermint at ietf.org<br>
<br>
General information about the mailing list is at:<br>
<br>
&nbsp; <a =
href=3D"https://www1.ietf.org/mailman/listinfo/peppermint">https://www1.i=
etf.org/mailman/listinfo/peppermint</a><br>
<br>
<br>
Temporary Area Directorate: Real Time Applications (RAI)<br>
<br>
Ultimate Area Directorate: TBD<br>
<br>
<br>
BOF Purpose.<br>
<br>
The ENUM and SPEERMINT working groups are working on various aspects =
of<br>
Multi Media Interconnection. ENUM is specifically chartered to =
develop<br>
protocols that involve the translation of E.164 numbers to URI's. <br>
<br>
SPEERMINT has been chartered to develop best current practices among<br>
real-time application service providers and how such services =
interconnect<br>
across domain boundaries.<br>
<br>
It is clear from discussions in both working groups that Multi-Media<br>
Interconnection will require various forms of data to be exchanged =
among<br>
administrative domains outside the normal scope of establishing =
various<br>
forms of a SIP session.<br>
<br>
Such data exchanges might be provisioning of various forms of =
Registries<br>
containing mappings of phone numbers to URI, policies surrounding =
the<br>
admission to points of network interconnection,&nbsp; trunking data and =
the<br>
distribution of Registry data to various types of databases. <br>
<br>
Provisioning may include PBX to service provider data exchanges as =
well.<br>
<br>
The purpose of the BOF is to determine the need and scope for such =
data<br>
exchanges, what existing protocols need to be adapted to meet those =
needs<br>
and the appropriate schema and queries are needed to facilitate such<br>
exchanges.<br>
<br>
The IETF has in the past done significant work on data exchanges =
among<br>
various administrative entities. In particular the PROVREG working =
group<br>
developed various schema and query mechanisms to facilitate the exchange =
of<br>
data among domain name registries and registrars.<br>
<br>
The ENUM Working group has adapted PROVREG working group protocols =
to<br>
develop RFC 4114, which facilitates the provisioning of ENUM data in the =
DNS<br>
tree.&nbsp; However, there has been little adoption of RFC 4114, and =
many of
the<br>
participants of the SPEERMINT working group require both data models =
and<br>
protocol features not found in RFC 4114.<br>
<br>
The proposed PEPPERMINT working group will build upon the knowledge =
gained<br>
from those efforts, and the intent of this proposed working group is to =
find<br>
a provisioning solution for peering as defined by SPEERMINT. The final =
work<br>
product(s) from this working group will be based upon XML.<br>
&nbsp;&nbsp; <br>
Additionally, bias will be given to re-using either EPP, HTTP/REST,<br>
HTTP/XML-RPC, or HTTP/SOAP.<br>
<br>
Proposed Deliverables<br>
<br>
Requirements for PEPPERMINT data exchanges.<br>
<br>
Provisioning of PEPPERMINT data registries.<br>
<br>
Provisioning of PEPPERMINT/ENUM data caches.<br>
<br>
Richard Shockey<br>
Director, Member of the Technical Staff<br>
NeuStar<br>
46000 Center Oak Plaza - Sterling, VA 20166<br>
PSTN Office +1 571.434.5651 <br>
PSTN Mobile: +1 703.593.2683<br>
&lt;<a href=3D"mailto:richard">mailto:richard</a>(at)shockey.us&gt; <br>
&lt;<a =
href=3D"mailto:richard.shockey">mailto:richard.shockey</a>(at)neustar.biz=
&gt;<br>
<br>
<o:p></o:p></p>

</div>

</div>

</body>

</html>

------=_NextPart_000_0D28_01C826AA.5EC51810--

--===============1427654896==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
PEPPERMINT mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/peppermint

--===============1427654896==--

From: "Richard Shockey" <[email-masked]>
To: <[email-masked]>
Date: Tue, 13 Nov 2007 15:21:09 -0500
Subject: [PEPPERMINT] FW: I-D ACTION:draft-schwartz-speermint-provisioning-problem-00.txt 

I believe this is a document we will be discussing in Vancouver at the BOF.
The references to spearmint was, I'm told somewhat inadvertent on the part
of the authors.

A New Internet-Draft is available from the on-line Internet-Drafts
directories.

	Title		: Managing Client Voice Peering Provisioning
	Author(s)	: D. Schwartz, et al.
	Filename	:
draft-schwartz-speermint-provisioning-problem-00.txt
	Pages		: 8
	Date		: 2007-11-13
	
   This document describes the type of data provisioned among Voice
   Service Providers.  This is in support of the service provider
   peering as defined by the Speermint WG.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-schwartz-speermint-provisioning-pr
oblem-00.txt

To remove yourself from the I-D Announcement list, send a message to 
[email-masked] with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-schwartz-speermint-provisioning-problem-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	[email-masked].
In the body type:
	"FILE
/internet-drafts/draft-schwartz-speermint-provisioning-problem-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

_______________________________________________
PEPPERMINT mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/peppermint

From: "Richard Shockey" <[email-masked]>
To: <[email-masked]>
Date: Wed, 7 Nov 2007 18:26:36 -0500
Subject: [PEPPERMINT] VERSION 00 PEPPERMINT BOF AGENDA

COMMENTS PLEASE ESPECIALLY ON THE PROPOSED CHARTER

If anyone wants to present anyting let me or Tom know.

**********************************

IETF 70 PEPPERMINT BOF Agenda

PEPPERMINT Session 1 (1 hour)
Thursday, Afternoon Session II 1510-1610 Room Name: Salon 2

Chair(s):

Richard Shockey <[email-masked]>
Tom Creighton  <[email-masked]>

RAI Director(s):

Jon Peterson [email-masked]
Cullen Jennings [email-masked]

Agenda Bashing. 

Presentation of the proposed charter. <Shockey> 10 min

1. Review of existing provisioning protocols in IETF especially RFC 4114
(S.Hollenbeck)

2. Review of peppermint problem statement ( David Schwartz )  ID
forthcoming.

General Discussion

The Usual Questions.

A. Is this a problem that the IETF needs to work on?

B. Are people willing to work on this problem?

************

Peppermint BOF

Provisioning Extensions in Peering Registries for Multimedia
Interconnection.

Mailing Lists: 

  [email-masked]

General information about the mailing list is at:

  https://www1.ietf.org/mailman/listinfo/peppermint

Temporary Area Directorate: Real Time Applications (RAI)

Ultimate Area Directorate: TBD

BOF Purpose.

The ENUM and SPEERMINT working groups are working on various aspects of
Multi Media Interconnection. ENUM is specifically chartered to develop
protocols that involve the translation of E.164 numbers to URI's. 
 
SPEERMINT has been chartered to develop best current practices among
real-time application service providers and how such services interconnect
across domain boundaries.

It is clear from discussions in both working groups that Multi-Media
Interconnection will require various forms of data to be exchanged among
administrative domains outside the normal scope of establishing various
forms of a SIP session.

Such data exchanges might be provisioning of various forms of Registries
containing mappings of phone numbers to URI, policies surrounding the
admission to points of network interconnection,  trunking data and the
distribution of Registry data to various types of databases. 

Provisioning may include PBX to service provider data exchanges as well.

The purpose of the BOF is to determine the need and scope for such data
exchanges, what existing protocols need to be adapted to meet those needs
and the appropriate schema and queries are needed to facilitate such
exchanges.

The IETF has in the past done significant work on data exchanges among
various administrative entities. In particular the PROVREG working group
developed various schema and query mechanisms to facilitate the exchange of
data among domain name registries and registrars.

The ENUM Working group has adapted PROVREG working group protocols to
develop RFC 4114, which facilitates the provisioning of ENUM data in the DNS
tree.  However, there has been little adoption of RFC 4114, and many of the
participants of the SPEERMINT working group require both data models and
protocol features not found in RFC 4114.

The proposed PEPPERMINT working group will build upon the knowledge gained
from those efforts, and the intent of this proposed working group is to find
a provisioning solution for peering as defined by SPEERMINT. The final work
product(s) from this working group will be based upon XML.
   
Additionally, bias will be given to re-using either EPP, HTTP/REST,
HTTP/XML-RPC, or HTTP/SOAP.

Proposed Deliverables

Requirements for PEPPERMINT data exchanges.

Provisioning of PEPPERMINT data registries.

Provisioning of PEPPERMINT/ENUM data caches.

Richard Shockey
Director, Member of the Technical Staff
NeuStar
46000 Center Oak Plaza - Sterling, VA 20166
PSTN Office +1 571.434.5651 
PSTN Mobile: +1 703.593.2683
<mailto:richard(at)shockey.us> 
<mailto:richard.shockey(at)neustar.biz>

_______________________________________________
PEPPERMINT mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/peppermint

From: "Richard Shockey" <[email-masked]>
To: "'Hollenbeck, Scott'" <[email-masked]>, <[email-masked]>
Subject: RE: [PEPPERMINT] Please submit requests for slots for the BOF..
Date: Wed, 7 Nov 2007 15:41:14 -0500
Cc: "'Creighton, Tom'" <[email-masked]>

Confirmed ... tks.

>  -----Original Message-----
>  From: Hollenbeck, Scott [mailto:[email-masked]]
>  Sent: Wednesday, November 07, 2007 2:09 PM
>  To: [email-masked]; Richard Shockey
>  Cc: Creighton, Tom
>  Subject: RE: [PEPPERMINT] Please submit requests for slots for the
>  BOF..
>  
>  > -----Original Message-----
>  > From: Richard Shockey [mailto:[email-masked]]
>  > Sent: Tuesday, November 06, 2007 3:48 PM
>  > To: [email-masked]
>  > Cc: 'Creighton, Tom'
>  > Subject: [PEPPERMINT] Please submit requests for slots for the BOF..
>  >
>  > As soon a practically possible.
>  
>  Rich, I'd like to have a few minutes to talk about EPP and if/how it
>  might be useful in this context.
>  
>  -Scott-

_______________________________________________
PEPPERMINT mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/peppermint

Content-class: urn:content-classes:message
Subject: RE: [PEPPERMINT] Please submit requests for slots for the BOF..
Date: Wed, 7 Nov 2007 14:09:13 -0500
From: "Hollenbeck, Scott" <[email-masked]>
To: <[email-masked]>, "Richard Shockey" <[email-masked]>
Cc: "Creighton, Tom" <[email-masked]>

> -----Original Message-----
> From: Richard Shockey [mailto:[email-masked]]=20
> Sent: Tuesday, November 06, 2007 3:48 PM
> To: [email-masked]
> Cc: 'Creighton, Tom'
> Subject: [PEPPERMINT] Please submit requests for slots for the BOF..
>=20
> As soon a practically possible.

Rich, I'd like to have a few minutes to talk about EPP and if/how it
might be useful in this context.

-Scott-

_______________________________________________
PEPPERMINT mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/peppermint

From: "Richard Shockey" <[email-masked]>
To: <[email-masked]>
Date: Tue, 6 Nov 2007 15:47:55 -0500
Cc: "'Creighton, Tom'" <[email-masked]>
Subject: [PEPPERMINT] Please submit requests for slots for the BOF..

As soon a practically possible.

Richard Shockey
Director, Member of the Technical Staff
NeuStar
46000 Center Oak Plaza - Sterling, VA 20166
PSTN Office +1 571.434.5651 
PSTN Mobile: +1 703.593.2683
<mailto:richard(at)shockey.us> 
<mailto:richard.shockey(at)neustar.biz>

_______________________________________________
PEPPERMINT mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/peppermint

From: "Richard Shockey" <[email-masked]>
To: <[email-masked]>, <[email-masked]>
Date: Fri, 2 Nov 2007 13:30:36 -0400
Cc: 
Subject: [PEPPERMINT] FW: Internet-Drafts Submission Cutoff Dates for the 70th IETF Meeting in Vancouver, BC, Canada 

-----Original Message-----
From: [email-masked] [mailto:[email-masked]]=20
Sent: Friday, November 02, 2007 12:00 AM
To: [email-masked]
Subject: Internet-Drafts Submission Cutoff Dates for the 70th IETF =
Meeting in Vancouver, BC, Canada=20

There are two (2) Internet-Draft cutoff dates for the 70th=20
IETF Meeting in Vancouver, BC, Canada:

November 12th: Cutoff Date for Initial (i.e., version -00)=20
Internet-Draft Submissions=20

All initial Internet-Drafts (version -00) must be submitted by Monday,=20
November 12th at 9:00 AM ET (14:00 UTC/GMT). As always, all initial =
submissions with a=20
filename beginning with "draft-ietf" must be approved by the=20
appropriate WG Chair before they can be processed or announced.  The=20
Secretariat would appreciate receiving WG Chair approval by Monday,=20
November 5th at 9:00 AM ET (14:00 UTC/GMT).

November  (14:00 UTC/GMT): Cutoff Date for Revised (i.e., version -01 =
and higher)=20
Internet-Draft Submissions=20

All revised Internet-Drafts (version -01 and higher) must be submitted=20
by Monday, November 19th at 9:00 AM ET (14:00 UTC/GMT).

Initial and revised Internet-Drafts received after their respective=20
cutoff dates will not be made available in the Internet-Drafts=20
directory or announced until on or after Monday, December 3rd at 9:00=20
AM ET (14:00 UTC/GMT), when Internet-Draft posting resumes.  Please do =
not wait until=20
the last minute to submit.

The Secretariat encourages you to submit your Internet-Drafts via the=20
Internet-Draft Submission Tool (IDST) =
https://datatracker.ietf.org/idst/upload.cgi.=20
If you are unable to do so, then you may still submit your Internet-
Drafts manually by sending them to [email-masked].  If you=20
are submitting a version -00 WG draft that replaces non-WG draft, then=20
you must submit it manually as the current IDST cannot handle=20
replacements.  Please be sure to state that one draft replaces another=20
in the cover note that accompanies your submission.  Also, please note=20
that the IDST will not accept drafts submitted after their respective=20
cutoff dates.

Thank you for your understanding and cooperation. If you have any=20
questions or concerns, then please send a message to=20
[email-masked].

The IETF Secretariat

FYI: The Internet-Draft cutoff dates as well as other significant dates
for the 70th IETF Meeting can be found at =
http://www.ietf.org/meetings/cutoff_dates_70.html.

_______________________________________________
IETF-Announce mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/ietf-announce

_______________________________________________
PEPPERMINT mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/peppermint

Date: Wed, 31 Oct 2007 15:50:50 -0400
To: "Richard Shockey" <[email-masked]>, <[email-masked]>, <[email-masked]>, <[email-masked]>
From: Tony Rutkowski <[email-masked]>
Cc: 
Subject: [PEPPERMINT] FCC VoIP Order/NPRM implementation

Hi Rich,

Considering the Commission's adoption of VoIP
portability requirements today, is the implementation
something you will be considering at the next ENUM
fete.

--tony

_______________________________________________
PEPPERMINT mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/peppermint