Re: [bfcpbis] Review of draft-ram-bfcpbis-sdp-ws-uri-01.txt

"Suhas Nandakumar (snandaku)" <snandaku@cisco.com> Mon, 15 February 2016 19:53 UTC

Return-Path: <snandaku@cisco.com>
X-Original-To: bfcpbis@ietfa.amsl.com
Delivered-To: bfcpbis@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A831A1ACD29 for <bfcpbis@ietfa.amsl.com>; Mon, 15 Feb 2016 11:53:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.506
X-Spam-Level:
X-Spam-Status: No, score=-14.506 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.006, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xKvxltOfeiNr for <bfcpbis@ietfa.amsl.com>; Mon, 15 Feb 2016 11:53:19 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7B5F1ACD0E for <bfcpbis@ietf.org>; Mon, 15 Feb 2016 11:53:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=20413; q=dns/txt; s=iport; t=1455565998; x=1456775598; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=0uD3CGRe33oNGvhSdbDadlpu6wEk5k9tUjDE2SJD54M=; b=iEfNBFrB86bVtkZxBfmZchtCzHyYbXbl0SbRai9m5pPy4q/x358i9uY1 kfjppjo1wsrNK9xFWDg9nfVXjU8Caxiq8oOutmu6bPmOpJqqXUVqQKd8s LIsSYu1H3jz93tu46axcycKFLSJ0eSx03tgng0iLQvMBZW8uYlO98LzZR E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D9BADkK8JW/4sNJK1egm5MUm0GhTdGp?= =?us-ascii?q?TkBBAGOXAENgWcXAQmEFYENSgKBNzgUAQEBAQEBAX8LhEEBAQEEAQEBaxsCAQg?= =?us-ascii?q?RAwEBAQoeBw8SBgsUAwEFCAIEE4gFAxIOsiINhFYBAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQERBIYRhDWCN4IbDQmEBAWLLYF6OIUPhAsBhU6GE4FzgVyEQ4hVhn6HPwE?= =?us-ascii?q?eAQFCgUyCF2oBh1J8AQEB?=
X-IronPort-AV: E=Sophos; i="5.22,452,1449532800"; d="scan'208,217"; a="71610367"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 15 Feb 2016 19:53:17 +0000
Received: from XCH-RCD-010.cisco.com (xch-rcd-010.cisco.com [173.37.102.20]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id u1FJrHfv016538 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <bfcpbis@ietf.org>; Mon, 15 Feb 2016 19:53:17 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-RCD-010.cisco.com (173.37.102.20) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Mon, 15 Feb 2016 13:53:16 -0600
Received: from xch-aln-008.cisco.com ([173.36.7.18]) by XCH-ALN-008.cisco.com ([173.36.7.18]) with mapi id 15.00.1104.009; Mon, 15 Feb 2016 13:53:16 -0600
From: "Suhas Nandakumar (snandaku)" <snandaku@cisco.com>
To: "bfcpbis@ietf.org" <bfcpbis@ietf.org>
Thread-Topic: [bfcpbis] Review of draft-ram-bfcpbis-sdp-ws-uri-01.txt
Thread-Index: AQHRXn09awGPcMtKSOuEMOqqlqy9z58kBpWAgAia4QuAAK7PgIAAQwLGgAAEpdU=
Date: Mon, 15 Feb 2016 19:53:16 +0000
Message-ID: <1455565996728.53190@cisco.com>
References: <D2D7EFD6.5024B%rmohanr@cisco.com> <D2DF81D1.663E5%eckelcu@cisco.com> <7594FB04B1934943A5C02806D1A2204B37DEF39D@ESESSMB209.ericsson.se>, <CAGTXFp8x1Rkkuvrp68EfmgPOW+yvxg4UATkfZbaHU9xxUCWa7Q@mail.gmail.com>, <5BF523F4-844D-4E04-B2B8-33D7EF1360C7@cisco.com>
In-Reply-To: <5BF523F4-844D-4E04-B2B8-33D7EF1360C7@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.35.132.38]
Content-Type: multipart/alternative; boundary="_000_145556599672853190ciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/bfcpbis/MX5aRz7tDrfuw3hnEy5X6aYjEt4>
X-Mailman-Approved-At: Mon, 15 Feb 2016 22:37:41 -0800
Subject: Re: [bfcpbis] Review of draft-ram-bfcpbis-sdp-ws-uri-01.txt
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: BFCPBIS working group discussion list <bfcpbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bfcpbis/>
List-Post: <mailto:bfcpbis@ietf.org>
List-Help: <mailto:bfcpbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Feb 2016 19:53:22 -0000

?I support adopting this draft


Thanks

Suhas


