http://blog.gmane.org/gmane.ietf.rai.speermint hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.ietf.rai.speermint/2269 <pre> A new Request for Comments is now available in online RFC libraries. RFC 6406 Title: Session PEERing for Multimedia INTerconnect (SPEERMINT) Architecture Author: D. Malas, Ed., J. Livingood, Ed. Status: Informational Stream: IETF Date: November 2011 Mailbox: d.malas-AwJHAePZ/FCakBO8gow8eQ&lt; at &gt;public.gmane.org, Jason_Livingood-aUJzA63xOnoL9wKPcNvCOAC/G2K4zDHf&lt; at &gt;public.gmane.org Pages: 16 Characters: 35032 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-speermint-architecture-19.txt URL: http://www.rfc-editor.org/rfc/rfc6406.txt This document defines a peering architecture for the Session Initiation Protocol (SIP) and its functional components and interfaces. It also describes the components and the steps necessary to establish a session between two SIP Service Provider (SSP) peering domains. This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Session PEERing for Multimedia INTerconnect Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor-i4YTrOVFbXnQdKpFsAHx7g&lt; at &gt;public.gmane.org Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC </pre> rfc-editor-i4YTrOVFbXmRpAAqCnN02g< at >public.gmane.org 2011-11-05T01:29:37 http://comments.gmane.org/gmane.ietf.rai.speermint/2268 <pre> A new Request for Comments is now available in online RFC libraries. RFC 6405 Title: Voice over IP (VoIP) SIP Peering Use Cases Author: A. Uzelac, Ed., Y. Lee, Ed. Status: Informational Stream: IETF Date: November 2011 Mailbox: adam.uzelac-sy4M0opG+mbg68bSLmQ3W9BPR1lH4CV8&lt; at &gt;public.gmane.org, yiu_lee-aUJzA63xOnoL9wKPcNvCOAC/G2K4zDHf&lt; at &gt;public.gmane.org Pages: 23 Characters: 51354 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-speermint-voip-consolidated-usecases-18.txt URL: http://www.rfc-editor.org/rfc/rfc6405.txt This document depicts many common Voice over IP (VoIP) use cases for Session Initiation Protocol (SIP) peering. These use cases are categorized into static and on-demand, and then further sub- categorized into direct and indirect. These use cases are not an exhaustive set, but rather the most common use cases deployed today. This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Session PEERing for Multimedia INTerconnect Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor-i4YTrOVFbXnQdKpFsAHx7g&lt; at &gt;public.gmane.org Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC </pre> rfc-editor-i4YTrOVFbXmRpAAqCnN02g< at >public.gmane.org 2011-11-05T01:29:26 http://comments.gmane.org/gmane.ietf.rai.speermint/2265 <pre>Folks, as you know, the plan is to close down the SPEERMINT WG as soon as the last documents are published as RFCs (and that will happen shortly). The only decision that remains to be made is whether or not we also close the mailing list. If I do not hear otherwise, I will request it to be closed as well. If for some reason you want this mailing list to remain open, let me know. Cheers, Gonzalo </pre> Gonzalo Camarillo 2011-10-17T20:31:56 http://comments.gmane.org/gmane.ietf.rai.speermint/2264 <pre>A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Session PEERing for Multimedia INTerconnect Working Group of the IETF. Title : VoIP SIP Peering Use Cases Author(s) : Adam Uzelac Comcast Cable Filename : draft-ietf-speermint-voip-consolidated-usecases-19.txt Pages : 25 Date : 2011-10-17 This document depicts many common Voice over IP (VoIP) use cases for Session Initiation Protocol (SIP) Peering. These use cases are categorized into static and on-demand, and then further sub- categorized into direct and indirect. These use cases are not an exhaustive set, but rather the most common use cases deployed today. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-speermint-voip-consolidated-usecases-19.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ This Internet-Draft can be retrieved at: ftp://ftp.ietf.org/internet-drafts/draft-ietf-speermint-voip-consolidated-usecases-19.txt </pre> internet-drafts-EgrivxUAwEY< at >public.gmane.org 2011-10-17T15:15:20 http://comments.gmane.org/gmane.ietf.rai.speermint/2263 <pre>The IESG has approved the following document: - 'Session Peering for Multimedia Interconnect (SPEERMINT) Security Threats and Suggested Countermeasures' (draft-ietf-speermint-voipthreats-09.txt) as an Informational RFC This document is the product of the Session PEERing for Multimedia INTerconnect Working Group. The IESG contact persons are Gonzalo Camarillo and Robert Sparks. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-speermint-voipthreats/ 1 - Technical Summary This document describes potential security threats related to SPEERMINT. 2 - Working Group Summary There is consensus in the WG to publish this document. A Working Group Last Call has been issued, and we have achieved consensus and resolved all concerns. All changes suggested by the WG have been made to this draft. A NITS review has also been performed and those changes made as well. 3 - Document Quality Good quality - no issues 4 - Personnel Document Shepherd: Jason Livingood Responsible AD: Gonzalo Camarillo </pre> The IESG 2011-09-12T18:42:13 http://comments.gmane.org/gmane.ietf.rai.speermint/2261 <pre>A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Session PEERing for Multimedia INTerconnect Working Group of the IETF. Title : Session Peering for Multimedia Interconnect (SPEERMINT) Security Threats and Suggested Countermeasures Author(s) : Jan Seedorf Saverio Niccolini Eric Chen Hendrik Scholz Filename : draft-ietf-speermint-voipthreats-09.txt Pages : 29 Date : 2011-08-16 The Session PEERing for Multimedia INTerconnect working group (SPEERMINT) provides a peering framework that leverages the building blocks of existing IETF-defined protocols such as SIP and ENUM for the interconnection between SIP Service Providers (SSPs). The objective of this document is to identify and enumerate SPEERMINT- specific threat vectors and to give guidance for implementers on selecting appropriate countermeasures. Security requirements for SPEERMINT which have been derived from the threats detailed in this document can be found in RFC 6271; this document provides concrete countermeasures to meet those SPEERMINT security requirements. In this document, the different security threats related to SPEERMINT are classified into threats to the Lookup Function (LUF), to the Location Routing Function (LRF), to the Signaling Function (SF), and to the Media Function (MF) of a specific SIP Service Provider. Various instances of the threats are briefly introduced inside the classification. Finally, existing security solutions for SIP and RTP/RTCP are presented to describe countermeasures currently available for such threats. Each SSP may have connections to one or more remote SSPs through peering or transit contracts. A potentially compromised remote SSP which attacks other SSPs is out of the scope of this document; this document focuses on attacks on an SSP from outside the trust domain such an SSP may have with other SSPs. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-speermint-voipthreats-09.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ This Internet-Draft can be retrieved at: ftp://ftp.ietf.org/internet-drafts/draft-ietf-speermint-voipthreats-09.txt </pre> internet-drafts-EgrivxUAwEY< at >public.gmane.org 2011-08-16T08:05:56 http://comments.gmane.org/gmane.ietf.rai.speermint/2258 <pre>FYI. The email below went to the SPLICES mailing list for some reason. Cheers, Gonzalo -------- Original Message -------- Subject: [splices] RFC 6271 on Requirements for SIP-Based Session Peering Date: Wed, 29 Jun 2011 00:35:20 +0200 From: rfc-editor-i4YTrOVFbXmRpAAqCnN02g&lt; at &gt;public.gmane.org &lt;rfc-editor-i4YTrOVFbXmRpAAqCnN02g&lt; at &gt;public.gmane.org&gt; To: ietf-announce-EgrivxUAwEY&lt; at &gt;public.gmane.org &lt;ietf-announce-EgrivxUAwEY&lt; at &gt;public.gmane.org&gt;, rfc-dist-i4YTrOVFbXmRpAAqCnN02g&lt; at &gt;public.gmane.org &lt;rfc-dist-i4YTrOVFbXmRpAAqCnN02g&lt; at &gt;public.gmane.org&gt; CC: splices-EgrivxUAwEY&lt; at &gt;public.gmane.org &lt;splices-EgrivxUAwEY&lt; at &gt;public.gmane.org&gt;, rfc-editor-i4YTrOVFbXmRpAAqCnN02g&lt; at &gt;public.gmane.org &lt;rfc-editor-i4YTrOVFbXmRpAAqCnN02g&lt; at &gt;public.gmane.org&gt; A new Request for Comments is now available in online RFC libraries. RFC 6271 Title: Requirements for SIP-Based Session Peering Author: J-F. Mule Status: Informational Stream: IETF Date: June 2011 Mailbox: jf.mule-AwJHAePZ/FCakBO8gow8eQ&lt; at &gt;public.gmane.org Pages: 23 Characters: 54492 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-speermint-requirements-11.txt URL: http://www.rfc-editor.org/rfc/rfc6271.txt This memo captures protocol requirements to enable session peering of voice, presence, instant messaging, and other types of multimedia traffic. This informational document is intended to link the various use cases described for session peering to protocol solutions. This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Session PEERing for Multimedia INTerconnect Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor-i4YTrOVFbXnQdKpFsAHx7g&lt; at &gt;public.gmane.org Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC _______________________________________________ splices mailing list splices-EgrivxUAwEY&lt; at &gt;public.gmane.org https://www.ietf.org/mailman/listinfo/splices </pre> Gonzalo Camarillo 2011-06-29T08:22:29 http://comments.gmane.org/gmane.ietf.rai.speermint/2257 <pre> Ich bin abwesend und kehre am 04.04.2011 zurück. Ich werde Ihre Nachricht nach meiner Rückkehr beantworten. Hinweis: Dies ist eine automatische Antwort auf Ihre Nachricht "Speermint Digest, Vol 63, Issue 3" gesendet am 28.3.11 21:00:03. Diese ist die einzige Benachrichtigung, die Sie empfangen werden, während diese Person abwesend ist. _______________________________________________ Speermint mailing list Speermint&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/speermint </pre> Heike Schmidt-Hunkel 2011-03-30T15:11:19 http://comments.gmane.org/gmane.ietf.rai.speermint/2256 <pre>Dear all, In the latest version of the draft (which we just posted, see below) we have addressed many of the DICUSSES we had received from the IESG (we believe we have addressed the ones from Sean Turner, Tim Polk, and Alexey Melnikov). However, we did not yet address all the DISCUSSES and COMMENTS (the ones from Peter Saint-Andre and Robert Sparks we did not yet get to). - Jan -----Original Message----- From: speermint-bounces-EgrivxUAwEY&lt; at &gt;public.gmane.org [mailto:speermint-bounces-EgrivxUAwEY&lt; at &gt;public.gmane.org] On Behalf Of Internet-Drafts-EgrivxUAwEY&lt; at &gt;public.gmane.org Sent: Montag, 28. März 2011 14:45 To: i-d-announce-EgrivxUAwEY&lt; at &gt;public.gmane.org Cc: speermint-EgrivxUAwEY&lt; at &gt;public.gmane.org Subject: [Speermint] I-D Action:draft-ietf-speermint-voipthreats-08.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Session PEERing for Multimedia INTerconnect Working Group of the IETF. Title : Session Peering for Multimedia Interconnect (SPEERMINT) Security Threats and Suggested Countermeasures Author(s) : J. Seedorf, et al. Filename : draft-ietf-speermint-voipthreats-08.txt Pages : 27 Date : 2011-03-28 The Session PEERing for Multimedia INTerconnect working group (SPEERMINT) provides a peering framework that leverages the building blocks of existing IETF-defined protocols such as SIP and ENUM for the interconnection between SIP service providers. The objective of this document is to identify and enumerate SPEERMINT-specific threat vectors and to give guidance for implementers on selecting appropriate countermeasures. Security requirements for SPEERMINT which have been derived from the threats detailed in this document can be found in draft-ietf-speermint-requirements; this document provides concrete countermeasures to meet those SPEERMINT security requirements. In this document, the different security threats related to SPEERMINT are classified into threats to the Lookup Function (LUF), to the Location Routing Function (LRF), to the Signaling Function (SF), and to the Media Function (MF) of a specific SIP Service Provider (SSP). Various instances of the threats are briefly introduced inside the classification. Finally, existing security solutions for SIP and RTP/RTCP are presented to describe countermeasures currently available for such threats. Each SSP may have connections to one or more remote SSPs through peering or transit contracts. A potentially compromised remote SSP which attacks other SSPs is out of the scope of this document; this document focuses on attacks on an SSP from outside the trust domain such an SSP may have with other SSPs. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-speermint-voipthreats-08.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ Speermint mailing list Speermint-EgrivxUAwEY&lt; at &gt;public.gmane.org https://www.ietf.org/mailman/listinfo/speermint </pre> Jan Seedorf 2011-03-28T14:22:17 http://comments.gmane.org/gmane.ietf.rai.speermint/2255 <pre>A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Session PEERing for Multimedia INTerconnect Working Group of the IETF. Title : Session Peering for Multimedia Interconnect (SPEERMINT) Security Threats and Suggested Countermeasures Author(s) : J. Seedorf, et al. Filename : draft-ietf-speermint-voipthreats-08.txt Pages : 27 Date : 2011-03-28 The Session PEERing for Multimedia INTerconnect working group (SPEERMINT) provides a peering framework that leverages the building blocks of existing IETF-defined protocols such as SIP and ENUM for the interconnection between SIP service providers. The objective of this document is to identify and enumerate SPEERMINT-specific threat vectors and to give guidance for implementers on selecting appropriate countermeasures. Security requirements for SPEERMINT which have been derived from the threats detailed in this document can be found in draft-ietf-speermint-requirements; this document provides concrete countermeasures to meet those SPEERMINT security requirements. In this document, the different security threats related to SPEERMINT are classified into threats to the Lookup Function (LUF), to the Location Routing Function (LRF), to the Signaling Function (SF), and to the Media Function (MF) of a specific SIP Service Provider (SSP). Various instances of the threats are briefly introduced inside the classification. Finally, existing security solutions for SIP and RTP/RTCP are presented to describe countermeasures currently available for such threats. Each SSP may have connections to one or more remote SSPs through peering or transit contracts. A potentially compromised remote SSP which attacks other SSPs is out of the scope of this document; this document focuses on attacks on an SSP from outside the trust domain such an SSP may have with other SSPs. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-speermint-voipthreats-08.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. _______________________________________________ Speermint mailing list Speermint-EgrivxUAwEY&lt; at &gt;public.gmane.org https://www.ietf.org/mailman/listinfo/speermint </pre> Internet-Drafts-EgrivxUAwEY< at >public.gmane.org 2011-03-28T12:45:06 http://comments.gmane.org/gmane.ietf.rai.speermint/2254 <pre>The IESG has approved the following document: - 'Requirements for SIP-based Session Peering' (draft-ietf-speermint-requirements-11.txt) as an Informational RFC This document is the product of the Session PEERing for Multimedia INTerconnect Working Group. The IESG contact persons are Gonzalo Camarillo and Robert Sparks. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-speermint-requirements/ Technical Summary This document captures protocol requirements to enable session peering of voice, presence, instant messaging and other types of multimedia traffic. It is based on the use cases that have been described in the SPEERMINT working group. This informational document is intended to link the session peering use cases to protocol solutions. Working Group Summary There is consensus in the WG to publish this document. Several Working Group Last Calls have been issued, and we have finally achieved consensus and resolved all concerns. All changes suggested by the WG have been made to this draft. A NITS review has also been performed by our secretary, and those changes made as well. Document Quality Good quality - no issues Personnel Document Shepherd: Jason Livingood Responsible AD: Gonzalo Camarillo IANA Experts Required: No </pre> The IESG 2011-03-15T15:25:35 http://comments.gmane.org/gmane.ietf.rai.speermint/2252 <pre>The IESG has approved the following document: - 'Session PEERing for Multimedia INTerconnect Architecture' (draft-ietf-speermint-architecture-19.txt) as an Informational RFC This document is the product of the Session PEERing for Multimedia INTerconnect Working Group. The IESG contact persons are Gonzalo Camarillo and Robert Sparks. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-speermint-architecture/ Technical Summary This document defines a peering architecture for the SIP between two or more service provider domains. Working Group Summary There is consensus in the WG to publish this document. A Working Group Last Call has been issued, and we have achieved consensus and resolved all concerns. All changes suggested by the WG have been made to this draft. A NITS review has also been performed and those changes made as well. Document Quality Good quality - no issues Personnel Document Shepherd: Jason Livingood Responsible AD: Gonzallo Camarillo IANA Experts Required: No </pre> The IESG 2011-02-22T19:26:54 http://comments.gmane.org/gmane.ietf.rai.speermint/2251 <pre>Folks, FYI: this is the status of our WG items: https://datatracker.ietf.org/wg/speermint/ I have requested the approval of the architecture draft. The requirements draft will be approved as soon as its editor performs a few minor changes requested to address comments on the draft. The use cases draft is in the RFC Editor's queue. I have placed the voipthreats draft on the agenda of the IESG telechat on March 3rd. Cheers, Gonzalo </pre> Gonzalo Camarillo 2011-02-22T16:04:04 http://comments.gmane.org/gmane.ietf.rai.speermint/2248 <pre>A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Session PEERing for Multimedia INTerconnect Working Group of the IETF. Title : Session PEERing for Multimedia INTerconnect Architecture Author(s) : D. Malas, J. Livingood Filename : draft-ietf-speermint-architecture-18.txt Pages : 18 Date : 2011-02-17 This document defines a peering architecture for the Session Initiation Protocol (SIP), its functional components and interfaces. It also describes the components and the steps necessary to establish a session between two SIP Service Provider (SSP) peering domains. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-speermint-architecture-18.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. _______________________________________________ Speermint mailing list Speermint-EgrivxUAwEY&lt; at &gt;public.gmane.org https://www.ietf.org/mailman/listinfo/speermint </pre> Internet-Drafts-EgrivxUAwEY< at >public.gmane.org 2011-02-17T20:00:01 http://comments.gmane.org/gmane.ietf.rai.speermint/2244 <pre>From Eric Burger – worth checking out: // The SIP Forum is holding its first SIP Network Operators Conference (SIPNOC) on April 25th to the 27th, 2011, at the Hyatt Dulles Hotel in Herndon, Virginia – a few minutes from Dulles International Airport. SIPNOC is a technical conference developed for service providers and carriers to gather and discuss the challenges of deploying and implementing SIP-based communications technology, and to share the best-practices and strategies that enable the successful and profitable operation of SIP-based services and applications in fixed and mobile IP network environments. Unlike other events, this conference is for SIP network operations personnel, such as NOC engineers, rather than a high-level conference for executives. For more information about SIPNOC, including the preliminary schedule of events and other important details about the conference, please visithttp://www.sipnoc.org&lt;http://www.sipnoc.org/&gt;. The SIPNOC Program Committee is seeking proposals for presentations, panels, or BOFs (Birds-Of-a-Feather sessions) for the SIPNOC 2011 program. We invite presentations highlighting issues relating to SIP network deployments. Operators are encouraged to present on successes, issues, and concerns found in their deployments. Vendors are encouraged to work with operators to present real-world deployment experiences. The deadline for submission of presentation/paper abstracts and draft slides is February 21, 2011. Full details of the submission process and policies, as well as other SIPNOC 2011 dates of interest, can be found at: http://www.sipforum.org/content/view/374/275/ I look forward to seeing you at the event! Best Wishes, Eric Burger SIPNOC Chair _______________________________________________ Speermint mailing list Speermint-EgrivxUAwEY&lt; at &gt;public.gmane.org https://www.ietf.org/mailman/listinfo/speermint </pre> Livingood, Jason 2011-02-02T13:44:23 http://comments.gmane.org/gmane.ietf.rai.speermint/2243 <pre>Hi, please, note the following review on the general IETF list. The IESG will be discussing this draft on February 3rd. Cheers, Gonzalo -------- Original Message -------- Subject: opsdir review of draft-ietf-speermint-architecture-17.txt Date: Tue, 25 Jan 2011 17:38:05 +0100 From: Bert (IETF) Wijnen &lt;bertietf-CDCpF2HQJvjR7s880joybQ&lt; at &gt;public.gmane.org&gt; To: Jason_Livingood-aUJzA63xOnoL9wKPcNvCOAC/G2K4zDHf&lt; at &gt;public.gmane.org &lt;Jason_Livingood-aUJzA63xOnoL9wKPcNvCOAC/G2K4zDHf&lt; at &gt;public.gmane.org&gt;,d.malas-AwJHAePZ/FCakBO8gow8eQ&lt; at &gt;public.gmane.org &lt;d.malas-AwJHAePZ/FCakBO8gow8eQ&lt; at &gt;public.gmane.org&gt; CC: ops-dir-EgrivxUAwEY&lt; at &gt;public.gmane.org &lt;ops-dir-EgrivxUAwEY&lt; at &gt;public.gmane.org&gt;, ietf-EgrivxUAwEY&lt; at &gt;public.gmane.org &gt;&gt; "ietf-EgrivxUAwEY&lt; at &gt;public.gmane.org" &lt;ietf-EgrivxUAwEY&lt; at &gt;public.gmane.org&gt; I was appointed to review this document from an OPS-DIR point of vie, i,e, to check for operational or management aspects. This are is not my space of expertise, so don't rely too much on my report. I think that there might be some operational aspects in the sense that sometimes secure/encrypted connections are needed and other times it may be OK to use unencrypted connections if they are inside the same secure building. So is there not something for an operator to configure in such cases? typo: Section 4, 4th bullet, 2nd sub bullet: * LUF can communicator with SF and SBE s/cator/cate/ Section 5.1.1.2 2nd para: If an im: or pres: URI is chosen based on an "E2U+im" [RFC3861] or "E2U+pres" [RFC3953] enumserver, the SSP follows the procedures for resolving these URIs to URIs for specific protocols such a SIP or XMPP as described in the previous section. s/such a SIP/such as SIP/ Bert Wijnen _______________________________________________ Ietf mailing list Ietf-EgrivxUAwEY&lt; at &gt;public.gmane.org https://www.ietf.org/mailman/listinfo/ietf </pre> Gonzalo Camarillo 2011-01-27T07:26:06 http://comments.gmane.org/gmane.ietf.rai.speermint/2237 <pre>A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Session PEERing for Multimedia INTerconnect Working Group of the IETF. Title : Session PEERing for Multimedia INTerconnect Architecture Author(s) : D. Malas, J. Livingood Filename : draft-ietf-speermint-architecture-17.txt Pages : 17 Date : 2010-12-20 This document defines a peering architecture for the Session Initiation Protocol (SIP) [RFC3261], its functional components and interfaces. It also describes the components and the steps necessary to establish a session between two SIP Service Provider (SSP) peering domains. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-speermint-architecture-17.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. _______________________________________________ Speermint mailing list Speermint-EgrivxUAwEY&lt; at &gt;public.gmane.org https://www.ietf.org/mailman/listinfo/speermint </pre> Internet-Drafts-EgrivxUAwEY< at >public.gmane.org 2010-12-20T22:00:01 http://comments.gmane.org/gmane.ietf.rai.speermint/2232 <pre>Hi, I received a publication request for the following draft a few days ago: https://datatracker.ietf.org/doc/draft-ietf-speermint-architecture/ Please, find below a few comments and questions on the draft. Thanks, Gonzalo Title: I leave it up to the editors whether or not they want to expand the acronym SPEERMINT. Given that it is exanded in the Introduction, it should probably be expanded also in the title. First sentence in the Abstract and first sentence in the Introduction: s/it's/its/ First paragraph in the Introduction: "...of a SIP Service providers [RFC5486] network." It should be Provider's. Also, when capitalizing Provider, expand the SSP acronym there, and not in the next sentence. When the reader reaches Figure 1, there are a lot of new acronyms. Having a terminology section after the Introduction would help readers understand the figure. Otherwise, readers need to consult other RFCs or check the meaning of the acronyms later in this document. Acronyms such as UA should also be expanded on their first use or added to the Terminology section. Section 3. Why is the sending of the BYE (step 5) more likely to be performed by the target SSP than by the originating SSP? Section 5.1.1.2 s/chosen for based on/chosen based on/ Section 5.1.2: "not all of them may be used". Does this mean that the LRF MUST NOT use all of them or that the LRF does not need to necessarily use all of them? Section 5.1.3 When communicating with another SSP, entities compliant to this document should select a TLS-protected transport for communication from the originating (or indirect) SSP to the receiving SSP if available, as described further in Section 5.2.1. This "should" sounds like a normative SHOULD. If this normatively defined somewhere else (i.e., in another document)? In general, there are a set of instructions that are given without using normative language. What is the intention of those instructions? ID nits gives the following warning: == Unused Reference: 'I-D.ietf-speermint-voip-consolidated-usecases' is defined on line 609, but no explicit reference was found in the text </pre> Gonzalo Camarillo 2010-11-17T13:40:40 http://comments.gmane.org/gmane.ietf.rai.speermint/2230 <pre>A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Session PEERing for Multimedia INTerconnect Working Group of the IETF. Title : SPEERMINT Peering Architecture Author(s) : D. Malas, J. Livingood Filename : draft-ietf-speermint-architecture-16.txt Pages : 15 Date : 2010-11-08 This document defines a peering architecture for the Session Initiation Protocol (SIP) [RFC3261], it's functional components and interfaces. It also describes the components and the steps necessary to establish a session between two SIP Service Provider (SSP) peering domains. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-speermint-architecture-16.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. _______________________________________________ Speermint mailing list Speermint-EgrivxUAwEY&lt; at &gt;public.gmane.org https://www.ietf.org/mailman/listinfo/speermint </pre> Internet-Drafts-EgrivxUAwEY< at >public.gmane.org 2010-11-09T02:15:35 http://comments.gmane.org/gmane.ietf.rai.speermint/2229 <pre>A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Session PEERing for Multimedia INTerconnect Working Group of the IETF. Title : SPEERMINT Peering Architecture Author(s) : D. Malas, J. Livingood Filename : draft-ietf-speermint-architecture-15.txt Pages : 15 Date : 2010-11-07 This document defines a peering architecture for the Session Initiation Protocol (SIP) [RFC3261], it's functional components and interfaces. It also describes the components and the steps necessary to establish a session between two SIP Service Provider (SSP) peering domains. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-speermint-architecture-15.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. _______________________________________________ Speermint mailing list Speermint-EgrivxUAwEY&lt; at &gt;public.gmane.org https://www.ietf.org/mailman/listinfo/speermint </pre> Internet-Drafts-EgrivxUAwEY< at >public.gmane.org 2010-11-09T02:15:28 http://comments.gmane.org/gmane.ietf.rai.speermint/2228 <pre>A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Session PEERing for Multimedia INTerconnect Working Group of the IETF. Title : SPEERMINT Peering Architecture Author(s) : D. Malas, J. Livingood Filename : draft-ietf-speermint-architecture-14.txt Pages : 15 Date : 2010-11-07 This document defines a peering architecture for the Session Initiation Protocol (SIP) [RFC3261], it's functional components and interfaces. It also describes the components and the steps necessary to establish a session between two SIP Service Provider (SSP) peering domains. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-speermint-architecture-14.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. _______________________________________________ Speermint mailing list Speermint-EgrivxUAwEY&lt; at &gt;public.gmane.org https://www.ietf.org/mailman/listinfo/speermint </pre> Internet-Drafts-EgrivxUAwEY< at >public.gmane.org 2010-11-09T02:15:27 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.ietf.rai.speermint