[PEPPERMINT] new BoF proposal
Andrew Newton <andy@hxr.us> Sun, 28 January 2007 18:36 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBEtJ-0001Xj-6h; Sun, 28 Jan 2007 13:36:37 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBEtI-0001XZ-8X for peppermint@ietf.org; Sun, 28 Jan 2007 13:36:36 -0500
Received: from zeke.toscano.org ([69.31.8.124] helo=zeke.ecotroph.net) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HBEtG-0006co-Ui for peppermint@ietf.org; Sun, 28 Jan 2007 13:36:36 -0500
Received: from [10.0.1.110] ([::ffff:72.196.237.170]) (AUTH: PLAIN anewton, SSL: TLSv1/SSLv3,128bits,AES128-SHA) by zeke.ecotroph.net with esmtp; Sun, 28 Jan 2007 13:35:55 -0500 id 0158811A.45BCED0C.000024D2
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Transfer-Encoding: 7bit
Message-Id: <6F5BC580-3C9C-44EB-839D-3004CFAC2250@hxr.us>
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
To: peppermint@ietf.org
From: Andrew Newton <andy@hxr.us>
Date: Sun, 28 Jan 2007 13:36:29 -0500
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Subject: [PEPPERMINT] new BoF proposal
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
All, A tightened up version of the PEPPERMINT BoF proposal has been formulated. The major changes since the last version are: 1) some language has been changed or eliminated that was construed to give PEPPERMINT a larger scope than intended, and 2) the input documents are listed. The text is below. Comments, questions, and suggestions welcomed. -andy Peppermint BOF Provisioning Extensions in Peering Registries for Multimedia INTerconnection. Mailing Lists: BOF chairs: Andrew Newton [andy@hxr.us] Richard Shockey [rich.shockey@neustar.biz] 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 address of record data to be provisioned among administrative domains outside the normal scope of establishing a SIP session. 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 in the operator community 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: 1) Requirements for SPEERMINT data exchange. 2) Provisioning of SPEERMINT data registries. 3) Provisioning of SPEERMINT/ENUM data caches. Input Documents: 1) PEPPERMINT Problem Statement draft-newton-peppermint-problem-statement-00.txt 2) E.164 Number Provisioning Requirements - Data Set Requirements draft-schwartz-peppermint-e164-provisioning-data-set-00.txt 3) ENUM Registry Interface Requirements draft-lewis-peppermint-enum-reg-if-00.txt _______________________________________________ PEPPERMINT mailing list PEPPERMINT@ietf.org https://www1.ietf.org/mailman/listinfo/peppermint
- [PEPPERMINT] new BoF proposal Andrew Newton
- RE: [PEPPERMINT] new BoF proposal Romascanu, Dan (Dan)