Re: [MMUSIC] WG Poll on the middleboxes draft (draft-ietf-mmusic-media-path-middleboxes)

Gonzalo Salgueiro <gsalguei@cisco.com> Thu, 28 June 2012 04:30 UTC

Return-Path: <gsalguei@cisco.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7498011E81D2 for <mmusic@ietfa.amsl.com>; Wed, 27 Jun 2012 21:30:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OOm9LjDpeZFZ for <mmusic@ietfa.amsl.com>; Wed, 27 Jun 2012 21:30:42 -0700 (PDT)
Received: from av-tac-rtp.cisco.com (av-tac-rtp.cisco.com [64.102.19.209]) by ietfa.amsl.com (Postfix) with ESMTP id 78F6011E81CA for <mmusic@ietf.org>; Wed, 27 Jun 2012 21:30:42 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from chook.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id q5S4UfhP005796 for <mmusic@ietf.org>; Thu, 28 Jun 2012 00:30:41 -0400 (EDT)
Received: from rtp-gsalguei-8719.cisco.com (rtp-gsalguei-8719.cisco.com [10.116.61.58]) by chook.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id q5S4UZjf014230; Thu, 28 Jun 2012 00:30:35 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset="us-ascii"
From: Gonzalo Salgueiro <gsalguei@cisco.com>
In-Reply-To: <E721D8C6A2E1544DB2DEBC313AF54DE20128EDC8@xmb-rcd-x02.cisco.com>
Date: Thu, 28 Jun 2012 00:30:35 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <49F21D33-F41E-4FBA-91ED-22C0711959A8@cisco.com>
References: <4FD27EAB.1090102@cisco.com> <4FD28645.5000702@cisco.com> <E721D8C6A2E1544DB2DEBC313AF54DE20128EDC8@xmb-rcd-x02.cisco.com>
To: Muthu Arul Mozhi Perumal <mperumal@cisco.com>
X-Mailer: Apple Mail (2.1278)
Cc: "Flemming Andreasen (fandreas)" <fandreas@cisco.com>, mmusic <mmusic@ietf.org>, draft-ietf-mmusic-media-path-middleboxes@tools.ietf.org
Subject: Re: [MMUSIC] WG Poll on the middleboxes draft (draft-ietf-mmusic-media-path-middleboxes)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jun 2012 04:30:43 -0000

+1

Gonzalo

On Jun 25, 2012, at 6:39 AM, Muthu Arul Mozhi Perumal (mperumal) wrote:

> +1
>  
> Considering that the draft has preliminary recommendations, I think it should be a BCP if we agree on those recommendations.
>  
> Muthu
>  
> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf Of Flemming Andreasen (fandreas)
> Sent: Saturday, June 09, 2012 4:40 AM
> To: mmusic
> Cc: draft-ietf-mmusic-media-path-middleboxes@tools.ietf.org
> Subject: Re: [MMUSIC] WG Poll on the middleboxes draft (draft-ietf-mmusic-media-path-middleboxes)
>  
> Some comments (as an individual)
> 
> A lot of the SIP and SDP work started out with a somewhat "purist" Internet view of the world, where things such as middleboxes were not considered. As other standards and industry organizations became interested in using SIP and SDP, different architectures were defined and some of those arcitectures did include the notion of middleboxes (e.g. 3GPP IMS and CableLabs PacketCable). From an IETF point of view, there was, at least initially, not a great deal of knowledge about these architectures and what the middleboxes defined by them were doing. Conversely, there was (is) also a concern that such middleboxes may break end-to-end transparency and hence there was a desire to try and alleviate that. 
> 
> To that effect, it was seen as useful to have a document that could
> a) Explain what/how middleboxes might be operating in these architectures
> b) Provide guidelines as to how such middleboxes could minimize (ideally avoid) impacting end-to-end transparency and/or how protocols could be used to try and alleviate any impact such middleboxes might have. 
> 
> The middleboxes draft is trying to address the above as it relates to the media path. The target audience is thus IETF participants that would like an overview of how these middleboxes may affect SIP/SDP-signaled media streams as well as what can be done to try and overcome that. Similarly, the document is targeted at people involved in these "other" architecture efforts, with a goal of making it clear how middleboxes may affect the operation of SIP/SDP-signaled media streams and hence provide some "design principles". This is not unlike some of the NAT work that was done in BEHAVE. 
> 
> It could be argued that these architectures have now been around for so long that producing the above document will not make any difference at this point. While I have some sympathy for this, I also think we have to recognize the importance of documenting what we know and to make that readily available for new people that will be working in this space. 
> 
> In other words, I still believe there is value in pursuing this document. As to whether it should be a BCP or Informational, I don't have any strong opinions. 
> 
> Thanks 
> 
> -- Flemming (as an individual)
> 
> 
> 
> 
> On 6/8/12 6:37 PM, Flemming Andreasen wrote:
> Hi 
> 
> As part of the MMUSIC charter we have the following milestone
> 
> Sep 2012
> Submit Considerations for using SDP offer/answer with middleboxes for BCP
> 
> and we have the middleboxes draft
> 
>     http://www.ietf.org/id/draft-ietf-mmusic-media-path-middleboxes-04.txt
> 
> to address that milestone. 
> 
> As discussed at IETF 83 (Paris), Hadriel Kaplan raised some concerns with the goal of the document and the potential target as further explained in the following e-mail: 
> 
>     http://www.ietf.org/mail-archive/web/mmusic/current/msg09278.html
> 
> A set of (initial) technical comments were also provided by Hadriel in the following e-mail:
> 
>     http://www.ietf.org/mail-archive/web/mmusic/current/msg08640.html
> 
> For now, the chairs would like to focus on the first set of questions above, i.e. what is the goal and potential target audience for the document and is there still value in pursuing it ?
> 
> 
> The chairs would like to poll the group for opinions and interest in this. Specific areas to consider:
> 
> 1) What is the target audience for the document ?
> 
> 2) Do people believe that the target audience will read and/or care about this document at this point ?
> 
> 3) Should the document be a BCP or Informational ?
> 
> 
> Thanks 
> 
> -- Miguel & Flemming (as chairs)
> 
> 
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic