Re: [rtcweb] Agenda requests for Atlanta meeting

"Cullen Jennings (fluffy)" <> Tue, 09 October 2012 14:16 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1DC1F11E8097 for <>; Tue, 9 Oct 2012 07:16:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -110.532
X-Spam-Status: No, score=-110.532 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Gv5PpbZQoWBX for <>; Tue, 9 Oct 2012 07:16:55 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id BA3D011E810C for <>; Tue, 9 Oct 2012 07:16:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=2064; q=dns/txt; s=iport; t=1349792215; x=1351001815; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=c/Y1vw2NnkEUWBwAlCO354fFebett7WZ8yiYY+LdG4I=; b=Lwsds2iY6tNoFZgYo7M+aekCXrKhYUW/YAd3HJyvZzw615KbRZEH2Gl+ O7pidftaAUb1cJTyPsBJP3PyztNqsGX7Ktr7invqnfa4pAet/ayAE64Ar /pCTcNusl8wI0rrtSOWL9txuI5L7NuHu8CeOCd8ZVe8drnUKS7tz467gK g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="4.80,560,1344211200"; d="scan'208";a="129724056"
Received: from ([]) by with ESMTP; 09 Oct 2012 14:16:50 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id q99EGo9I029478 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 9 Oct 2012 14:16:50 GMT
Received: from ([]) by ([]) with mapi id 14.02.0318.001; Tue, 9 Oct 2012 09:16:50 -0500
From: "Cullen Jennings (fluffy)" <>
To: Christer Holmberg <>
Thread-Topic: [rtcweb] Agenda requests for Atlanta meeting
Thread-Index: AQHNpaenkG2ADNG+3EO5+NGGgdEEepewfwQwgADbJIA=
Date: Tue, 09 Oct 2012 14:16:49 +0000
Message-ID: <>
References: <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
x-tm-as-product-ver: SMEX-
x-tm-as-result: No--32.966700-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-ID: <>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "" <>
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: Tue, 09 Oct 2012 14:16:56 -0000

On Oct 8, 2012, at 23:41 , Christer Holmberg <>

> Hi,
>>> I would like to discuss the different alternatives in order to support forking, e.g. whether we use cloning, whether we simply set additional local descriptor, and whether we can get rid of PRANSWER.
>> Seriously? we have discussed this so many times and always come to the same conclusion. I have not seen anything on the list that suggests why we need to remove this or how mapping to SIP 180 with sequential forking is going to work without it.
> You CAN do serial forking also with cloning (or, as suggested by Martin, simply setting additional local descriptors).
> I am not blindly suggesting to remove PRANSWER (I have been one of the defenders for having it). It's part of the more general "JSEP Offer/Answer Usage" issue, which we DO need to make sure we get right.

agree - sounds like we are on same page 

>> It also has other important uses. There are a bunch of changes that are needed to the JSEP draft to remove some of the inconsistencies in this and clarify some parts but I'd rather wait till we had that updated before we got into a whole discussion about 
>> exploding it yet again. 
> 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.

>> Why don't we have a phone call to try and outline what the problems you are trying to solve that the current solution does not work for then figure out how much we want to explode this. 
> Sure. I'd attend such call.
> Regards,
> Christer