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

Hannes Tschofenig <hannes.tschofenig@gmx.net> Thu, 28 June 2012 10:09 UTC

Return-Path: <hannes.tschofenig@gmx.net>
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 7D02621F8595 for <mmusic@ietfa.amsl.com>; Thu, 28 Jun 2012 03:09:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 xsaXE-HRdsaj for <mmusic@ietfa.amsl.com>; Thu, 28 Jun 2012 03:09:42 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 7C12411E81C5 for <mmusic@ietf.org>; Thu, 28 Jun 2012 00:19:51 -0700 (PDT)
Received: (qmail invoked by alias); 28 Jun 2012 07:19:49 -0000
Received: from unknown (EHLO [10.255.135.50]) [194.251.119.201] by mail.gmx.net (mp034) with SMTP; 28 Jun 2012 09:19:49 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1++QvV2OIa+tpZVAGZL58kiiv9f3YdQbfJqT1nHw/ 9ClvFkG+BGo5lL
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
In-Reply-To: <4FD28645.5000702@cisco.com>
Date: Thu, 28 Jun 2012 10:19:46 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <DCD530E7-4026-4AD2-85D5-650F732D4D3A@gmx.net>
References: <4FD27EAB.1090102@cisco.com> <4FD28645.5000702@cisco.com>
To: Flemming Andreasen <fandreas@cisco.com>
X-Mailer: Apple Mail (2.1084)
X-Y-GMX-Trusted: 0
Cc: 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 10:09:43 -0000

Hi Flemming, 

I take a pragmatic view. The document has been worked on in the group for a while, a WGLC had been held, the received last call comments had been incorporated in the meanwhile. 

From there on there are only two routes (IMHO):
a) publish the document through the working group, 
b) the authors submit it to the RFC editor as an independent submission

At this point in time the outcome is not so much different anymore (since the working group had already provided their input). 

The text about the impact of middleboxes on signaling protocols is something worth capturing and the offered guidance seems to be OK. I still think that this writeup will be a useful reference for the work on middleboxes with relationship to security protocols. 

Ciao
Hannes


On Jun 9, 2012, at 2:09 AM, Flemming Andreasen wrote:

> 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