[Speermint] RE: Closing Issue SIP Interoperablity (Section 4.3: draft-khan-ip-serv-arch-02)
"Francois D. Menard" <fmenard@xittelecom.com> Sat, 27 May 2006 01:39 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fjnlm-0006t9-T0; Fri, 26 May 2006 21:39:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fjnll-0006t4-Bg for speermint@ietf.org; Fri, 26 May 2006 21:39:09 -0400
Received: from [205.151.208.34] (helo=fw.tr.xittelecom.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fjnlk-0003mG-3G for speermint@ietf.org; Fri, 26 May 2006 21:39:09 -0400
Received: from [192.168.2.139] (helo=gestionfm) by fw.tr.xittelecom.com with esmtp (Exim 3.36 #1 (Debian)) id 1Fv33W-0002kw-00; Mon, 26 Jun 2006 22:11:58 -0400
From: "Francois D. Menard" <fmenard@xittelecom.com>
To: 'James McEachern' <jmce@nortel.com>, "'Khan, Sohel Q [CTO]'" <Sohel.Q.Khan@sprint.com>, speermint@ietf.org
Date: Fri, 26 May 2006 21:36:48 -0400
Message-ID: <01e001c6812e$07fbf7b0$8b02a8c0@gestionfm>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <F1A1D21DA394814E824AC89F5A005BA30B467CB3@zcarhxm0.corp.nortel.com>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
Thread-Index: AcZ55c9pook8AV07QCuSGZUVJZHNwAAALQwwAAMtGwAAALabEAAtwXjAAPK/xLAAAMWBMAAFEnSQAADsacAAAXIwMAAAWSswAAMILuAAANiSfAAGpkGwABFyNDAABcvUoAAA7iiQAELeetAAAMAqIAAO6n1wACEPZuAAAmRecAAMESHQ
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Cc:
Subject: [Speermint] RE: Closing Issue SIP Interoperablity (Section 4.3: draft-khan-ip-serv-arch-02)
X-BeenThere: speermint@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mailing list for the speermint working group <speermint.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/speermint>, <mailto:speermint-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/speermint>
List-Post: <mailto:speermint@ietf.org>
List-Help: <mailto:speermint-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/speermint>, <mailto:speermint-request@ietf.org?subject=subscribe>
Errors-To: speermint-bounces@ietf.org
Sorry for introducing confusion. So it shall read: SIP Interoperability: SPEERMINT Signaling Function (SF) in general should support all SIP RFCs identified in the SIP hitchhiker's guide. The SF must minimally support RFC 3261, 3323, 3325, and lastly, 3263, should peering occur across the Public Internet. I just do not see a mandatory requirement for the SF to support 3263 whereas peering is not across the big I, say on a private IP network. I believe the scenario we are excluding is transitive betwene private IP and Public Internet. F. -- François D. Ménard Chargé de projet Xit télécom inc. 1350 rue Royale #800 Trois-Rivières, QC, G9A 4J4 Canada fmenard@xittelecom.com Tel: (819) 374-2556 ext. 268 Fax: (819) 374-0395 Cell: (819) 692-1383 -----Original Message----- From: James McEachern [mailto:jmce@nortel.com] Sent: 26 mai 2006 15:49 To: Khan, Sohel Q [CTO]; Francois D. Menard; speermint@ietf.org Subject: RE: Closing Issue SIP Interoperablity (Section 4.3: draft-khan-ip-serv-arch-02) Sohel, I believe the minimum list should be RFC 3261, 3323, and 3325 (perhaps also 3263?). Jim -----Original Message----- From: Khan, Sohel Q [CTO] [mailto:Sohel.Q.Khan@sprint.com] Sent: Friday, May 26, 2006 2:49 PM To: Francois D. Menard; Brian Rosen; McEachern, James [CAR:5N00:EXCH]; Stastny Richard; speermint@ietf.org; Michael Hammer (mhammer); David Meyer Subject: Closing Issue SIP Interoperablity (Section 4.3: draft-khan-ip-serv-arch-02) Thank you for all suggestions and comments on the SIP Interoperability (Section 4.3: draft-khan-ip-serv-arch-02) paragraph in Speermint Peering Architecture draft. Based on the discussion, I would propose to close the issue by replacing the current paragraph, "SIP Interoperability:TBD" with the following paragraph. "SIP Interoperability: SPEERMINT Signaling Function (SF) in general should support all SIP RFCs identified in the SIP hitchhiker's guide. The SF must minimally support RFC 3261, 3263, 3325, and 3326. A SPEERMINT SIP Profile document would recommend a rationale set of SIP profiles to perform smooth interoperability. The document will also contain information on the population of the header fields, particularly in context with phone numbers (e.164 and non-E.164). A SPEERMINT SIP Flow Document would recommend call flows and establishment of two-way TLS connections." Please do not criticize! Instead, suggest another paragraph or a better version of this paragraph. Sohel Khan, Ph.D. Technology Strategist Sprint-Nextel 913-794-1470 (office) 913-486-3145 (cell) _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint
- [Speermint] Closing Issue SIP Interoperablity (Se… Khan, Sohel Q [CTO]
- [Speermint] RE: Closing Issue SIP Interoperablity… James McEachern
- [Speermint] RE: Closing Issue SIP Interoperablity… Brian Rosen
- [Speermint] RE: Closing Issue SIP Interoperablity… Khan, Sohel Q [CTO]
- [Speermint] RE: Closing Issue SIP Interoperablity… Francois D. Menard