Re: [MMUSIC] BUNDLE: Allowed to change local bundle port in SDP Answer?
"Hutton, Andrew" <email@example.com> Wed, 29 May 2013 10:05 UTC
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50B9621F9360 for <firstname.lastname@example.org>; Wed, 29 May 2013 03:05:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([184.108.40.206]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l2fW3r46FRFL for <email@example.com>; Wed, 29 May 2013 03:05:42 -0700 (PDT)
Received: from senmx12-mx.siemens-enterprise.com (senmx12-mx.siemens-enterprise.com [220.127.116.11]) by ietfa.amsl.com (Postfix) with ESMTP id 98A4F21F937A for <firstname.lastname@example.org>; Wed, 29 May 2013 03:05:40 -0700 (PDT)
Received: from MCHP01HTC.global-ad.net (unknown [172.29.42.234]) by senmx12-mx.siemens-enterprise.com (Server) with ESMTP id 3EB6323F0464; Wed, 29 May 2013 12:05:39 +0200 (CEST)
Received: from MCHP04MSX.global-ad.net ([169.254.1.174]) by MCHP01HTC.global-ad.net ([172.29.42.234]) with mapi id 14.03.0123.003; Wed, 29 May 2013 12:05:39 +0200
From: "Hutton, Andrew" <email@example.com>
To: Christer Holmberg <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>
Thread-Topic: BUNDLE: Allowed to change local bundle port in SDP Answer?
Date: Wed, 29 May 2013 10:05:38 +0000
Content-Type: multipart/alternative; boundary="_000_9F33F40F6F2CD847824537F3C4E37DDF115B4EAEMCHP04MSXglobal_"
Subject: Re: [MMUSIC] BUNDLE: Allowed to change local bundle port in SDP Answer?
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:email@example.com?subject=unsubscribe>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:firstname.lastname@example.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 10:05:47 -0000
Cannot see why the answerer should be prevented from changing the port and even the connection address and candidates etc. in any new answer any such restriction would seem to be a major diversion from existing offer/answer procedures and I cannot see why we would want to consider it. We need to maintain the existing offer/answer procedures as much as possible. Andy From: email@example.com [mailto:firstname.lastname@example.org] On Behalf Of Christer Holmberg Sent: 29 May 2013 10:36 To: email@example.com Subject: [MMUSIC] BUNDLE: Allowed to change local bundle port in SDP Answer? Hi, When the answerer receives the first bundle offer, it will assign a local bundle port. Nothing strange there. Paul raised a question whether, when an updated offer is received, the answerer is allowed to change the local bundle port in the associated answer. Personally, I can't think of a reason why it should not be allowed - no matter whether the offer contains different bundle ports or not - it would be according to normal O/A procedures. If NOT allowed, if the answerer wants to change its local bundle port, it would have to send a new offer by itself (the details of such offer is discussed in another tread). Comments? Regards, Christer
- [MMUSIC] BUNDLE: Allowed to change local bundle p… Christer Holmberg
- Re: [MMUSIC] BUNDLE: Allowed to change local bund… Hutton, Andrew
- Re: [MMUSIC] BUNDLE: Allowed to change local bund… Christer Holmberg