From speermint-bounces@ietf.org Thu Dec 07 14:42:48 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GsP8F-0006Sd-Sn; Thu, 07 Dec 2006 14:42:11 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GsP8E-0006ST-Dw for speermint@ietf.org; Thu, 07 Dec 2006 14:42:10 -0500 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GsP8D-0000Z0-2c for speermint@ietf.org; Thu, 07 Dec 2006 14:42:10 -0500 Received: from RSHOCKEYLTXP (neustargw.va.neustar.com [209.173.53.233]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id kB7Jg65m002705 for ; Thu, 7 Dec 2006 11:42:12 -0800 From: "Richard Shockey" To: Date: Thu, 7 Dec 2006 14:41:50 -0500 Message-ID: <054901c71a37$be58e9d0$c5201f0a@cis.neustar.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 thread-index: AccaN7zvKk8CYObgQFCFeFDmH8awZg== X-SongbirdInformation: support@songbird.com for more information X-Songbird: Clean X-Songbird-From: richard@shockey.us X-Spam-Score: 0.5 (/) X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0 Subject: [Speermint] Interest in SPEERMINT provisioning issues. X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: richard@shockey.us List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: speermint-bounces@ietf.org There was some talk in San Diego of interest in peeling off the provisioning issues surrounding SPEERMINT information registries into a separate work item. I'd like to get a poll of the list to see again how many people are interested in the work and what might be the proper way to expedite this. We're certainly not ready to provision policy yet but its clear that some form of SPEERMINT provisioning requirements document is in order. As I mentioned in the meeting there has been some preliminary work in the area from the ENUM WG however it is based on EPP and as I mentioned most of the OSS systems now deployed in carrier networks have generally been based on SOAP/XML. RFC 4114 Title: E.164 Number Mapping for the Extensible Provisioning Protocol (EPP) Author(s): S. Hollenbeck Status: Standards Track Date: June 2005 Mailbox: shollenbeck@verisign.com Pages: 17 Characters: 31490 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-enum-epp-e164-08.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc4114.txt Provisioning issues are not very sexy but are essential to moving things forward. A. What interest is there in this work? B. What scope should it take? SOAP etc? C. Where should this work be done? Richard Shockey Director, Member of the Technical Staff NeuStar 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org sip:5651(at)neustarlab.biz PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683 _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint From speermint-bounces@ietf.org Thu Dec 07 15:22:09 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GsPkf-0007aa-Ga; Thu, 07 Dec 2006 15:21:53 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GsPkd-0007Ut-R9 for speermint@ietf.org; Thu, 07 Dec 2006 15:21:51 -0500 Received: from zeke.ecotroph.net ([69.31.8.124]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GsPkX-0005z5-IA for speermint@ietf.org; Thu, 07 Dec 2006 15:21:51 -0500 Received: from [172.16.10.88] ([::ffff:208.50.38.5]) (AUTH: PLAIN anewton, SSL: TLSv1/SSLv3,128bits,AES128-SHA) by zeke.ecotroph.net with esmtp; Thu, 07 Dec 2006 15:21:19 -0500 id 0158836A.457877BF.00003E64 In-Reply-To: <054901c71a37$be58e9d0$c5201f0a@cis.neustar.com> References: <054901c71a37$be58e9d0$c5201f0a@cis.neustar.com> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <378E2A37-DC3E-43DB-96B2-84D6F3BC0289@hxr.us> Content-Transfer-Encoding: 7bit From: Andrew Newton Subject: Re: [Speermint] Interest in SPEERMINT provisioning issues. Date: Thu, 7 Dec 2006 15:21:30 -0500 To: richard@shockey.us X-Mailer: Apple Mail (2.752.3) X-Spam-Score: 0.5 (/) X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8 Cc: speermint@ietf.org X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: speermint-bounces@ietf.org Richard, I think you are starting this off on the wrong foot, that is with a technology battle. I've personally reviewed the specs for many of the peering points and only one used SOAP. We shouldn't start off with a SOAP vs EPP vs REST vs ASN.1 battle. As I stated at the mic when I brought up this idea, the design team should focus on the functional requirements for a provisioning interface. It may turn out that EPP works just fine and that people hoisting their flavor of SOAP are just trying to drive a wedge in the marketplace. If it turns out that EPP isn't right, then we can let the powers that be worry about who gets to specify the new protocol, etc... To answer part of your question, yes I am interested in finding out what functions a provisioning interface needs to have. -andy On Dec 7, 2006, at 2:41 PM, Richard Shockey wrote: > > There was some talk in San Diego of interest in peeling off the > provisioning > issues surrounding SPEERMINT information registries into a separate > work > item. > > I'd like to get a poll of the list to see again how many people are > interested in the work and what might be the proper way to expedite > this. > > We're certainly not ready to provision policy yet but its clear > that some > form of SPEERMINT provisioning requirements document is in order. > > As I mentioned in the meeting there has been some preliminary work > in the > area from the ENUM WG however it is based on EPP and as I mentioned > most of > the OSS systems now deployed in carrier networks have generally > been based > on SOAP/XML. > > > > RFC 4114 > > Title: E.164 Number Mapping for the Extensible > Provisioning Protocol (EPP) > Author(s): S. Hollenbeck > Status: Standards Track > Date: June 2005 > Mailbox: shollenbeck@verisign.com > Pages: 17 > Characters: 31490 > Updates/Obsoletes/SeeAlso: None > > I-D Tag: draft-ietf-enum-epp-e164-08.txt > > URL: ftp://ftp.rfc-editor.org/in-notes/rfc4114.txt > > > Provisioning issues are not very sexy but are essential to moving > things > forward. > > A. What interest is there in this work? > > B. What scope should it take? SOAP etc? > > C. Where should this work be done? > > > Richard Shockey > Director, Member of the Technical Staff > NeuStar > 46000 Center Oak Plaza - Sterling, VA 20166 > sip:rshockey(at)iptel.org > sip:5651(at)neustarlab.biz > PSTN Office +1 571.434.5651 > PSTN Mobile: +1 703.593.2683 > > > > > > > > > _______________________________________________ > Speermint mailing list > Speermint@ietf.org > https://www1.ietf.org/mailman/listinfo/speermint _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint From speermint-bounces@ietf.org Thu Dec 07 21:20:42 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GsVKi-0004DJ-Kc; Thu, 07 Dec 2006 21:19:28 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GsVKh-0004DB-6S for speermint@ietf.org; Thu, 07 Dec 2006 21:19:27 -0500 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GsVKf-0004Tr-MT for speermint@ietf.org; Thu, 07 Dec 2006 21:19:27 -0500 Received: from RSHOCKEYLTXP (h-68-165-240-34.mclnva23.covad.net [68.165.240.34]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id kB82JBx8023760; Thu, 7 Dec 2006 18:19:17 -0800 From: "Richard Shockey" To: , "'Andrew Newton'" Subject: RE: [Speermint] Interest in SPEERMINT provisioning issues. Date: Thu, 7 Dec 2006 21:18:56 -0500 Message-ID: <00ad01c71a6f$38346b80$22f0a544@cis.neustar.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 Thread-Index: AccaTiHJj85Jsgo9S76/rBbfpaYmlQAHq3Xg In-Reply-To: <336601437-1165530110-cardhu_blackberry.rim.net-1321879507-@bxe005-cell01.bisx.prod.on.blackberry> X-SongbirdInformation: support@songbird.com for more information X-Songbird: Clean X-Songbird-From: richard@shockey.us X-Spam-Score: 0.5 (/) X-Scan-Signature: 827a2a57ca7ab0837847220f447e8d56 Cc: speermint@ietf.org X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: richard@shockey.us List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: speermint-bounces@ietf.org OK ... I'm not going to be a protocol bigot here but I do think we are in agreement that provisioning is a critical element to any discussion of federations and peering. Irrespective of the natural TN 2 URI ENUM mappings to points of interconnection there is the expression of policies etc that will have to be documented. My only concern is that discussions of this class of topic not be taken without the input of the poor companies that actually have to do this kind of work for service providers. We certainly know who some of them are... the issue how do we create a proper forum that takes into account the obvious need with the reality of implementation strategies. Is the work appropriate for SPEERMINT aka is it within charter or is some separate WG necessary. OSS provisioning issues are a difficult beasts that have to be integrated into larger Operational Support environments. That is my point. I'm just asking questions here. This is IMHO a issue we need to have some consensus on before Prague so lets start asking the right questions. David to your point clearly there needs to be a Requirements document that outlines what is required etc so some preliminary ID on the subject are certainly in order. LIST: please chime in here with comments. > -----Original Message----- > From: david.m.schwartz@kayote.com [mailto:david.m.schwartz@kayote.com] > Sent: Thursday, December 07, 2006 5:23 PM > To: Andrew Newton; richard@shockey.us > Cc: speermint@ietf.org > Subject: Re: [Speermint] Interest in SPEERMINT provisioning issues. > > I am with Andy on this. In fact I have spent some time looking over the > various formats we use in different relationships amd have started to put > together a short doc describing what information we deem important. > > Protocol is secondary. > > Hope to be able to send our formats to list by next week. > > Cheers, > > David > > Sent via BlackBerry from T-Mobile > > -----Original Message----- > From: Andrew Newton > Date: Thu, 7 Dec 2006 15:21:30 > To:richard@shockey.us > Cc:speermint@ietf.org > Subject: Re: [Speermint] Interest in SPEERMINT provisioning issues. > > Richard, > > I think you are starting this off on the wrong foot, that is with a > technology battle. I've personally reviewed the specs for many of > the peering points and only one used SOAP. We shouldn't start off > with a SOAP vs EPP vs REST vs ASN.1 battle. > > As I stated at the mic when I brought up this idea, the design team > should focus on the functional requirements for a provisioning > interface. It may turn out that EPP works just fine and that people > hoisting their flavor of SOAP are just trying to drive a wedge in the > marketplace. If it turns out that EPP isn't right, then we can let > the powers that be worry about who gets to specify the new protocol, > etc... > > To answer part of your question, yes I am interested in finding out > what functions a provisioning interface needs to have. > > -andy > > On Dec 7, 2006, at 2:41 PM, Richard Shockey wrote: > > > > > There was some talk in San Diego of interest in peeling off the > > provisioning > > issues surrounding SPEERMINT information registries into a separate > > work > > item. > > > > I'd like to get a poll of the list to see again how many people are > > interested in the work and what might be the proper way to expedite > > this. > > > > We're certainly not ready to provision policy yet but its clear > > that some > > form of SPEERMINT provisioning requirements document is in order. > > > > As I mentioned in the meeting there has been some preliminary work > > in the > > area from the ENUM WG however it is based on EPP and as I mentioned > > most of > > the OSS systems now deployed in carrier networks have generally > > been based > > on SOAP/XML. > > > > > > > > RFC 4114 > > > > Title: E.164 Number Mapping for the Extensible > > Provisioning Protocol (EPP) > > Author(s): S. Hollenbeck > > Status: Standards Track > > Date: June 2005 > > Mailbox: shollenbeck@verisign.com > > Pages: 17 > > Characters: 31490 > > Updates/Obsoletes/SeeAlso: None > > > > I-D Tag: draft-ietf-enum-epp-e164-08.txt > > > > URL: ftp://ftp.rfc-editor.org/in-notes/rfc4114.txt > > > > > > Provisioning issues are not very sexy but are essential to moving > > things > > forward. > > > > A. What interest is there in this work? > > > > B. What scope should it take? SOAP etc? > > > > C. Where should this work be done? > > > > > > Richard Shockey > > Director, Member of the Technical Staff > > NeuStar > > 46000 Center Oak Plaza - Sterling, VA 20166 > > sip:rshockey(at)iptel.org > > sip:5651(at)neustarlab.biz > > PSTN Office +1 571.434.5651 > > PSTN Mobile: +1 703.593.2683 > > > > > > > > > > > > > > > > > > _______________________________________________ > > Speermint mailing list > > Speermint@ietf.org > > https://www1.ietf.org/mailman/listinfo/speermint > > > _______________________________________________ > Speermint mailing list > Speermint@ietf.org > https://www1.ietf.org/mailman/listinfo/speermint _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint From speermint-bounces@ietf.org Tue Dec 19 10:40:26 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gwh4S-00009y-68; Tue, 19 Dec 2006 10:40:00 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gwh4Q-00009a-8X for speermint@ietf.org; Tue, 19 Dec 2006 10:39:58 -0500 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gwh3K-0001Mo-Sl for speermint@ietf.org; Tue, 19 Dec 2006 10:38:53 -0500 Received: from RSHOCKEYLTXP (h-68-165-240-34.mclnva23.covad.net [68.165.240.34]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id kBJFc5cd026501; Tue, 19 Dec 2006 07:38:11 -0800 From: "Richard Shockey" To: "'Andrew Newton'" , "'Livingood, Jason'" , "'David Meyer'" , Date: Tue, 19 Dec 2006 10:37:49 -0500 Message-ID: <021401c72383$a626b130$22f0a544@cis.neustar.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 Thread-Index: AccjSWNdXUPAEzfrRSm4yvIVZU6iiAAOYF0g X-SongbirdInformation: support@songbird.com for more information X-Songbird: Clean X-Songbird-From: richard@shockey.us X-Spam-Score: 0.0 (/) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 Cc: 'RAI ADs' Subject: [Speermint] FW: Preliminary BOF proposals due soon X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: richard@shockey.us List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: speermint-bounces@ietf.org Andrew Newton and I will be proposing a BOF on SPEERMINT Provisioning issues for IETF 68 in Prague. If anyone has topic or is considering producing drafts related to provisioning issues please let Andy or I know. > -----Original Message----- > From: IETF Chair [mailto:chair@ietf.org] > Sent: Tuesday, December 19, 2006 3:39 AM > To: IETF Announcement list > Subject: Preliminary BOF proposals due soon > > As for the previous IETF, we're asking for preliminary BOF proposals to be > sent to the appropriate Area Director a little earlier, by January 15. > Even sooner would be better! > > Full list of dates: > http://www.ietf.org/meetings/68-cutoff_dates.html > > BOF wiki: > http://www1.tools.ietf.org/bof/trac/wiki > > Hints: > http://tools.ietf.org/html/draft-narten-successful-bof > > Brian Carpenter > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/ietf-announce _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint From speermint-bounces@ietf.org Tue Dec 19 11:26:54 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwhnS-0000mB-8u; Tue, 19 Dec 2006 11:26:30 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwhnQ-0000m5-Ia for speermint@ietf.org; Tue, 19 Dec 2006 11:26:28 -0500 Received: from bzq-25-94-44.cust.bezeqint.net ([212.25.94.44] helo=isr-jlm-mail.Kayote.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwhnP-0000zX-5L for speermint@ietf.org; Tue, 19 Dec 2006 11:26:28 -0500 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5 Subject: RE: [Speermint] FW: Preliminary BOF proposals due soon Date: Tue, 19 Dec 2006 18:26:23 +0200 Message-ID: <1DDB0D3CC4E7F14FAE946361C0A6065501C086A4@isr-jlm-mail.Kayote.com> In-Reply-To: <021401c72383$a626b130$22f0a544@cis.neustar.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Speermint] FW: Preliminary BOF proposals due soon Thread-Index: AccjSWNdXUPAEzfrRSm4yvIVZU6iiAAOYF0gAAHWoVA= From: "David Schwartz" To: , "Andrew Newton" , "Livingood, Jason" , "David Meyer" , X-Spam-Score: 0.1 (/) X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64 Cc: RAI ADs X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: speermint-bounces@ietf.org I am 85% finished on an a draft describing requirements we have accumulated at XConnect. Hope to have this out by the end of the year. David -----Original Message----- From: Richard Shockey [mailto:richard@shockey.us]=20 Sent: Tuesday, December 19, 2006 5:38 PM To: 'Andrew Newton'; 'Livingood, Jason'; 'David Meyer'; speermint@ietf.org Cc: 'RAI ADs' Subject: [Speermint] FW: Preliminary BOF proposals due soon Andrew Newton and I will be proposing a BOF on SPEERMINT Provisioning issues for IETF 68 in Prague. If anyone has topic or is considering producing drafts related to provisioning issues please let Andy or I know. > -----Original Message----- > From: IETF Chair [mailto:chair@ietf.org] > Sent: Tuesday, December 19, 2006 3:39 AM > To: IETF Announcement list > Subject: Preliminary BOF proposals due soon >=20 > As for the previous IETF, we're asking for preliminary BOF proposals to be > sent to the appropriate Area Director a little earlier, by January 15. > Even sooner would be better! >=20 > Full list of dates: > http://www.ietf.org/meetings/68-cutoff_dates.html >=20 > BOF wiki: > http://www1.tools.ietf.org/bof/trac/wiki >=20 > Hints: > http://tools.ietf.org/html/draft-narten-successful-bof >=20 > Brian Carpenter >=20 > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/ietf-announce _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint From speermint-bounces@ietf.org Tue Dec 19 15:13:53 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwlLK-0002Dw-RN; Tue, 19 Dec 2006 15:13:42 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwlLJ-0002DK-Be for speermint@ietf.org; Tue, 19 Dec 2006 15:13:41 -0500 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwlLH-00077x-V2 for speermint@ietf.org; Tue, 19 Dec 2006 15:13:41 -0500 Received: from RSHOCKEYLTXP (h-68-165-240-34.mclnva23.covad.net [68.165.240.34]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id kBJKDG1d000395; Tue, 19 Dec 2006 12:13:28 -0800 From: "Richard Shockey" To: "'David Schwartz'" , "'Andrew Newton'" , "'Livingood, Jason'" , "'David Meyer'" , Subject: RE: [Speermint] FW: Preliminary BOF proposals due soon Date: Tue, 19 Dec 2006 15:13:00 -0500 Message-ID: <019e01c723aa$17e514d0$22f0a544@cis.neustar.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 In-Reply-To: <1DDB0D3CC4E7F14FAE946361C0A6065501C086A4@isr-jlm-mail.Kayote.com> Thread-Index: AccjSWNdXUPAEzfrRSm4yvIVZU6iiAAOYF0gAAHWoVAAB+WfgA== X-SongbirdInformation: support@songbird.com for more information X-Songbird: Clean X-Songbird-From: richard@shockey.us X-Spam-Score: 0.0 (/) X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d Cc: 'RAI ADs' X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: richard@shockey.us List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: speermint-bounces@ietf.org BTW you can also put on catchy BOF name thinking caps on ..feel free. My current favorite is Peppermint. Provisioning Extenstions in Peering Registries for Multimedia INTerconnection. Has that nice IETF ring to it ..dont you think? > -----Original Message----- > From: David Schwartz [mailto:David.Schwartz@Kayote.com] > Sent: Tuesday, December 19, 2006 11:26 AM > To: richard@shockey.us; Andrew Newton; Livingood, Jason; David Meyer; > speermint@ietf.org > Cc: RAI ADs > Subject: RE: [Speermint] FW: Preliminary BOF proposals due soon > > I am 85% finished on an a draft describing requirements we have > accumulated at XConnect. Hope to have this out by the end of the year. > > David > > -----Original Message----- > From: Richard Shockey [mailto:richard@shockey.us] > Sent: Tuesday, December 19, 2006 5:38 PM > To: 'Andrew Newton'; 'Livingood, Jason'; 'David Meyer'; > speermint@ietf.org > Cc: 'RAI ADs' > Subject: [Speermint] FW: Preliminary BOF proposals due soon > > > > Andrew Newton and I will be proposing a BOF on SPEERMINT Provisioning > issues > for IETF 68 in Prague. > > If anyone has topic or is considering producing drafts related to > provisioning issues please let Andy or I know. > > > -----Original Message----- > > From: IETF Chair [mailto:chair@ietf.org] > > Sent: Tuesday, December 19, 2006 3:39 AM > > To: IETF Announcement list > > Subject: Preliminary BOF proposals due soon > > > > As for the previous IETF, we're asking for preliminary BOF proposals > to be > > sent to the appropriate Area Director a little earlier, by January 15. > > Even sooner would be better! > > > > Full list of dates: > > http://www.ietf.org/meetings/68-cutoff_dates.html > > > > BOF wiki: > > http://www1.tools.ietf.org/bof/trac/wiki > > > > Hints: > > http://tools.ietf.org/html/draft-narten-successful-bof > > > > Brian Carpenter > > > > _______________________________________________ > > IETF-Announce mailing list > > IETF-Announce@ietf.org > > https://www1.ietf.org/mailman/listinfo/ietf-announce > > > _______________________________________________ > Speermint mailing list > Speermint@ietf.org > https://www1.ietf.org/mailman/listinfo/speermint _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint From speermint-bounces@ietf.org Tue Dec 19 15:19:22 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwlQZ-0003ME-Cq; Tue, 19 Dec 2006 15:19:07 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwlQY-0003M7-6m for speermint@ietf.org; Tue, 19 Dec 2006 15:19:06 -0500 Received: from unknown-141-roc.globalcrossing.com ([209.130.177.141] helo=mailsrv.ams.gblxint.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwlQW-0000Hs-EA for speermint@ietf.org; Tue, 19 Dec 2006 15:19:06 -0500 Received: from w3uspdy19.ams.gblxint.com (w3uspdy19.ams.gblxint.com [10.60.51.69]) by mailsrv.ams.gblxint.com (Postfix) with ESMTP id 25A25E8E1D; Tue, 19 Dec 2006 15:18:58 -0500 (EST) Received: from EVS2.ams.gblxint.com ([10.60.51.59]) by w3uspdy19.ams.gblxint.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 19 Dec 2006 15:18:58 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Subject: RE: [Speermint] FW: Preliminary BOF proposals due soon Date: Tue, 19 Dec 2006 15:18:56 -0500 Message-ID: In-Reply-To: <019e01c723aa$17e514d0$22f0a544@cis.neustar.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Speermint] FW: Preliminary BOF proposals due soon Thread-Index: AccjSWNdXUPAEzfrRSm4yvIVZU6iiAAOYF0gAAHWoVAAB+WfgAAANcjw From: "Uzelac, Adam" To: , "David Schwartz" , "Andrew Newton" , "Livingood, Jason" , "David Meyer" , X-OriginalArrivalTime: 19 Dec 2006 20:18:58.0043 (UTC) FILETIME=[E9FCF4B0:01C723AA] X-Spam-Score: 0.1 (/) X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86 Cc: RAI ADs X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: speermint-bounces@ietf.org Not only an IETF ring, but also a holiday ring!!! Candy canes and all. ;) Happy Holidays one and all, I hope this email finds you well. -AU=20 > -----Original Message----- > From: Richard Shockey [mailto:richard@shockey.us]=20 > Sent: Tuesday, December 19, 2006 3:13 PM > To: 'David Schwartz'; 'Andrew Newton'; 'Livingood, Jason';=20 > 'David Meyer'; speermint@ietf.org > Cc: 'RAI ADs' > Subject: RE: [Speermint] FW: Preliminary BOF proposals due soon >=20 >=20 >=20 > BTW you can also put on catchy BOF name thinking caps on ..feel free. >=20 > My current favorite is Peppermint. >=20 > Provisioning Extenstions in Peering Registries for Multimedia=20 > INTerconnection. >=20 > Has that nice IETF ring to it ..dont you think? >=20 >=20 > > -----Original Message----- > > From: David Schwartz [mailto:David.Schwartz@Kayote.com] > > Sent: Tuesday, December 19, 2006 11:26 AM > > To: richard@shockey.us; Andrew Newton; Livingood, Jason;=20 > David Meyer;=20 > > speermint@ietf.org > > Cc: RAI ADs > > Subject: RE: [Speermint] FW: Preliminary BOF proposals due soon > >=20 > > I am 85% finished on an a draft describing requirements we have=20 > > accumulated at XConnect. Hope to have this out by the end=20 > of the year. > >=20 > > David > >=20 > > -----Original Message----- > > From: Richard Shockey [mailto:richard@shockey.us] > > Sent: Tuesday, December 19, 2006 5:38 PM > > To: 'Andrew Newton'; 'Livingood, Jason'; 'David Meyer';=20 > > speermint@ietf.org > > Cc: 'RAI ADs' > > Subject: [Speermint] FW: Preliminary BOF proposals due soon > >=20 > >=20 > >=20 > > Andrew Newton and I will be proposing a BOF on SPEERMINT=20 > Provisioning=20 > > issues for IETF 68 in Prague. > >=20 > > If anyone has topic or is considering producing drafts related to=20 > > provisioning issues please let Andy or I know. > >=20 > > > -----Original Message----- > > > From: IETF Chair [mailto:chair@ietf.org] > > > Sent: Tuesday, December 19, 2006 3:39 AM > > > To: IETF Announcement list > > > Subject: Preliminary BOF proposals due soon > > > > > > As for the previous IETF, we're asking for preliminary=20 > BOF proposals > > to be > > > sent to the appropriate Area Director a little earlier,=20 > by January 15. > > > Even sooner would be better! > > > > > > Full list of dates: > > > http://www.ietf.org/meetings/68-cutoff_dates.html > > > > > > BOF wiki: > > > http://www1.tools.ietf.org/bof/trac/wiki > > > > > > Hints: > > > http://tools.ietf.org/html/draft-narten-successful-bof > > > > > > Brian Carpenter > > > > > > _______________________________________________ > > > IETF-Announce mailing list > > > IETF-Announce@ietf.org > > > https://www1.ietf.org/mailman/listinfo/ietf-announce > >=20 > >=20 > > _______________________________________________ > > Speermint mailing list > > Speermint@ietf.org > > https://www1.ietf.org/mailman/listinfo/speermint >=20 >=20 > _______________________________________________ > Speermint mailing list > Speermint@ietf.org > https://www1.ietf.org/mailman/listinfo/speermint >=20 _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint From speermint-bounces@ietf.org Tue Dec 19 16:29:29 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwmWO-0000xi-0D; Tue, 19 Dec 2006 16:29:12 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwmWM-0000xa-H1 for speermint@ietf.org; Tue, 19 Dec 2006 16:29:10 -0500 Received: from m106.maoz.com ([205.167.76.9]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwmWI-000052-5e for speermint@ietf.org; Tue, 19 Dec 2006 16:29:10 -0500 Received: from m106.maoz.com (localhost.localdomain [127.0.0.1]) by m106.maoz.com (8.13.8/8.13.8) with ESMTP id kBJLSv6q011994; Tue, 19 Dec 2006 13:28:57 -0800 Received: (from dmm@localhost) by m106.maoz.com (8.13.8/8.12.11/Submit) id kBJLSlVQ011993; Tue, 19 Dec 2006 13:28:47 -0800 X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f Date: Tue, 19 Dec 2006 13:28:46 -0800 From: David Meyer To: "Uzelac, Adam" Subject: Re: [Speermint] FW: Preliminary BOF proposals due soon Message-ID: <20061219212846.GB11964@1-4-5.net> References: <019e01c723aa$17e514d0$22f0a544@cis.neustar.com> Mime-Version: 1.0 In-Reply-To: User-Agent: Mutt/1.4.1i X-public-key: http://www.1-4-5.net/~dmm/public-key.asc X-gpg-fingerprint: 2409 8B50 B389 A307 BA5C 2A16 3918 03D6 A099 D8A7 X-philosophy: "I find your lack of faith disturbing." -- Darth Vader, Star Wars Episode IV. X-Spam-Score: 0.0 (/) X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228 Cc: RAI ADs , speermint@ietf.org, David Schwartz , "Livingood, Jason" X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0449312245==" Errors-To: speermint-bounces@ietf.org --===============0449312245== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZoaI/ZTpAVc4A5k6" Content-Disposition: inline --ZoaI/ZTpAVc4A5k6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 19, 2006 at 03:18:56PM -0500, Uzelac, Adam wrote: > Not only an IETF ring, but also a holiday ring!!! Candy canes and all. > ;) >=20 > Happy Holidays one and all, I hope this email finds you well. Likewise. Safe and happy holidays to all of you and your families. --dmm --ZoaI/ZTpAVc4A5k6 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFFiFmOORgD1qCZ2KcRAuvoAKCLxk6o293sngkLPhTTbFR+dgQkmwCfRMOf /ifWAQN8Oz+R0Mryc8Jc6eI= =NVSX -----END PGP SIGNATURE----- --ZoaI/ZTpAVc4A5k6-- --===============0449312245== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint --===============0449312245==-- From speermint-bounces@ietf.org Tue Dec 19 17:37:12 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwnZv-0003w4-OQ; Tue, 19 Dec 2006 17:36:55 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwnZu-0003te-95 for speermint@ietf.org; Tue, 19 Dec 2006 17:36:54 -0500 Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwnZr-0002bp-UY for speermint@ietf.org; Tue, 19 Dec 2006 17:36:54 -0500 Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-2.cisco.com with ESMTP; 19 Dec 2006 17:36:52 -0500 X-IronPort-AV: i="4.12,188,1165208400"; d="scan'208"; a="109885474:sNHT52462988" Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id kBJMap7a006149; Tue, 19 Dec 2006 17:36:51 -0500 Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id kBJMapvo014950; Tue, 19 Dec 2006 17:36:51 -0500 (EST) Received: from xmb-rtp-20b.amer.cisco.com ([64.102.31.53]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 19 Dec 2006 17:36:51 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Speermint] FW: Preliminary BOF proposals due soon Date: Tue, 19 Dec 2006 17:36:47 -0500 Message-ID: <072C5B76F7CEAB488172C6F64B30B5E3025AA066@xmb-rtp-20b.amer.cisco.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Speermint] FW: Preliminary BOF proposals due soon Thread-Index: AccjSWNdXUPAEzfrRSm4yvIVZU6iiAAOYF0gAAHWoVAAB+WfgAAFEWJg From: "Michael Hammer \(mhammer\)" To: , "David Schwartz" , "Andrew Newton" , "Livingood, Jason" , "David Meyer" , X-OriginalArrivalTime: 19 Dec 2006 22:36:51.0028 (UTC) FILETIME=[2D124940:01C723BE] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3027; t=1166567811; x=1167431811; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=mhammer@cisco.com; z=From:=20=22Michael=20Hammer=20\(mhammer\)=22=20 |Subject:=20RE=3A=20[Speermint]=20FW=3A=20Preliminary=20BOF=20proposals=2 0due=20soon |Sender:=20 |To:=20, =20=22David=20Schwartz=22=20, =0A=20=20=20=20=20=20=20=20=22Andrew=20Newton=22=20, =0A=20=20=20=20=20=20=20=20=22Livingood, =20Jason=22=20, =0A=20=20=20=20=20=20=20=20=22David=20Meyer=22=20,=20; bh=0k8asqJvvHicKfJvOfq5bKccnSMASRq8K9XoJO3dKu0=; b=FNqx0VmEYM4MkGyyORotNSI0HnnJ1B9MC1JJwt/VpFLl6qhVq1g3QVfMsUTNUT2aIkdbbxdY nHNoITdbpEdWn0EJotFSs9ek/L65+b+Ys/7XFLiDZE9x7wUP7UbV3NLn; Authentication-Results: rtp-dkim-1; header.From=mhammer@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86 Cc: RAI ADs X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: speermint-bounces@ietf.org That is a good one. Happy Holidays all. Mike > -----Original Message----- > From: Richard Shockey [mailto:richard@shockey.us]=20 > Sent: Tuesday, December 19, 2006 3:13 PM > To: 'David Schwartz'; 'Andrew Newton'; 'Livingood, Jason';=20 > 'David Meyer'; speermint@ietf.org > Cc: 'RAI ADs' > Subject: RE: [Speermint] FW: Preliminary BOF proposals due soon >=20 >=20 >=20 > BTW you can also put on catchy BOF name thinking caps on ..feel free. >=20 > My current favorite is Peppermint. >=20 > Provisioning Extenstions in Peering Registries for Multimedia=20 > INTerconnection. >=20 > Has that nice IETF ring to it ..dont you think? >=20 >=20 > > -----Original Message----- > > From: David Schwartz [mailto:David.Schwartz@Kayote.com] > > Sent: Tuesday, December 19, 2006 11:26 AM > > To: richard@shockey.us; Andrew Newton; Livingood, Jason;=20 > David Meyer;=20 > > speermint@ietf.org > > Cc: RAI ADs > > Subject: RE: [Speermint] FW: Preliminary BOF proposals due soon > >=20 > > I am 85% finished on an a draft describing requirements we have=20 > > accumulated at XConnect. Hope to have this out by the end=20 > of the year. > >=20 > > David > >=20 > > -----Original Message----- > > From: Richard Shockey [mailto:richard@shockey.us] > > Sent: Tuesday, December 19, 2006 5:38 PM > > To: 'Andrew Newton'; 'Livingood, Jason'; 'David Meyer';=20 > > speermint@ietf.org > > Cc: 'RAI ADs' > > Subject: [Speermint] FW: Preliminary BOF proposals due soon > >=20 > >=20 > >=20 > > Andrew Newton and I will be proposing a BOF on SPEERMINT=20 > Provisioning=20 > > issues for IETF 68 in Prague. > >=20 > > If anyone has topic or is considering producing drafts related to=20 > > provisioning issues please let Andy or I know. > >=20 > > > -----Original Message----- > > > From: IETF Chair [mailto:chair@ietf.org] > > > Sent: Tuesday, December 19, 2006 3:39 AM > > > To: IETF Announcement list > > > Subject: Preliminary BOF proposals due soon > > > > > > As for the previous IETF, we're asking for preliminary=20 > BOF proposals > > to be > > > sent to the appropriate Area Director a little earlier,=20 > by January 15. > > > Even sooner would be better! > > > > > > Full list of dates: > > > http://www.ietf.org/meetings/68-cutoff_dates.html > > > > > > BOF wiki: > > > http://www1.tools.ietf.org/bof/trac/wiki > > > > > > Hints: > > > http://tools.ietf.org/html/draft-narten-successful-bof > > > > > > Brian Carpenter > > > > > > _______________________________________________ > > > IETF-Announce mailing list > > > IETF-Announce@ietf.org > > > https://www1.ietf.org/mailman/listinfo/ietf-announce > >=20 > >=20 > > _______________________________________________ > > Speermint mailing list > > Speermint@ietf.org > > https://www1.ietf.org/mailman/listinfo/speermint >=20 >=20 > _______________________________________________ > Speermint mailing list > Speermint@ietf.org > https://www1.ietf.org/mailman/listinfo/speermint >=20 _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint From speermint-bounces@ietf.org Tue Dec 19 18:07:39 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gwo3U-0004Sz-V6; Tue, 19 Dec 2006 18:07:28 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gwo3T-0004Sb-RI for speermint@ietf.org; Tue, 19 Dec 2006 18:07:27 -0500 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gwo3S-0007KA-F4 for speermint@ietf.org; Tue, 19 Dec 2006 18:07:27 -0500 Received: from RSHOCKEYLTXP (h-68-165-240-34.mclnva23.covad.net [68.165.240.34]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id kBJN74Wj010025; Tue, 19 Dec 2006 15:07:15 -0800 From: "Richard Shockey" To: "'Uzelac, Adam'" , "'David Schwartz'" , "'Andrew Newton'" , "'Livingood, Jason'" , "'David Meyer'" , Subject: RE: [Speermint] FW: Preliminary BOF proposals due soon Date: Tue, 19 Dec 2006 18:06:32 -0500 Message-ID: <031f01c723c2$55a988b0$22f0a544@cis.neustar.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 In-Reply-To: Thread-Index: AccjSWNdXUPAEzfrRSm4yvIVZU6iiAAOYF0gAAHWoVAAB+WfgAAANcjwAAXaLdA= X-SongbirdInformation: support@songbird.com for more information X-Songbird: Clean X-Songbird-From: richard@shockey.us X-Spam-Score: 0.0 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 Cc: 'RAI ADs' X-BeenThere: speermint@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: richard@shockey.us List-Id: Mailing list for the speermint working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: speermint-bounces@ietf.org Oh geez .. that's right and its even politically correct Ho Ho and all that ... > -----Original Message----- > From: Uzelac, Adam [mailto:Adam.Uzelac@globalcrossing.com] > Sent: Tuesday, December 19, 2006 3:19 PM > To: richard@shockey.us; David Schwartz; Andrew Newton; Livingood, Jason; > David Meyer; speermint@ietf.org > Cc: RAI ADs > Subject: RE: [Speermint] FW: Preliminary BOF proposals due soon > > Not only an IETF ring, but also a holiday ring!!! Candy canes and all. > ;) > > Happy Holidays one and all, I hope this email finds you well. > > -AU > > > -----Original Message----- > > From: Richard Shockey [mailto:richard@shockey.us] > > Sent: Tuesday, December 19, 2006 3:13 PM > > To: 'David Schwartz'; 'Andrew Newton'; 'Livingood, Jason'; > > 'David Meyer'; speermint@ietf.org > > Cc: 'RAI ADs' > > Subject: RE: [Speermint] FW: Preliminary BOF proposals due soon > > > > > > > > BTW you can also put on catchy BOF name thinking caps on ..feel free. > > > > My current favorite is Peppermint. > > > > Provisioning Extenstions in Peering Registries for Multimedia > > INTerconnection. > > > > Has that nice IETF ring to it ..dont you think? > > > > _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint