Re: [rtcweb] Agenda requests for Atlanta meeting

Christer Holmberg <> Thu, 11 October 2012 15:45 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 35B0C21F874C for <>; Thu, 11 Oct 2012 08:45:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.127
X-Spam-Status: No, score=-6.127 tagged_above=-999 required=5 tests=[AWL=0.122, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id FyF73OX0uG2v for <>; Thu, 11 Oct 2012 08:45:13 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id D064121F86C9 for <>; Thu, 11 Oct 2012 08:45:12 -0700 (PDT)
X-AuditID: c1b4fb25-b7f956d0000011c3-ab-5076e9878f04
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id 5B.1D.04547.789E6705; Thu, 11 Oct 2012 17:45:11 +0200 (CEST)
Received: from ([]) by ([]) with mapi; Thu, 11 Oct 2012 17:45:11 +0200
From: Christer Holmberg <>
To: Harald Alvestrand <>, "" <>
Date: Thu, 11 Oct 2012 17:44:18 +0200
Thread-Topic: [rtcweb] Agenda requests for Atlanta meeting
Thread-Index: Ac2nxFkYlxHAcOGpQSSR4wekASssMwAAhcYHAAA1pVI=
Message-ID: <>
References: <> <> <> <> <> <>, <>, <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrLLMWRmVeSWpSXmKPExsUyM+JvrW77y7IAg1/3jSyO9XWxWaz9187u wORxZcIVVo8lS34yBTBFcdmkpOZklqUW6dslcGW0NU5nK9jJW7H74XKWBsZPXF2MnBwSAiYS 39e1s0HYYhIX7q0Hsrk4hAROMUrc7NzOAuHMZZR4NvMraxcjBwebgIVE9z9tkAYRgWCJ3ufv GUFsFgFViX+PFrGC2MIClhKLNu9ng6ixklhz6zozjN30/TyYzSsQLvF/+2pWiPkNLBJbXt4B a+AUiJA49vEB2FBGoIu+n1rDBGIzC4hL3HoynwniUgGJJXsgBkkIiEq8fPyPFaJeVOJO+3pG iHodiQW7P7FB2NoSyxa+hlosKHFy5hOWCYyis5CMnYWkZRaSlllIWhYwsqxiFM5NzMxJLzfS Sy3KTC4uzs/TK07dxAiMkoNbfqvuYLxzTuQQozQHi5I4r/XWPf5CAumJJanZqakFqUXxRaU5 qcWHGJk4OKUaGGvbFk5UXHnAmN9pd/mab+2Bs26HThTc7DbJ/4mSU61Z3kZh8Rc1398+/ZT6 9dCGjw7Tlr51WxShZHn+F/dX6aOzA5QtFBwLfXm+SB5/6/k6/phv4tqL+oeiWScyxJbw1uoF TS5mLZ1ptYYhXvlSq2hW4vyk5Qeq87xC/1V7zPeZmNi05+nRf0osxRmJhlrMRcWJAPFYdqBg AgAA
Subject: Re: [rtcweb] Agenda requests for Atlanta meeting
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 11 Oct 2012 15:45:14 -0000

That answer CANNOT be "updated" in another reliable 18x response, or in the 200 response - on the same SIP early dialog, that is.

From: [] On Behalf Of Christer Holmberg []
Sent: Thursday, October 11, 2012 6:38 PM
To: Harald Alvestrand;
Subject: Re: [rtcweb] Agenda requests for Atlanta meeting


>>> I have no problem with that. But, again, we do need to get the JSEP O/A sorted out. My suggesting is still that the base should be RFC 3264, and if we need to "relax" things we should very carefully look at those cases.
>> I have not seen any reason to relax 3264 yet but if something comes up, agree we should carefully look at the cases. I think we can just do straight up 3264. Arguments that SIP early media in a 180 is not compliant with 3264 are just wrong.
> This seems to be true as long as I consider the offer/180 exchange a
> separate SDP exchange from the offer/answer exchange, and abandon the
> concept that the final answer "updates" the 180 answer.
> Is that what you are saying, or did I squint the wrong way?

If you receive the SDP answer in a reliable 180 response, that IS an offer/answer exchange :)

That answer CANNOT be "updated" in another reliable 18x response, or in the 200 response.

(You can receive a "copy" of the previously received SDP answer in the 18x/200 responses, but it will not update the previously received SDP answer)


rtcweb mailing list