Re: [P2PSIP] Review of DRR and RPR documents

Carlos Jesús Bernardos Cano <cjbc@it.uc3m.es> Mon, 18 February 2013 09:16 UTC

Return-Path: <cjbc@it.uc3m.es>
X-Original-To: p2psip@ietfa.amsl.com
Delivered-To: p2psip@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03E8021F87AD for <p2psip@ietfa.amsl.com>; Mon, 18 Feb 2013 01:16:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.224
X-Spam-Level:
X-Spam-Status: No, score=-6.224 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uvWg5nChA3QA for <p2psip@ietfa.amsl.com>; Mon, 18 Feb 2013 01:16:49 -0800 (PST)
Received: from smtp03.uc3m.es (smtp03.uc3m.es [163.117.176.133]) by ietfa.amsl.com (Postfix) with ESMTP id 1B12321F8519 for <p2psip@ietf.org>; Mon, 18 Feb 2013 01:16:46 -0800 (PST)
Received: from smtp03.uc3m.es (localhost [127.0.0.1]) by localhost.uc3m.es (Postfix) with ESMTP id 8E570FA98DC; Mon, 18 Feb 2013 10:16:45 +0100 (CET)
X-uc3m-safe: yes
X-uc3m-safe: yes
Received: from [163.117.139.72] (acorde.it.uc3m.es [163.117.139.72]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: cjbc@smtp03.uc3m.es) by smtp03.uc3m.es (Postfix) with ESMTPSA id 61B68FA98AF; Mon, 18 Feb 2013 10:16:45 +0100 (CET)
Message-ID: <1361179005.4189.10.camel@acorde.it.uc3m.es>
From: Carlos Jesús Bernardos Cano <cjbc@it.uc3m.es>
To: Zongning <zongning@huawei.com>
Date: Mon, 18 Feb 2013 10:16:45 +0100
In-Reply-To: <B0D29E0424F2DE47A0B36779EC6667792561FD07@nkgeml501-mbs.china.huawei.com>
References: <1358855465.4174.24.camel@acorde.it.uc3m.es> <008a01cdf8a1$c767bca0$563735e0$@gmail.com> <1358873012.4174.54.camel@acorde.it.uc3m.es> <B0D29E0424F2DE47A0B36779EC6667792561FD07@nkgeml501-mbs.china.huawei.com>
Organization: Universidad Carlos III de Madrid
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.4.4-1
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-TM-AS-Product-Ver: IMSS-7.1.0.1224-7.0.0.1014-19644.006
X-TM-AS-Result: No--39.821-7.0-31-1
X-imss-scan-details: No--39.821-7.0-31-1
Cc: "p2psip@ietf.org" <p2psip@ietf.org>
Subject: Re: [P2PSIP] Review of DRR and RPR documents
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: cjbc@it.uc3m.es
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/p2psip>, <mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/p2psip>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2psip>, <mailto:p2psip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Feb 2013 09:16:51 -0000

Dear Ning,

OK, thanks for the updates. Let me take a look and post my revision.

Carlos

On Sun, 2013-02-17 at 01:30 +0000, Zongning wrote:
> Hi, Carlos and all.
> 
> We have submitted new revision of DRR draft and RPR draft. The main change is that we did some wording in RPR draft to avoid referring to DRR as normative reference.
> As said, we still have some duplication in the two drafts because we want to keep them independent to each other.
> Further comments and suggestions are welcome.
> Thanks.
> 
> -Ning
> 
> > -----Original Message-----
> > From: p2psip-bounces@ietf.org [mailto:p2psip-bounces@ietf.org] On Behalf Of
> > Carlos Jesús Bernardos Cano
> > Sent: Wednesday, January 23, 2013 12:44 AM
> > To: Roni Even
> > Cc: draft-ietf-p2psip-rpr@tools.ietf.org; draft-ietf-p2psip-drr@tools.ietf.org;
> > p2psip@ietf.org
> > Subject: Re: [P2PSIP] Review of DRR and RPR documents
> > 
> > Hi Roni,
> > 
> > Thanks for the prompt reaction.
> > 
> > If the split/merging discussion has already taken place, I don't want to
> > bring it again, but I just found a bit artificial the separation in two
> > documents (and now I see why). I see the point of implementation
> > compliance with one RFC and not the other, but current text in RPR
> > refers to protocol extensions defined in DRR, so we are not there
> > either.
> > 
> > As I see it (personal opinion) if we want to keep two separate
> > documents, we still need some additional work on the wording of them,
> > and we might end up duplicating some content. The merging approach would
> > make the text cleaner, but would have the problem you pointed out.
> > 
> > Thanks,
> > 
> > Carlos
> > 
> > On Tue, 2013-01-22 at 15:09 +0200, Roni Even wrote:
> > > Hi Carlos,
> > > Thanks for the review, we will look at the comments as for merging the
> > documents. Originally it was one document and it was a WG decision to split it
> > to allow implementation to be compliant with an RFC if they want only to
> > support DRR or RPR
> > > Roni Even
> > >
> > > -----Original Message-----
> > > From: p2psip-bounces@ietf.org [mailto:p2psip-bounces@ietf.org] On Behalf
> > Of Carlos Jes?s Bernardos Cano
> > > Sent: 22 January, 2013 1:51 PM
> > > To: p2psip@ietf.org
> > > Cc: draft-ietf-p2psip-drr@tools.ietf.org; draft-ietf-p2psip-rpr@tools.ietf.org
> > > Subject: [P2PSIP] Review of DRR and RPR documents
> > >
> > > Hi,
> > >
> > > As agreed during the last meeting, I've performed a review of
> > draft-ietf-p2psip-drr and draft-ietf-p2psip-rpr documents, prior to shipping
> > them to the IESG for publication. My reviews are attached to this e-mail (I
> > added comments to the PDF version of each draft, hope this is fine).
> > >
> > > I'd like authors to go through the comments before sending the documents to
> > the IESG. There might be some issues that need to be brought to the WG for
> > discussion.
> > >
> > > I'd also like to ask the WG for opinion on one particular aspect. I'm wondering
> > if it would be better to merge both documents into a single one. Currently, both
> > documents make quite a lot of cross-references, but still there is duplicate text
> > in both of them, so I'd be more in favor of merging (personal opinion). Please,
> > comment on this on the mailing list.
> > >
> > > Thanks,
> > >
> > > Carlos
> > >
> > 
> > 
> > _______________________________________________
> > P2PSIP mailing list
> > P2PSIP@ietf.org
> > https://www.ietf.org/mailman/listinfo/p2psip