From: Victor Pascual Avila <victor.pascual.avila@gmail.com<mailto:victor.pascual.avila@gmail.com>>
Date: February 15, 2016 at 4:36:23 AM EST
To: Christer Holmberg <christer.holmberg@ericsson.com<mailto:christer.holmberg@ericsson.com>>
Cc: "Ram Mohan R \(rmohanr\)" <rmohanr@cisco.com<mailto:rmohanr@cisco.com>>, "bfcpbis@ietf.org<mailto:bfcpbis@ietf.org>" <bfcpbis@ietf.org<mailto:bfcpbis@ietf.org>>, "Charles Eckel \(eckelcu\)" <eckelcu@cisco.com<mailto:eckelcu@cisco.com>>
Subject: Re: [bfcpbis] Review of draft-ram-bfcpbis-sdp-ws-uri-01.txt

I support adoption

On Mon, Feb 15, 2016 at 6:10 AM, Christer Holmberg
<christer.holmberg@ericsson.com<mailto:christer.holmberg@ericsson.com>> wrote:
Hi,

I think the draft is ready for adoption.

Regards.

Christer

Sent from my Windows Phone
________________________________
From: Charles Eckel (eckelcu)
Sent: ?09/?02/?2016 21:45
To: Ram Mohan R (rmohanr); Christer Holmberg; bfcpbis@ietf.org<mailto:bfcpbis@ietf.org>
Subject: Re: [bfcpbis] Review of draft-ram-bfcpbis-sdp-ws-uri-01.txt

Ram and other draft authors,

Thanks for updating and posting the revised draft.
I would like to poll the working group to see if people think this draft
is now ready to be adopted as a bfcpbis working group draft.

Thanks,
Charles



On 2/3/16, 4:20 AM, "bfcpbis on behalf of Ram Mohan R (rmohanr)"
<bfcpbis-bounces@ietf.org<mailto:bfcpbis-bounces@ietf.org> on behalf of rmohanr@cisco.com<mailto:rmohanr@cisco.com>> wrote:

Hi Christer,

Thanks for the feedback. All the below comments has been take care and a
new revision is published. Please look at the diffs here:
https://www.ietf.org/rfcdiff?url2=draft-ram-bfcpbis-sdp-ws-uri-02

Link to draft  -
https://tools.ietf.org/html/draft-ram-bfcpbis-sdp-ws-uri-02

Regards,
Ram

From:  bfcpbis <bfcpbis-bounces@ietf.org<mailto:bfcpbis-bounces@ietf.org>> on behalf of Christer Holmberg
<christer.holmberg@ericsson.com<mailto:christer.holmberg@ericsson.com>>
Date:  Wednesday, 21 October 2015 at 12:23 AM
To:  "bfcpbis@ietf.org<mailto:bfcpbis@ietf.org>" <bfcpbis@ietf.org<mailto:bfcpbis@ietf.org>>
Subject:  [bfcpbis] Review of draft-ram-bfcpbis-sdp-ws-uri-01.txt


Hi,

I have reviewed draft-ram-bfcpbis-sdp-ws-uri-01.txt.

I think the draft needs some editorial work, and there is also technical
procedures (related to SDP Offer/Answer) missing.

Q3_1:    I suggest to remove ³Media² from the section titles. Instead the
text should indicate that the attributes are media-level attributes. Also,
in the text you should say something like ³This section defines a new SDP
media-level attribute,
<attribute-name>,S.² instead of the current text which says ³The new
attribute MUST be a media levelS².

Q3_2:    Sections 3.1 and 3.2 start with text saying:

³Applications that use SDP for negotiation and also use WebSocket as a
            transport protocol MAY indicate the connection URI for the
WebSocketS²

I don¹t think this text belongs in the attribute definition sections.
Instead I suggest to add a section ³3.1 General² where you describe the
need for the attributes.


Also, instead of saying ³Applications that use SDP for negotiationS² I
would say ³Applications that use the SDP Offer/Answer mechanism [RFC3264]
for negotiating mediaS².

Q3_3:    There is no port information in c= lines.

Q3_4:    There should be an OESDP Offer/Answer¹ section, describing the
usage of the attributes. The structure should be:

 X.  SDP Offer/Answer Procedures
   X.1.  General
   X.2.  Generating the Initial SDP Offer
   X.3.  Generating the SDP Answer
   X.4.  Offerer Processing of the SDP Answer
   X.5.  Modifying the Session

For example, in section X.5 you need to describe what it means to NOT
include the attributes in a subsequent offer. Does it mean that the
websocket connection shall be terminated? Etc.

Regards,

Christer

_______________________________________________
bfcpbis mailing list
bfcpbis@ietf.org<mailto:bfcpbis@ietf.org>
https://www.ietf.org/mailman/listinfo/bfcpbis


_______________________________________________
bfcpbis mailing list
bfcpbis@ietf.org<mailto:bfcpbis@ietf.org>
https://www.ietf.org/mailman/listinfo/bfcpbis




--
Victor Pascual Ávila

_______________________________________________
bfcpbis mailing list
bfcpbis@ietf.org<mailto:bfcpbis@ietf.org>
https://www.ietf.org/mailman/listinfo/bfcpbis