Re: [P2PSIP] Review of DRR and RPR documents

"Roni Even" <ron.even.tlv@gmail.com> Wed, 13 March 2013 12:46 UTC

Return-Path: <ron.even.tlv@gmail.com>
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 D56A621F848B for <p2psip@ietfa.amsl.com>; Wed, 13 Mar 2013 05:46:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level:
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_31=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pmivcyzPhtKg for <p2psip@ietfa.amsl.com>; Wed, 13 Mar 2013 05:46:08 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id B1CB421F8477 for <p2psip@ietf.org>; Wed, 13 Mar 2013 05:46:08 -0700 (PDT)
Received: by mail-pb0-f44.google.com with SMTP id wz12so988094pbc.17 for <p2psip@ietf.org>; Wed, 13 Mar 2013 05:46:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-type:content-transfer-encoding :x-mailer:thread-index:content-language; bh=XDPmvJ6kofFigF/gby95TmePKh2ftlomHHQm5ZR4glU=; b=RGEwxIQ23YofKnMNjx08s+oBe0ZEqGlR7ZZGPDl/AyuF5ylEbLXcN08iT3IYI6Ldcd D26kzLDPgolts3eHfuhbaN6Tirn4LfDraInYRVhHmvcZ9TgWoL8cT7aay4UJ33SLsxPz IS+P5VTYf3p3XVf0SEap49JE8o33D/6mh4Gw/iYqhRj/5GOE+QwhRmjEoeZ/M8G/T/Sd NvWcHGuzy5pkB8U7vYDig0/Qv4A7Y/Ty8hgiUF2Xo8C8S6xT7TOEiYwbQiLLhzL8wBAW P+5R/OonDqHp46w8levxkl014G+nAbw2jz4r7OUnBDd5gNo60oS0u1jmHWS4w0yGW0cr eGog==
X-Received: by 10.68.213.104 with SMTP id nr8mr46068559pbc.200.1363178768051; Wed, 13 Mar 2013 05:46:08 -0700 (PDT)
Received: from RoniE ([2001:df8:0:64:4571:a157:5673:fb54]) by mx.google.com with ESMTPS id xz5sm97220pbb.25.2013.03.13.05.46.04 (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 13 Mar 2013 05:46:06 -0700 (PDT)
From: Roni Even <ron.even.tlv@gmail.com>
To: cjbc@it.uc3m.es, p2psip@ietf.org
References: <1358855465.4174.24.camel@acorde.it.uc3m.es>
In-Reply-To: <1358855465.4174.24.camel@acorde.it.uc3m.es>
Date: Wed, 13 Mar 2013 14:45:42 +0200
Message-ID: <008f01ce1fe8$aedf0c10$0c9d2430$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJJctlInCoLwT4KekX9uZ6cgNVklpes6wTw
Content-Language: en-us
Cc: draft-ietf-p2psip-drr@tools.ietf.org, draft-ietf-p2psip-rpr@tools.ietf.org
Subject: Re: [P2PSIP] Review of DRR and RPR documents
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: Wed, 13 Mar 2013 12:46:09 -0000

Hi Carlos,
You made a comment about registering the forward option flag and forward option type with IANA.
These parameters are defined in the p2psip base draft and flags values are assigned over there. So if there is a need for IANA registry this should be specified in the base draft which is the main document
Roni

-----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