[PEPPERMINT] I have formally requested a BOF on the PEPPERMINT proposition for Vancouver.
"Richard Shockey" <richard@shockey.us> Thu, 18 October 2007 03:05 UTC
Return-path: <peppermint-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IiLhv-0006Yi-Pp; Wed, 17 Oct 2007 23:05:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IiLht-0006Xx-CM; Wed, 17 Oct 2007 23:05:57 -0400
Received: from mail.songbird.com ([208.184.79.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IiLhs-00065U-3X; Wed, 17 Oct 2007 23:05:57 -0400
Received: from rshockeyPC (h-68-165-240-35.mclnva23.covad.net [68.165.240.35]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l9I35WE1009611 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 17 Oct 2007 20:05:33 -0700
From: Richard Shockey <richard@shockey.us>
To: peppermint@ietf.org, speermint@ietf.org, enum@ietf.org
References: <B70F3C61-8E7F-484C-882E-B6FFA88C8D42@hxr.us>
In-Reply-To: <B70F3C61-8E7F-484C-882E-B6FFA88C8D42@hxr.us>
Date: Wed, 17 Oct 2007 23:05:16 -0400
Message-ID: <011001c81133$b6867ad0$23937070$@us>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acdq2YSxJnBpAM8fRfeozkdMO0FALymWRc5w
Content-Language: en-us
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Cc:
Subject: [PEPPERMINT] I have formally requested a BOF on the PEPPERMINT proposition for Vancouver.
X-BeenThere: peppermint@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Provisioning Extensions in Peering Registries for Multimedia INTerconnection <peppermint.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/peppermint>, <mailto:peppermint-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/peppermint>
List-Post: <mailto:peppermint@ietf.org>
List-Help: <mailto:peppermint-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/peppermint>, <mailto:peppermint-request@ietf.org?subject=subscribe>
Errors-To: peppermint-bounces@ietf.org
I have submitted to the RAI AD's and the agenda folks a proposed BOF. I would like folks to consider the proposed charter and comment. Should folks wish to present drafts or simply wish to present ideas let us know ASAP. Peppermint BOF Provisioning Extensions in Peering Registries for Multimedia Interconnection. Mailing Lists: peppermint@ietf.org General information about the mailing list is at: https://www1.ietf.org/mailman/listinfo/peppermint BOF chairs: Richard Shockey [richard.shockey@neustar.biz] Other co-chairs TBD waiting on approvals... 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. _______________________________________________ PEPPERMINT mailing list PEPPERMINT@ietf.org https://www1.ietf.org/mailman/listinfo/peppermint
- [PEPPERMINT] not a done deal, there's still a lot… Andrew Newton
- [PEPPERMINT] I have formally requested a BOF on t… Richard Shockey