
From david.black@emc.com  Mon Dec  3 15:13:12 2012
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C011521F8968; Mon,  3 Dec 2012 15:13:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 6k+FL7sRA7Es; Mon,  3 Dec 2012 15:13:11 -0800 (PST)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id CE74E21F86F3; Mon,  3 Dec 2012 15:13:10 -0800 (PST)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id qB3ND5V0015947 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 3 Dec 2012 18:13:06 -0500
Received: from mailhub.lss.emc.com (mailhubhoprd02.lss.emc.com [10.254.221.253]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Mon, 3 Dec 2012 18:12:55 -0500
Received: from mxhub29.corp.emc.com (mxhub29.corp.emc.com [128.222.70.169]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id qB3NCsh8000640; Mon, 3 Dec 2012 18:12:54 -0500
Received: from mx15a.corp.emc.com ([169.254.1.253]) by mxhub29.corp.emc.com ([128.222.70.169]) with mapi; Mon, 3 Dec 2012 18:12:54 -0500
From: "Black, David" <david.black@emc.com>
To: "yiu_lee@cable.comcast.com" <yiu_lee@cable.comcast.com>, "roberta.maglione@telecomitalia.it" <roberta.maglione@telecomitalia.it>, "carlw@mcsr-labs.org" <carlw@mcsr-labs.org>, "christian.jacquenet@orange.com" <christian.jacquenet@orange.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Date: Mon, 3 Dec 2012 18:12:52 -0500
Thread-Topic: Gen-ART review of draft-ietf-softwire-dslite-deployment-07
Thread-Index: Ac2rKkPgDErjXyHISiSTlQ/jGKFZIgmf5XbA
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712864B595B@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE7120DFAEF29@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7120DFAEF29@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "softwires@ietf.org" <softwires@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: [Gen-art] Gen-ART review of draft-ietf-softwire-dslite-deployment-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Dec 2012 23:13:12 -0000

Authors,

The -07 version of this draft has resolved most of the concerns raised by
the  Gen-ART review of the -06 version of this draft, with one significant
exception:

> [5] Section 2.8 discusses IPv4 accounting at the AFTR, but notes that
> "the AFTR does not have detailed customer identity information."  Does
> that create a theft of service possibility?  If so, that possibility
> should be mentioned as a security consideration.  Also, Section 2.8
> ought to be expanded with a sentence or two explaining why the AFTR
> does not have that identity information, and in particular to explain
> whether and why it is unreasonable in some or all cases to expect
> that customer identity information be provided to the AFTR as part
> of provisioning each customer's softwire.

This has been partially resolved - the explanation of why the AFTR may
not have that identity information has been added.  Here's the text from
the -07 draft.

   Alternatively, AFTR may perform accounting for IPv4 traffic.
   However, operators must be aware that this will introduce some
   challenges especially in DSL deployment.  In DSL deployment, the AAA
   transaction normally happens between the edge router (i.e., Broadband
   Network Gateway) and AAA server.  [RFC6333] does not require the AFTR
   to interact with the AAA server or edge router.  Thus, AFTR may not
   have the AAA parameters (e.g., Account Session ID) associated to
   users to generate IPv4 accounting record.  The accounting process at
   the AFTR is only necessary if the operator requires separating per
   user accounting records for IPv4 and IPv6 traffic.  If the per user
   IPv6 accounting records, collected by the edge router, are
   sufficient, and the additional complexity of enabling IPv4 accounting
   at the ATFR is not required.  It is important to notice that, since
   the IPv4 traffic is encapsulated in IPv6 packets, the data collected
   by the edge router for IPv6 traffic already contain the total amount
   of traffic (i.e.  IPv4 and IPv6).

This revised text removes my concern about a security risk, but=20
I think the result still provides more support than it should for
trying to do accounting without all the information needed to do it.

Please insert a sentence before "The accounting process at the AFTR is
only necessary if ..." to state that IPv4 traffic accounting at the AFTR
is not recommended when the necessary AAA parameters are not available.
The following sentence would suffice.

   IPv4 traffic accounting at the AFTR is not recommended when the
   AAA parameters necessary to generate complete IPv4 accounting
   records are not available.

Also, the response to this nit could be improved:

> Section 3.2.2 uses 192.0.0.2/32 as an example IP address for the
> B4.  That section should also cross-reference Section 5.7 on RFC 6333
> on IP address assignment to B4s, as other IP addresses may be used.

My original comment wasn't complete - here's a suggested text change
that should be clearer:

OLD
   Operators should assign the same IPv4 address
   (i.e., 192.0.0.2/32) to all AFTRs.  IANA allocates 192.0.0.0/29
   [RFC6333] Section 5.7 that can be used for this purpose.
NEW
   Operators should assign the same IPv4 address
   (e.g., 192.0.0.2/32 [RFC6333]) to all AFTRs.  IANA has allocated
   the 192.0.0.0/29 network prefix to provide IPv4 addresses for this
   purpose [RFC 6333].
END

Thanks,
--David

> -----Original Message-----
> From: Black, David
> Sent: Monday, October 15, 2012 7:10 PM
> To: yiu_lee@cable.comcast.com; roberta.maglione@telecomitalia.it; carlw@m=
csr-
> labs.org; christian.jacquenet@orange.com; mohamed.boucadair@orange.com; g=
en-
> art@ietf.org
> Cc: softwires@ietf.org; Black, David; ietf@ietf.org; Ralph Droms
> Subject: Gen-ART review of draft-ietf-softwire-dslite-deployment-06
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-softwire-dslite-deployment-06
> Reviewer: David L. Black
> Review Date: October 15, 2012
> IETF LC End Date: October 16, 2012
> IESG Telechat Date: October 25, 2012
>=20
> Summary:
>=20
> This draft is on the right track but has open issues, described in the re=
view.
>=20
> This is a generally well-written draft that expands considerably on the b=
rief
> deployment considerations for DS-Lite in Appendix A of RFC 6333.  The dra=
ft
> is clear and reasonably well-written, and a significant improvement on th=
at
> RFC 6333 Appendix, although an understanding of RFC 6333 is necessary to
> understand this draft, which seems completely reasonable.
>=20
> The B4 and AFTR acronyms are clever - kudos to whomever came up with thos=
e.
>=20
> I found five open issues, all of which are minor.
>=20
> Minor Issues:
>=20
> [1] Ironically, the first issue is that something should be said about
> the relationship of this draft to Appendix A of RFC 6333.  It probably
> suffices to say that this draft expands on the material in that Appendix,
> as I see no need to specify that this draft updates RFC 6333 solely to
> change non-normative material in an Appendix.
>=20
> [2] The MTU increase technique in Section 2.2 is a "may", which is
> consistent with Section 5.3 of RFC 6333.  OTOH, Section 2.2 of this
> draft should also discuss the AFTR resource exhaustion concern that
> described in Section 6.3 of RFC 6333, as that is a potential
> operational reason for an ISP to increase MTU size (e.g., if customer
> sourcing of large IPv4 packets is not sufficiently rare).
>=20
> [3] Section 2.7 refers to "the AFTR's internal interface".  There may be
> two internal interfaces, the physical IPv6 interface (outer header) and
> the tunnel's IPv4 interface (inner header).  The text should be clarified
> to indicate which interface is involved - it appears that the AFTR's
> physical IPv6 interface is intended in this section.
>=20
> [4] Section 2.7 cites RFC 6333 for use of DHCPv6 with DS-Lite.  RFC 6334
> should be cited - either in addition to or instead of RFC 6333.
>=20
> [5] Section 2.8 discusses IPv4 accounting at the AFTR, but notes that
> "the AFTR does not have detailed customer identity information."  Does
> that create a theft of service possibility?  If so, that possibility
> should be mentioned as a security consideration.  Also, Section 2.8
> ought to be expanded with a sentence or two explaining why the AFTR
> does not have that identity information, and in particular to explain
> whether and why it is unreasonable in some or all cases to expect
> that customer identity information be provided to the AFTR as part
> of provisioning each customer's softwire.
>=20
> Nits:
>=20
> Section 2.3 on MTU Considerations could usefully mention MTU discovery
> techniques, as possibilities for customer IPv4 traffic to adapt to a
> smaller IPv4 MTU.  If this is done, it would be useful to mention
> RFC 4821 in addition to the mention of RFC 1191 in RFC 6333.
>=20
> Section 2.4 should define "lawful intercept".  It would be helpful to
> cite a reference for this concept if something appropriate can be found.
>=20
> Section 2.5:
> - Are one or both types of logging recommended?
> - Last paragraph on p.4, "timestamped log" is not a good verb phrase.
> 	"maintain a timestamped log of" would be a better replacement.
> - Last paragraph in section, where is the batch file sent?
>=20
> In Section 2.7, I'm having a hard time understanding which traffic is
> intended to be subject to the Outgoing Policies and the Incoming Policies=
.
> Expanding each of those two bullets to explain what traffic is subject
> to each class of policies would help.
>=20
> Section 3.2.2.2 uses 192.0.0.2/32 as an example IP address for the
> B4.  That section should also cross-reference Section 5.7 on RFC 6333
> on IP address assignment to B4s, as other IP addresses may be used.
>=20
> idnits 2.12.13 found a tiny nit - draft-ietf-pcp-base is now at
> version 28.
>=20
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
> +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-7=
786
> david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> ----------------------------------------------------
>=20


From fandreas@cisco.com  Tue Dec  4 10:16:23 2012
Return-Path: <fandreas@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B33421F892F for <gen-art@ietfa.amsl.com>; Tue,  4 Dec 2012 10:16:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 bXps8z2WImlO for <gen-art@ietfa.amsl.com>; Tue,  4 Dec 2012 10:16:22 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 257DF21F872C for <gen-art@ietf.org>; Tue,  4 Dec 2012 10:16:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4036; q=dns/txt; s=iport; t=1354644982; x=1355854582; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=CpESVEvBLbUDwUY4d28NFj8Hpq/wkH9zQmBdzw51inE=; b=cjZWQqLsdphZrKi6+XMR/8DxR/00R12f15vD0p+4I+io5QuB/GJHZbA+ WhnfGR/mmZoSrHqaeYr0PmJY2Ic5KCT/DuFD6BqVc0sf0WQJCRDP91iCD HYjuYWf5HdjPw2cLy720qujv8AlEsOTfOtC4F1VGqWzk/Hza9nXO82xxQ E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtkGABs8vlCtJV2d/2dsb2JhbABEg0e6aBZzgh4BAQEDATg8BAEFCwsUBAkWDwkDAgECAUUGDQEHAQGIBgYMsESQYJB4A4hfiXGDM4EcjyuDEA
X-IronPort-AV: E=McAfee;i="5400,1158,6916"; a="149294356"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-7.cisco.com with ESMTP; 04 Dec 2012 18:16:21 +0000
Received: from rtp-fandreas-8717.cisco.com (rtp-fandreas-8717.cisco.com [10.117.7.88]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id qB4IGKne027051;  Tue, 4 Dec 2012 18:16:21 GMT
Message-ID: <50BE3DF4.6040206@cisco.com>
Date: Tue, 04 Dec 2012 13:16:20 -0500
From: Flemming Andreasen <fandreas@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>
References: <50B35AAF.20104@isode.com>
In-Reply-To: <50B35AAF.20104@isode.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 04 Dec 2012 10:31:34 -0800
Cc: draft-ietf-mmusic-sdp-media-capabilities.all@tools.ietf.org, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-mmusic-sdp-media-capabilities-15
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Dec 2012 18:16:23 -0000

Hi Alexey

Thank you for your review of the document - comments below:

On 11/26/12 7:03 AM, Alexey Melnikov wrote:
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>   <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments
> you may receive.
>
> Document: draft-ietf-mmusic-sdp-media-capabilities-15
> Reviewer: Alexey Melnikov
> Review Date: 2012-11-26
> IETF LC End Date: 2012-11-12
> IESG Telechat date: not scheduled
>
> Summary:  This document is ready for publication as Proposed Standard,
> with nits.
>
> Nits/editorial comments:
>
> This might be obvious to a SIP implementer, but the media type/subtype 
> definition RFC is not referenced anywhere. Should it be?
>
I don't believe so. The document is an extension of SDP (RFC 4566) which 
maintains its own media type name space and registry and hence it simply 
follows the rules of SDP (as defined in RFC 4566, which did change from 
the old SDP spec defined in RFC 2327).

RFC 4288 (which I presume you are referring to here) should not apply.



> 3.3.5. The Latent Configuration Attribute
>
>    Latent configurations may be announced by use of the latent
>    configuration attribute, which is defined in a manner very similar to
>    the potential configuration attribute.  The latent configuration
>    attribute combines the properties of a media line and a potential
>    configuration.  The media type (mt=) and the transport protocol(s)
>    (t=) MUST be specified since the latent configuration is independent
>    of any media line present.  In most cases, the media configuration
>    (m=) parameter MUST be present as well (see Section 4 for examples).
>
> This doesn't look like a correct use of MUST, please reword not to use 
> any RFC 2119 keyword or at least provide a pointer to a document that 
> contains the original requirement.
How about this:
<quote>
           Latent configurations may be announced by use of the latent
           configuration attribute, which is defined in a manner very 
similar
           to the potential configuration attribute. The latent 
configuration
           attribute combines the properties of a media line and a potential
           configuration. A latent configuration MUST include a media 
type (mt=) and a transport protocol configuration parameter
       since the latent configuration is independent
           of any media line present. In most cases, the media configuration
           (m=) parameter needs to be present as well (see Section 4 for 
examples).
</quote>
>
>    The lcfg attribute is a media level attribute.
>
>  [...]
>
>    If a cryptographic attribute, such as the SDES "a=crypto:" attribute
>    [RFC4568], is referenced by a latent configuration through an acap
>    attribute, any keying material required in the conventional
>    attribute, such as the SDES key/salt string, MUST be included in
>    order to satisfy formatting rules for the attribute.  The actual
>    value(s) of the keying material SHOULD be meaningless, and the
>
> Can you please elaborate on what are you trying to say here?
>
Is this better:
<quote>
          If a cryptographic attribute, such as the SDES "a=crypto:"
           attribute [RFC4568], is referenced by a latent
           configuration through an acap attribute, any keying material
           required in the conventional attribute, such as the SDES key/salt
           string, MUST be included in order to satisfy formatting rules for
           the attribute. Since the keying material will be visible but 
not actually used at this stage (since it's a latent configuration),
       the value(s) of the keying material SHOULD be meaningless, and 
the receiver of the lcfg attribute
       MUST ignore the values.
</quote>

> receiver of the lcfg attribute MUST ignore the values.
> .
>

Thanks

-- Flemming


From brian.e.carpenter@gmail.com  Wed Dec  5 02:38:34 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D0A121F88C7 for <gen-art@ietfa.amsl.com>; Wed,  5 Dec 2012 02:38:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.666
X-Spam-Level: 
X-Spam-Status: No, score=-101.666 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 U1T1wzUR+4s4 for <gen-art@ietfa.amsl.com>; Wed,  5 Dec 2012 02:38:33 -0800 (PST)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 245D021F881D for <gen-art@ietf.org>; Wed,  5 Dec 2012 02:38:32 -0800 (PST)
Received: by mail-we0-f172.google.com with SMTP id r3so2217314wey.31 for <gen-art@ietf.org>; Wed, 05 Dec 2012 02:38:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:content-type; bh=m4bNgs4S33FDsOT5ckwRyvNCj+PMxucrVFzULlXEqEc=; b=mZbfJHmPBC9N5U/n+yicxph3e1QT9R5bLIZT5iCZ+dOr/yiVmV9E1IhhT7bDxmuT5i cx5K32CKWg13pjGOaCkdew7qkcy/jCx9gKpGXbIO4ZYkF/86NcAVeWxp9waCL9wa+wHd LmlvoDNThhzo5fnaM3Bu5fgx9XD9HqZzcdJ9dhmfj3F+6JgSsaDacTEa01Sz4ntU7XbB uRmxlzmUSYv4XZM0QHK8Tzp47jTS4k0O8/tnDla5YXi31WIR8p9h7N6UMXSnQUrDPjTN kFeYHI0XEODSdokogP9FbV3reyqseuvYq6snraG0WrxJHYWPXpum3Mx1osuFbOolnrt3 CfAg==
Received: by 10.216.203.152 with SMTP id f24mr6610665weo.61.1354703912183; Wed, 05 Dec 2012 02:38:32 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-216-76.as13285.net. [2.102.216.76]) by mx.google.com with ESMTPS id b1sm5810168wix.11.2012.12.05.02.38.30 (version=SSLv3 cipher=OTHER); Wed, 05 Dec 2012 02:38:31 -0800 (PST)
Message-ID: <50BF242F.8000709@gmail.com>
Date: Wed, 05 Dec 2012 10:38:39 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: draft-hanes-dispatch-fax-capability.all@tools.ietf.org,  General Area Review Team <gen-art@ietf.org>
Content-Type: multipart/mixed; boundary="------------010003090900090703070300"
Cc: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: [Gen-art] Gen-ART LC review of draft-hanes-dispatch-fax-capability-06.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Dec 2012 10:38:34 -0000

This is a multi-part message in MIME format.
--------------010003090900090703070300
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Please see attached review.

     Brian



--------------010003090900090703070300
Content-Type: text/plain;
 name="draft-hanes-dispatch-fax-capability-06-carpenter.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="draft-hanes-dispatch-fax-capability-06-carpenter.txt"

SSBhbSB0aGUgYXNzaWduZWQgR2VuLUFSVCByZXZpZXdlciBmb3IgdGhpcyBkcmFmdC4gRm9y
IGJhY2tncm91bmQgb24NCkdlbi1BUlQsIHBsZWFzZSBzZWUgdGhlIEZBUSBhdA0KPGh0dHA6
Ly93aWtpLnRvb2xzLmlldGYub3JnL2FyZWEvZ2VuL3RyYWMvd2lraS9HZW5BcnRmYXE+Lg0K
DQpQbGVhc2UgcmVzb2x2ZSB0aGVzZSBjb21tZW50cyBhbG9uZyB3aXRoIGFueSBvdGhlciBM
YXN0IENhbGwgY29tbWVudHMNCnlvdSBtYXkgcmVjZWl2ZS4NCg0KRG9jdW1lbnQ6IGRyYWZ0
LWhhbmVzLWRpc3BhdGNoLWZheC1jYXBhYmlsaXR5LTA2LnR4dA0KUmV2aWV3ZXI6IEJyaWFu
IENhcnBlbnRlcg0KUmV2aWV3IERhdGU6IDIwMTItMTItMDUNCklFVEYgTEMgRW5kIERhdGU6
IDIwMTItMTItMjcNCklFU0cgVGVsZWNoYXQgZGF0ZTogDQoNClN1bW1hcnk6ICBBbG1vc3Qg
cmVhZHkNCi0tLS0tLS0tDQoNCkNvbW1lbnQ6ICBDbGVhciwgZWFzeSB0byB1bmRlcnN0YW5k
DQotLS0tLS0tLQ0KDQpNaW5vciBpc3N1ZToNCi0tLS0tLS0tLS0tLQ0KDQogICAuLi4gQSBV
QQ0KICAgcHJlZmVycmluZyB0aGUgcmVjZXB0aW9uIG9mIGZheCBjYWxscyBNVVNUIGluY2x1
ZGUgdGhlICJzaXAuZmF4Ig0KICAgbWVkaWEgZmVhdHVyZSB0YWcgaW4gdGhlIENvbnRhY3Qg
aGVhZGVyIGZpZWxkIG9mIFJFR0lTVEVSIG1lc3NhZ2VzLg0KICAgVG8gY29uZmlybSB0aGUg
cmVnaXN0cmF0aW9uIG9mIHRoaXMgcHJlZmVyZW5jZSwgYSBTSVAgW1JGQzMyNjFdDQogICBS
ZWdpc3RyYXIgTVVTVCB0aGVuIGluY2x1ZGUgdGhpcyB0YWcgaW4gdGhlIENvbnRhY3QgaGVh
ZGVyIGZpZWxkIG9mDQogICBpdHMgMjAwIE9LIHJlc3BvbnNlLg0KDQpJZiB0aGUgUmVnaXN0
cmFyIGRvZXMgbm90IGRvIHRoaXMgKGUuZy4gYmVjYXVzZSBpdCBoYXNuJ3QgYmVlbiB1cGRh
dGVkDQp0byBzdXBwb3J0IHRoZSBuZXcgdGFnKSwgd2hhdCBkb2VzIHRoZSBVQSBkbyB3aGVu
IGl0IHJlY2VpdmVzIHRoZQ0KMjAwIE9LIHJlc3BvbnNlIHRoYXQgZG9lc24ndCBpbmNsdWRl
IHRoZSB0YWc/DQo=
--------------010003090900090703070300--

From brian.e.carpenter@gmail.com  Wed Dec  5 03:35:48 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 016C921F8977 for <gen-art@ietfa.amsl.com>; Wed,  5 Dec 2012 03:35:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.667
X-Spam-Level: 
X-Spam-Status: No, score=-101.667 tagged_above=-999 required=5 tests=[AWL=0.024, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 PY+Nw9xUngp6 for <gen-art@ietfa.amsl.com>; Wed,  5 Dec 2012 03:35:47 -0800 (PST)
Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com [209.85.212.180]) by ietfa.amsl.com (Postfix) with ESMTP id 595A521F896F for <gen-art@ietf.org>; Wed,  5 Dec 2012 03:35:47 -0800 (PST)
Received: by mail-wi0-f180.google.com with SMTP id hj13so1318482wib.13 for <gen-art@ietf.org>; Wed, 05 Dec 2012 03:35:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=NAa9HIzc/MHwGLe2aiGzqscaW8tDV54RTMLY2LE5G5I=; b=HwazKCg/w7qCWlaWU4DQgJUa0CX568sJN+hyOu7q31uV0DqdpBapK+1OWHSt2T8l4r wRc379Qp9jHt2xIo8u1epo5pPzE9gQlsqRU9T6eqWaiokBgipUpbiSlwRRFvGIJKjAHs RiJ3UxGkbga1Z/1ziN4/MskuZBJxMompuzOq1GMAE29YNGhc4l2FLNQEg0Wj4HFsieVl epVGiiUdYq/dXn+ZRGeVmTLT5h51zSM2DwjQbGpl0sj9TeUn/YOse380h/adodGCq5eM twitcoSKjshRP06x6VJl8glczYW0g5wcMLxOhXYbS7WPdifyCHE9trPAwjnCq/XugIoA t9rg==
Received: by 10.180.86.167 with SMTP id q7mr2609894wiz.21.1354707346587; Wed, 05 Dec 2012 03:35:46 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-216-76.as13285.net. [2.102.216.76]) by mx.google.com with ESMTPS id d9sm19285295wiw.0.2012.12.05.03.35.44 (version=SSLv3 cipher=OTHER); Wed, 05 Dec 2012 03:35:45 -0800 (PST)
Message-ID: <50BF3199.4000109@gmail.com>
Date: Wed, 05 Dec 2012 11:35:53 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Kevin Fleming <kevin@kpfleming.us>
References: <50BF242F.8000709@gmail.com> <CAE+Udoqd_GHaEF6h_HGVZP8AwkKMaVGygKc5sJjcr8X=SsTiKA@mail.gmail.com>
In-Reply-To: <CAE+Udoqd_GHaEF6h_HGVZP8AwkKMaVGygKc5sJjcr8X=SsTiKA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: General Area Review Team <gen-art@ietf.org>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, draft-hanes-dispatch-fax-capability.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-hanes-dispatch-fax-capability-06.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Dec 2012 11:35:48 -0000

On 05/12/2012 11:01, Kevin Fleming wrote:
> The language in RFC 3840 doesn't appear to contemplate the situation you've
> proposed. In its world, registrars can either support prefs (and will
> accept "Require: pref") or they don't, and they don't have knowledge of
> which feature tags are registered with IANA and which are not. Of course,
> they *coud* attempt to validate the tags expressed by the UA, but I don't
> see an explicit way for the registrar to indicate that the UA included
> disallowed tags in its request.

Understood, but in that case I don't see what good the confirmation
of the tag from the registrar to the UA achieves - the UA is not going
to be able to do anything with it (except maybe log whether it was
received).

    Brian

From kevin@kpfleming.us  Wed Dec  5 03:01:46 2012
Return-Path: <kevin@kpfleming.us>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2357F21F885A for <gen-art@ietfa.amsl.com>; Wed,  5 Dec 2012 03:01:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 0BqF9fkWdsmA for <gen-art@ietfa.amsl.com>; Wed,  5 Dec 2012 03:01:45 -0800 (PST)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 632C921F8602 for <gen-art@ietf.org>; Wed,  5 Dec 2012 03:01:45 -0800 (PST)
Received: by mail-lb0-f172.google.com with SMTP id y2so4390037lbk.31 for <gen-art@ietf.org>; Wed, 05 Dec 2012 03:01:44 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=EIirIL0yOss4BJKRS2jyWES9abRPtsUatUkHXEA580w=; b=YchHqTQ7w7hwWfOI+yg5tI5KerdG1UDTB9QXM6gdlFzHz/dESB8l8lwjWpBOutbFHm cQfdSHe1FWJfkLCdEF+VjFGe/AOyl4VulOBWdGhcNVXJZo5b6ENYicuuongMDXd58FTk PbTsonPcTj6mW8H5FolDhKqIM4ahgntjMpqLvuRbXFhN/Mly2ZaaOB34PW4sZN2ajoPf QFPJuBieLxd4LJYneybbgcqy8wTHBqzUuktjRrIHMdznUvGFQBN1EXN0JKLDyFDsuFda inde8svmGJ0qqki2A3YgDiNvpSu0GToac2zJ0iEm3eM6DaayjZILAjppLuvRUnk0gzz5 aB1Q==
MIME-Version: 1.0
Received: by 10.152.145.202 with SMTP id sw10mr16339298lab.22.1354705304189; Wed, 05 Dec 2012 03:01:44 -0800 (PST)
Received: by 10.114.18.144 with HTTP; Wed, 5 Dec 2012 03:01:44 -0800 (PST)
In-Reply-To: <50BF242F.8000709@gmail.com>
References: <50BF242F.8000709@gmail.com>
Date: Wed, 5 Dec 2012 06:01:44 -0500
Message-ID: <CAE+Udoqd_GHaEF6h_HGVZP8AwkKMaVGygKc5sJjcr8X=SsTiKA@mail.gmail.com>
From: Kevin Fleming <kevin@kpfleming.us>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=e89a8f2348cf6e7a9504d018e888
X-Gm-Message-State: ALoCoQn/4GN9S+jlVmvE/ZmbDrAXoD6yCg0zTPRn8XWziEaFzBxINJ9HO7QQGRSK+AELtgTEPyVa
X-Mailman-Approved-At: Wed, 05 Dec 2012 03:36:26 -0800
Cc: General Area Review Team <gen-art@ietf.org>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, draft-hanes-dispatch-fax-capability.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-hanes-dispatch-fax-capability-06.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Dec 2012 11:01:46 -0000

--e89a8f2348cf6e7a9504d018e888
Content-Type: text/plain; charset=UTF-8

The language in RFC 3840 doesn't appear to contemplate the situation you've
proposed. In its world, registrars can either support prefs (and will
accept "Require: pref") or they don't, and they don't have knowledge of
which feature tags are registered with IANA and which are not. Of course,
they *coud* attempt to validate the tags expressed by the UA, but I don't
see an explicit way for the registrar to indicate that the UA included
disallowed tags in its request.

--e89a8f2348cf6e7a9504d018e888
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

The language in RFC 3840 doesn&#39;t appear to contemplate the situation yo=
u&#39;ve proposed. In its world, registrars can either support prefs (and w=
ill accept &quot;Require: pref&quot;) or they don&#39;t, and they don&#39;t=
 have knowledge of which feature tags are registered with IANA and which ar=
e not. Of course, they *coud* attempt to validate the tags expressed by the=
 UA, but I don&#39;t see an explicit way for the registrar to indicate that=
 the UA included disallowed tags in its request.

--e89a8f2348cf6e7a9504d018e888--

From kevin@kpfleming.us  Wed Dec  5 06:12:05 2012
Return-Path: <kevin@kpfleming.us>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7011521F89D4 for <gen-art@ietfa.amsl.com>; Wed,  5 Dec 2012 06:12:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 TpQaiJUbnE56 for <gen-art@ietfa.amsl.com>; Wed,  5 Dec 2012 06:12:04 -0800 (PST)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7069421F89CB for <gen-art@ietf.org>; Wed,  5 Dec 2012 06:12:04 -0800 (PST)
Received: by mail-lb0-f172.google.com with SMTP id y2so4583281lbk.31 for <gen-art@ietf.org>; Wed, 05 Dec 2012 06:12:03 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=C0f/zvoswR+IkZ/FObrGs4DvOmjDs3qXzeGtHqrYbwQ=; b=LvECcwIp5c7AZj9gjN8Wkw5UFlSK/OrHezsbNZxggQstRaeqrNeI98ghbEiq4+FvVN GV28YO25BLvgEEVZdUQpJx8vfVCFV9qav89Mq+9hddCH2f0wtLN1ERSzBmb42CYd0ekU gtYKdivwkSG9d6hFaiYuyAO5xDJfDY48EKz5WBj/LwWwRng4HX77g+7b7FQBfN409PeB CLT4njh8rtdbgzGajJ6Za134LGAQeJNSdDZffKYPAh2qo0mmjpVg9sr8TC4/gXp2xdCQ 0Oqt/ofevH/yVbGTcZHY4H59F/veyMUWP7lKFGa10ChuCh6zO7RshG+CanK2mXJGK4xi GV9w==
MIME-Version: 1.0
Received: by 10.152.46.161 with SMTP id w1mr16843134lam.27.1354716723170; Wed, 05 Dec 2012 06:12:03 -0800 (PST)
Received: by 10.114.18.144 with HTTP; Wed, 5 Dec 2012 06:12:03 -0800 (PST)
In-Reply-To: <50BF3199.4000109@gmail.com>
References: <50BF242F.8000709@gmail.com> <CAE+Udoqd_GHaEF6h_HGVZP8AwkKMaVGygKc5sJjcr8X=SsTiKA@mail.gmail.com> <50BF3199.4000109@gmail.com>
Date: Wed, 5 Dec 2012 09:12:03 -0500
Message-ID: <CAE+UdoqSZ_d1xTkyrTs-9rFq2OLyo0zZaxA29pqj_fo6vfk1RA@mail.gmail.com>
From: Kevin Fleming <kevin@kpfleming.us>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=bcaec55408900e4e6804d01b91f2
X-Gm-Message-State: ALoCoQl/+uVWi4TgsNlF8qkyhscKvgwmTmKKGQt1P6aw/vvJQIwl3fkyEM8lg5M4HMUkJuvgJJwT
Cc: General Area Review Team <gen-art@ietf.org>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, draft-hanes-dispatch-fax-capability.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-hanes-dispatch-fax-capability-06.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Dec 2012 14:12:05 -0000

--bcaec55408900e4e6804d01b91f2
Content-Type: text/plain; charset=UTF-8

I suppose it could choose to unregister and re-register in some other way
in order to achieve its goals of receiving FAX calls, if it was configured
with enough network information to do so.

Now that I think about it some more, is a registrar even allowed to return
a Contact header that differs from the one the UA supplied in its REGISTER
request? I suspect this is *not* allowed, and so if the registrar supports
Caller-Pref but the specific tag(s) in question fail some sort of
validation process, its only recourse would be to fail the REGISTER request
with a suitable error response.


On Wed, Dec 5, 2012 at 6:35 AM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> On 05/12/2012 11:01, Kevin Fleming wrote:
> > The language in RFC 3840 doesn't appear to contemplate the situation
> you've
> > proposed. In its world, registrars can either support prefs (and will
> > accept "Require: pref") or they don't, and they don't have knowledge of
> > which feature tags are registered with IANA and which are not. Of course,
> > they *coud* attempt to validate the tags expressed by the UA, but I don't
> > see an explicit way for the registrar to indicate that the UA included
> > disallowed tags in its request.
>
> Understood, but in that case I don't see what good the confirmation
> of the tag from the registrar to the UA achieves - the UA is not going
> to be able to do anything with it (except maybe log whether it was
> received).
>
>     Brian
>

--bcaec55408900e4e6804d01b91f2
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I suppose it could choose to unregister and re-register in some other way i=
n order to achieve its goals of receiving FAX calls, if it was configured w=
ith enough network information to do so.<div><br></div><div>Now that I thin=
k about it some more, is a registrar even allowed to return a Contact heade=
r that differs from the one the UA supplied in its REGISTER request? I susp=
ect this is *not* allowed, and so if the registrar supports Caller-Pref but=
 the specific tag(s) in question fail some sort of validation process, its =
only recourse would be to fail the REGISTER request with a suitable error r=
esponse.</div>
<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Wed, Dec 5=
, 2012 at 6:35 AM, Brian E Carpenter <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:brian.e.carpenter@gmail.com" target=3D"_blank">brian.e.carpenter@gmail.co=
m</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"HOEnZb"><div class=3D"h5">On 0=
5/12/2012 11:01, Kevin Fleming wrote:<br>
&gt; The language in RFC 3840 doesn&#39;t appear to contemplate the situati=
on you&#39;ve<br>
&gt; proposed. In its world, registrars can either support prefs (and will<=
br>
&gt; accept &quot;Require: pref&quot;) or they don&#39;t, and they don&#39;=
t have knowledge of<br>
&gt; which feature tags are registered with IANA and which are not. Of cour=
se,<br>
&gt; they *coud* attempt to validate the tags expressed by the UA, but I do=
n&#39;t<br>
&gt; see an explicit way for the registrar to indicate that the UA included=
<br>
&gt; disallowed tags in its request.<br>
<br>
</div></div>Understood, but in that case I don&#39;t see what good the conf=
irmation<br>
of the tag from the registrar to the UA achieves - the UA is not going<br>
to be able to do anything with it (except maybe log whether it was<br>
received).<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
=C2=A0 =C2=A0 Brian<br>
</font></span></blockquote></div><br></div>

--bcaec55408900e4e6804d01b91f2--

From brian.e.carpenter@gmail.com  Wed Dec  5 08:02:25 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B39321F8CCE for <gen-art@ietfa.amsl.com>; Wed,  5 Dec 2012 08:02:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.67
X-Spam-Level: 
X-Spam-Status: No, score=-101.67 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 ItCd6r1Xj+T1 for <gen-art@ietfa.amsl.com>; Wed,  5 Dec 2012 08:02:25 -0800 (PST)
Received: from mail-wg0-f42.google.com (mail-wg0-f42.google.com [74.125.82.42]) by ietfa.amsl.com (Postfix) with ESMTP id 91C3921F8BA9 for <gen-art@ietf.org>; Wed,  5 Dec 2012 08:02:24 -0800 (PST)
Received: by mail-wg0-f42.google.com with SMTP id dr1so1057840wgb.1 for <gen-art@ietf.org>; Wed, 05 Dec 2012 08:02:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=YYPLuY81HgGr2kIlIarED8BUlbi61eDz3hz1uWX4bJo=; b=HEbXSJeIdROWua3JvTdeY4GabMlLb94DLEzBeXp3lXRuFcETCMhTX+XGCgLD69tpQK f4axi0XrmXa2mnfbltQDHXqgmBZt6/Vm7wXxDEDwOczHaxzXoh+SZelGQZLn3PIWziF3 mvAeKtahiqeqGQj7R0JJ3gjWP2szftV1YNjELGsAahFVdFBObh3Hb5f0VWyQRCSOjzDL UDlIgHIt/tfaenXqTLTl3LFAO8Q004gYJnQCKbDZrbaJ2IoIpYaDXMtwREU1VECIHip7 Vl+FaTq/Qq3iy6CDFZTaIIvTvs96gIJxj6fHOR8MaYRiOgvB9mphBOSYhytOTziylyUl 2YPg==
Received: by 10.180.81.170 with SMTP id b10mr4048677wiy.16.1354723333359; Wed, 05 Dec 2012 08:02:13 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-216-76.as13285.net. [2.102.216.76]) by mx.google.com with ESMTPS id eu8sm19573789wib.1.2012.12.05.08.02.08 (version=SSLv3 cipher=OTHER); Wed, 05 Dec 2012 08:02:10 -0800 (PST)
Message-ID: <50BF700A.3010402@gmail.com>
Date: Wed, 05 Dec 2012 16:02:18 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Kevin Fleming <kevin@kpfleming.us>
References: <50BF242F.8000709@gmail.com>	<CAE+Udoqd_GHaEF6h_HGVZP8AwkKMaVGygKc5sJjcr8X=SsTiKA@mail.gmail.com>	<50BF3199.4000109@gmail.com> <CAE+UdoqSZ_d1xTkyrTs-9rFq2OLyo0zZaxA29pqj_fo6vfk1RA@mail.gmail.com>
In-Reply-To: <CAE+UdoqSZ_d1xTkyrTs-9rFq2OLyo0zZaxA29pqj_fo6vfk1RA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: General Area Review Team <gen-art@ietf.org>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, draft-hanes-dispatch-fax-capability.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-hanes-dispatch-fax-capability-06.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Dec 2012 16:02:25 -0000

On 05/12/2012 14:12, Kevin Fleming wrote:
> I suppose it could choose to unregister and re-register in some other way
> in order to achieve its goals of receiving FAX calls, if it was configured
> with enough network information to do so.
> 
> Now that I think about it some more, is a registrar even allowed to return
> a Contact header that differs from the one the UA supplied in its REGISTER
> request? I suspect this is *not* allowed, and so if the registrar supports
> Caller-Pref but the specific tag(s) in question fail some sort of
> validation process, its only recourse would be to fail the REGISTER request
> with a suitable error response.

If that's the standard behaviour, it would of course answer my question.

   Brian

> 
> 
> On Wed, Dec 5, 2012 at 6:35 AM, Brian E Carpenter <
> brian.e.carpenter@gmail.com> wrote:
> 
>> On 05/12/2012 11:01, Kevin Fleming wrote:
>>> The language in RFC 3840 doesn't appear to contemplate the situation
>> you've
>>> proposed. In its world, registrars can either support prefs (and will
>>> accept "Require: pref") or they don't, and they don't have knowledge of
>>> which feature tags are registered with IANA and which are not. Of course,
>>> they *coud* attempt to validate the tags expressed by the UA, but I don't
>>> see an explicit way for the registrar to indicate that the UA included
>>> disallowed tags in its request.
>> Understood, but in that case I don't see what good the confirmation
>> of the tag from the registrar to the UA achieves - the UA is not going
>> to be able to do anything with it (except maybe log whether it was
>> received).
>>
>>     Brian
>>
> 

From ben@nostrum.com  Wed Dec  5 14:14:53 2012
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FA8F21F8CE8; Wed,  5 Dec 2012 14:14:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
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 Wa-M41qwQ44h; Wed,  5 Dec 2012 14:14:52 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 5EFF421F8CE2; Wed,  5 Dec 2012 14:14:52 -0800 (PST)
Received: from [172.20.10.2] (mobile-166-137-149-189.mycingular.net [166.137.149.189]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qB5MEinA082069 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 5 Dec 2012 16:14:44 -0600 (CST) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <7B7C06EA-E5EB-4FD6-ADE6-1A8E38B11405@gmail.com>
Date: Wed, 5 Dec 2012 16:14:38 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <F2278C98-4C60-4D94-910D-D1E2607936B5@nostrum.com>
References: <18E6B18A-D465-47C6-9E06-886DFBFA1F67@nostrum.com> <F53DCC9A-8AA1-42D4-BF19-88ABCCCA68A7@gmail.com> <3B3FEC40-3D96-4F77-A628-E80DFAEB2278@nostrum.com> <F60EDDFC-0612-4636-AFC7-3D7FD9052D74@gmail.com> <7B7C06EA-E5EB-4FD6-ADE6-1A8E38B11405@gmail.com>
To: Mahesh Jethanandani <mjethanandani@gmail.com>
X-Mailer: Apple Mail (2.1499)
Received-SPF: pass (nostrum.com: 166.137.149.189 is authenticated by a trusted mechanism)
Cc: "draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org" <draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of	draft-ietf-karp-routing-tcp-analysis-05.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Dec 2012 22:14:53 -0000

Hi Mahesh,

The proposed changes work for me.

Thanks!

Ben.

On Nov 30, 2012, at 11:03 AM, Mahesh Jethanandani =
<mjethanandani@gmail.com> wrote:

> Ben,
>=20
> See inline. If you are ok with these changes, I will go ahead and =
submit an updated version of the draft.
>=20
> On Nov 25, 2012, at 5:56 PM, Mahesh Jethanandani wrote:
>=20
>> Further trimming it to sections that require a response.
>>=20
>> On Nov 21, 2012, at 3:12 PM, Ben Campbell wrote:
>>=20
>>>=20
>>>>>=20
>>>>> *** Minor issues *** :
>>>>>=20
>>>>> -- section 2.2, last paragraph:
>>>>>=20
>>>>> The IKE mention lacks context. Do you mean to suggest IKE with =
IPSec? I assume so, but there's been no mention of IPSec so far.
>>>>=20
>>>> No. It implies the use of IKEv2 protocol for performing mutual =
authentication and establishing SA. There is no suggestion of using IKE =
with IPSec.
>>>>=20
>>>> How about this?
>>>>=20
>>>> For point-to-point key management IKEv2[RFC5996] protocol provides =
...
>>>=20
>>> 5996 describes IKEv2 as a component of IPSec, and a key-management =
mechanism for ESP and AH SAs. Now, I won't claim to be an IKE expert by =
any extent, but I think that if you mean to use IKE _without_ IPSec it =
would be good to add a sentence or two pointing that out. Or is there =
some other reference that could be used that describes using IKEv2 for =
non-IPSec SAs?
>>=20
>> Added this sentence.
>>=20
>> Although IKEv2 is discussed as a component of IPsec, KMP can use just =
the mutual authentication and SA establishment portion of IKEv2.
>=20
> This statement has been further modified to:
>=20
> For point-to-point key management IKEv2 [RFC5996] provides for
>  automated key exchange under a SA and can be used for a comprehensive
>  Key Management Protocol (KMP) solution for routers.  IKEv2 can be =
used
>  for both IPsec SAs [RFC4301] and other types of SAs. For example,=20
>  Fibre Channel SAs  [RFC4595] are currently negotiated with IKEv2. =
Using
>  IKEv2 to negotiate TCP-AO is a possible option.
>=20
>=20
>>=20
>>>=20
>>>>=20
>>>>>=20
>>>>> *** Nits/editorial comments ***:
>>>>>=20
>>>>> -- IDNits indicates some unused and obsoleted references. Please =
check.
>>>>=20
>>>> Found one unused reference and have removed it.
>>>=20
>>> Seems like there were more than one. =46rom IDNits:
>>>=20
>>>  =3D=3D Missing Reference: 'IRR' is mentioned on line 92, but not =
defined
>>>=20
>>>  =3D=3D Unused Reference: 'RFC2409' is defined on line 585, but no =
explicit
>>>     reference was found in the text
>>>=20
>>>  =3D=3D Unused Reference: 'RFC3547' is defined on line 588, but no =
explicit
>>>     reference was found in the text
>>>=20
>>>  ** Obsolete normative reference: RFC 2385 (Obsoleted by RFC 5925)
>>>=20
>>>  -- Obsolete informational reference (is this intentional?): RFC =
2409
>>>     (Obsoleted by RFC 4306)
>>>=20
>>>  -- Obsolete informational reference (is this intentional?): RFC =
3547
>>>     (Obsoleted by RFC 6407)
>>=20
>> I have removed these unused references.
>>=20
>>>=20
>>>>>=20
>>>>> -- section 4, 2nd paragraph: "In addition Improving TCP=92s =
Robustness to Blind In-Window Attacks."
>>>>>=20
>>>>> sentence fragment.
>>>>=20
>>>> Changed it to say:
>>>>=20
>>>> In addition, the recommendations in Improving TCP's Robustness to =
Blind In-Window Attacks
>>>>=20
>>>=20
>>> Am I correct in assuming this merges with the following sentence? =
Otherwise, it's still a fragment.
>>>=20
>>=20
>> Changed it to:
>>=20
>> In addition, the recommendations in RFC 5961 should also be followed =
...
>=20
> Mahesh Jethanandani
> mjethanandani@gmail.com
>=20
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From mahoney@nostrum.com  Thu Dec  6 15:38:07 2012
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04F8521E802E for <gen-art@ietfa.amsl.com>; Thu,  6 Dec 2012 15:38:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
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 CULUmWtRdMwo for <gen-art@ietfa.amsl.com>; Thu,  6 Dec 2012 15:38:06 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id F29C421F8561 for <gen-art@ietf.org>; Thu,  6 Dec 2012 15:38:05 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-45-100.dllstx.fios.verizon.net [173.71.45.100]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qB6Nc4tb051146 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 6 Dec 2012 17:38:05 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <50C12C5D.6090706@nostrum.com>
Date: Thu, 06 Dec 2012 17:38:05 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 173.71.45.100 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2012-12-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Dec 2012 23:38:07 -0000

Hi all,

The following reviewers have assignments:

Reviewer           LC end      Draft

David Black        2012-12-14  draft-ietf-sidr-algorithm-agility-08

Elwyn Davies       2012-12-14  draft-ietf-sidr-usecases-05

Francis Dupont     2012-12-17  draft-ietf-sipclf-format-09

Joel Halpern       2012-12-17  draft-ietf-sipclf-problem-statement-11 *

Kathleen Moriarty  2012-12-17  draft-ietf-bliss-call-completion-18

Mary Barnes        2012-12-19  draft-ietf-mboned-auto-multicast-14

Martin Thomson     2013-01-02  draft-schaad-pkix-rfc2875-bis-03

Meral Shirazipour  2012-12-20  draft-ietf-v6ops-icp-guidance-04

* 2nd last call


I have made the assignments in the review tool:
http://art.tools.ietf.org/tools/art/genart/

And the assignments are captured in the spreadsheets:
http://wiki.tools.ietf.org/dav/genart/gen-art.html
http://wiki.tools.ietf.org/dav/genart/gen-art-by-reviewer.html


The standard template is included below.

Thanks,

Jean

-------------------------------------------------------------------

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

From mahoney@nostrum.com  Thu Dec  6 15:42:03 2012
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2F4821F8521 for <gen-art@ietfa.amsl.com>; Thu,  6 Dec 2012 15:42:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
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 ERDVCUIq7uvE for <gen-art@ietfa.amsl.com>; Thu,  6 Dec 2012 15:42:03 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 2C10321F8517 for <gen-art@ietf.org>; Thu,  6 Dec 2012 15:42:03 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-45-100.dllstx.fios.verizon.net [173.71.45.100]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qB6Ng2nm051578 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 6 Dec 2012 17:42:02 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <50C12D4B.90609@nostrum.com>
Date: Thu, 06 Dec 2012 17:42:03 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 173.71.45.100 is authenticated by a trusted mechanism)
Subject: [Gen-art] Assignments for the 2012-12-13 telechat
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Dec 2012 23:42:04 -0000

Hi all,

The following reviewers have assignments:

Reviewer             LC end      Draft

Christer Holmberg    2012-10-25 draft-leiba-3777upd-eligibility-05*
Christer Holmberg    2012-10-03 draft-kumaki-murai-l3vpn-rsvp-te-07 *

Francis Dupont       2012-11-26 draft-ietf-ppsp-problem-statement-11

Joel Halpern         2012-11-26  draft-nir-ipsecme-erx-09

Peter McCann         2012-03-30 
draft-ietf-dhc-dhcpv6-redundancy-consider-03 *

Richard Barnes       2012-11-26 draft-ietf-mediactrl-mrb-16

Suresh Krishnan      2012-12-10 draft-ietf-tcpm-initcwnd-06

* Earlier draft reviewed
** Already reviewed


I have made the assignments in the review tool:
http://art.tools.ietf.org/tools/art/genart/

And the assignments are captured in the spreadsheets:
http://wiki.tools.ietf.org/dav/genart/gen-art.html
http://wiki.tools.ietf.org/dav/genart/gen-art-by-reviewer.html

For your convenience, the review boilerplate template is included below.

Note that reviews should ideally be posted to the gen-art mailing list
by COB on Tuesday:
http://wiki.tools.ietf.org/area/gen/trac/wiki/

Jean

-------------------------------------------------------------------

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
< http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

From jmh@joelhalpern.com  Thu Dec  6 15:51:22 2012
Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6125921F86DC for <gen-art@ietfa.amsl.com>; Thu,  6 Dec 2012 15:51:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.376
X-Spam-Level: 
X-Spam-Status: No, score=-102.376 tagged_above=-999 required=5 tests=[AWL=-0.111, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
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 zxZwyi4F3EFV for <gen-art@ietfa.amsl.com>; Thu,  6 Dec 2012 15:51:19 -0800 (PST)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id B172721F86AD for <gen-art@ietf.org>; Thu,  6 Dec 2012 15:51:17 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by morbo.tigertech.net (Postfix) with ESMTP id 5FE55A3AD1 for <gen-art@ietf.org>; Thu,  6 Dec 2012 15:51:16 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 195AC1C9E76; Thu,  6 Dec 2012 15:51:14 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [10.10.10.104] (pool-71-161-51-204.clppva.btas.verizon.net [71.161.51.204]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 7FC7A1C0713; Thu,  6 Dec 2012 15:51:13 -0800 (PST)
Message-ID: <50C12F61.1060804@joelhalpern.com>
Date: Thu, 06 Dec 2012 18:50:57 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>,  General Area Review Team <gen-art@ietf.org>
References: <7594FB04B1934943A5C02806D1A2204B023C19@ESESSMB209.ericsson.se> <50954629.6040401@nostrum.com>
In-Reply-To: <50954629.6040401@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Gen-art]   Review: draft-nir-ipsecme-erx-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Dec 2012 23:51:22 -0000

I am the assigned Gen-ART reviewer for this draft. For background on 
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments 
you may receive.

Document: draft-nir-ipsecme-erx-09
     An IKEv2 Extension for Supporting ERP
Reviewer: Joel M. Halpern
Review Date: 6-December-2012
IETF LC End Date: 26-November-2012
IESG Telechat date:13-December-2012

Summary: This document is still ready for publication as an Experimental 
RFC.


_______________________________________________
Gen-art mailing list
Gen-art@ietf.org
https://www.ietf.org/mailman/listinfo/gen-art


From martin.thomson@gmail.com  Thu Dec  6 17:02:52 2012
Return-Path: <martin.thomson@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AA5F21F85D3 for <gen-art@ietfa.amsl.com>; Thu,  6 Dec 2012 17:02:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.984
X-Spam-Level: 
X-Spam-Status: No, score=-4.984 tagged_above=-999 required=5 tests=[AWL=-1.385, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 qBtq-RSAWCag for <gen-art@ietfa.amsl.com>; Thu,  6 Dec 2012 17:02:52 -0800 (PST)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 927E021F8587 for <gen-art@ietf.org>; Thu,  6 Dec 2012 17:02:51 -0800 (PST)
Received: by mail-la0-f44.google.com with SMTP id d3so5946760lah.31 for <gen-art@ietf.org>; Thu, 06 Dec 2012 17:02:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=Tj4ccNi6GkO0Lm1AZy5qusloOiJmAv3vMXGb02eAaFo=; b=WvXzHCSF4fLFuJOnIeYBVZgBFlkfGJd9TCauqFfmNf2LjOjgAt0h6S4M9h1Oh2R084 ry6Nxy7Bm6dgtIY7IqEUs3TkDqk9Wbq7e4icnxRnH4DXhdpMh7X4+5pQs1PtwlggrrCC GO7+w9TFp29VSlUf+04/FDA/oFUGS5fpCRf+FpZZeHb2y1lFtt+7V8G5yb45qBmjbqnc CT+DzwaeOKO/XWNWfa/nMrhEJtRsKygtdVchrufwb/s4suLzhGRg4t3jnQTKp5A8Yyiq luLSxIo72wMZa8p6mRRnTpqM/bDJHCIw2MIUFyW2tqOGe8i/VknE6q5K1PFpXV3bicEv 1egA==
MIME-Version: 1.0
Received: by 10.112.44.164 with SMTP id f4mr1755806lbm.111.1354842170462; Thu, 06 Dec 2012 17:02:50 -0800 (PST)
Received: by 10.112.98.200 with HTTP; Thu, 6 Dec 2012 17:02:50 -0800 (PST)
Date: Thu, 6 Dec 2012 17:02:50 -0800
Message-ID: <CABkgnnW_bUGEQSeupWSmw5d8gT-jWDreCptihhvemzGU6pzuWw@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>, draft-schaad-pkix-rfc2875-bis.all@tools.ietf.org
Content-Type: text/plain; charset=UTF-8
Subject: [Gen-art] GenART review of draft-schaad-pkix-rfc2875-bis-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Dec 2012 01:02:52 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: raft-schaad-pkix-rfc2875-bis-03
Reviewer: Martin Thomson
Review Date: 2012-12-06
IETF LC End Date: Aaaages
IESG Telechat date: (if known)

Summary: Looks good to me.  Ship it.

Nits/editorial comments:

Section 3 does not establish a notation convention for multiplication.
 I didn't find a specific place that this was a problem, but it seemed
appropriate since multiplications was, in some places denoted 'n*b'
and others as 'xy', even though multi-character identifiers are used
in many places.  This does imply that a precedence override is
necessary.  I suggest parentheses, since they are already used
extensively.

Section 3: s/MAC funtion/MAC functions/

Section 5: could use a more rigorous list construction, the
definitions all run together

Needs more ASN.1

--Martin

From jmh@joelhalpern.com  Thu Dec  6 20:06:12 2012
Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6229121F87DC for <gen-art@ietfa.amsl.com>; Thu,  6 Dec 2012 20:06:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.37
X-Spam-Level: 
X-Spam-Status: No, score=-102.37 tagged_above=-999 required=5 tests=[AWL=-0.105, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
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 JnhcCUVi3GyF for <gen-art@ietfa.amsl.com>; Thu,  6 Dec 2012 20:06:12 -0800 (PST)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 090D921F850D for <gen-art@ietf.org>; Thu,  6 Dec 2012 20:06:12 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by morbo.tigertech.net (Postfix) with ESMTP id 3F9805596C3 for <gen-art@ietf.org>; Thu,  6 Dec 2012 20:06:09 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 991341C07EA; Thu,  6 Dec 2012 20:06:08 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [10.10.10.104] (pool-71-161-51-204.clppva.btas.verizon.net [71.161.51.204]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 8DC051C0713; Thu,  6 Dec 2012 20:06:04 -0800 (PST)
Message-ID: <50C16B12.4080500@joelhalpern.com>
Date: Thu, 06 Dec 2012 23:05:38 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>,  General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Gen-art]  Review: draft-ietf-sipclf-problem-statement-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Dec 2012 04:06:12 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-sipclf-problem-statement-11
  The Common Log Format (CLF) for the Session Initiation Protocol (SIP):
                         Framework and Data Model
Reviewer: Joel M. Halpern
Review Date: 6-December-2012
IETF LC End Date: 1-December-2012
IESG Telechat date: N/A

Summary: This document is ready for publication as a Proposed Standard

Major issues: None

Minor issues: None

Nits/editorial comments: None


From ietf@augustcellars.com  Fri Dec  7 00:26:10 2012
Return-Path: <ietf@augustcellars.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D30A321F89FE for <gen-art@ietfa.amsl.com>; Fri,  7 Dec 2012 00:26:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 nUuPoaUx06Fe for <gen-art@ietfa.amsl.com>; Fri,  7 Dec 2012 00:26:10 -0800 (PST)
Received: from smtp1.pacifier.net (smtp1.pacifier.net [64.255.237.171]) by ietfa.amsl.com (Postfix) with ESMTP id 38AB621F89CC for <gen-art@ietf.org>; Fri,  7 Dec 2012 00:26:09 -0800 (PST)
Received: from Philemon (mail.augustcellars.com [50.34.17.238]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp1.pacifier.net (Postfix) with ESMTPSA id 877AE2CA25; Fri,  7 Dec 2012 00:26:08 -0800 (PST)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Martin Thomson'" <martin.thomson@gmail.com>, <gen-art@ietf.org>, <draft-schaad-pkix-rfc2875-bis.all@tools.ietf.org>
References: <CABkgnnW_bUGEQSeupWSmw5d8gT-jWDreCptihhvemzGU6pzuWw@mail.gmail.com>
In-Reply-To: <CABkgnnW_bUGEQSeupWSmw5d8gT-jWDreCptihhvemzGU6pzuWw@mail.gmail.com>
Date: Fri, 7 Dec 2012 00:25:57 -0800
Message-ID: <016001cdd454$7be5ede0$73b1c9a0$@augustcellars.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: AQJlGhEg/qQbG44WOCBvUc6FgBaHqJbedFUQ
Content-Language: en-us
X-Mailman-Approved-At: Fri, 07 Dec 2012 00:36:20 -0800
Subject: Re: [Gen-art] GenART review of draft-schaad-pkix-rfc2875-bis-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Dec 2012 08:26:10 -0000

> -----Original Message-----
> From: Martin Thomson [mailto:martin.thomson@gmail.com]
> Sent: Thursday, December 06, 2012 5:03 PM
> To: gen-art@ietf.org; draft-schaad-pkix-rfc2875-bis.all@tools.ietf.org
> Subject: GenART review of draft-schaad-pkix-rfc2875-bis-03
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-
> ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments =
you
> may receive.
>=20
> Document: raft-schaad-pkix-rfc2875-bis-03
> Reviewer: Martin Thomson
> Review Date: 2012-12-06
> IETF LC End Date: Aaaages
> IESG Telechat date: (if known)
>=20
> Summary: Looks good to me.  Ship it.
>=20
> Nits/editorial comments:
>=20
> Section 3 does not establish a notation convention for multiplication.
>  I didn't find a specific place that this was a problem, but it seemed
> appropriate since multiplications was, in some places denoted 'n*b'
> and others as 'xy', even though multi-character identifiers are used =
in many
> places.  This does imply that a precedence override is necessary.  I =
suggest
> parentheses, since they are already used extensively.

Yes - this one hit me after I published the last version.

>=20
> Section 3: s/MAC funtion/MAC functions/
>=20
> Section 5: could use a more rigorous list construction, the =
definitions all run
> together

This is harder to do with the tools, but will be address with the RFC =
Editor

>=20
> Needs more ASN.1

I'm lost with this, what do you believe needs to be added?  The ASN.1 as =
it stands is complete.

Jim

>=20
> --Martin


From gonzalo.camarillo@ericsson.com  Fri Dec  7 01:01:46 2012
Return-Path: <gonzalo.camarillo@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97A3721F852D for <gen-art@ietfa.amsl.com>; Fri,  7 Dec 2012 01:01:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 GKUt9XXyfjYo for <gen-art@ietfa.amsl.com>; Fri,  7 Dec 2012 01:01:46 -0800 (PST)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 8A32D21F851F for <gen-art@ietf.org>; Fri,  7 Dec 2012 01:01:45 -0800 (PST)
X-AuditID: c1b4fb25-b7f926d00000661f-39-50c1b0787da7
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 33.05.26143.870B1C05; Fri,  7 Dec 2012 10:01:44 +0100 (CET)
Received: from [131.160.126.171] (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.94) with Microsoft SMTP Server id 8.3.279.1; Fri, 7 Dec 2012 10:01:44 +0100
Message-ID: <50C1B077.9050004@ericsson.com>
Date: Fri, 7 Dec 2012 11:01:43 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <50BF242F.8000709@gmail.com>	<CAE+Udoqd_GHaEF6h_HGVZP8AwkKMaVGygKc5sJjcr8X=SsTiKA@mail.gmail.com>	<50BF3199.4000109@gmail.com> <CAE+UdoqSZ_d1xTkyrTs-9rFq2OLyo0zZaxA29pqj_fo6vfk1RA@mail.gmail.com> <50BF700A.3010402@gmail.com>
In-Reply-To: <50BF700A.3010402@gmail.com>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrPLMWRmVeSWpSXmKPExsUyM+JvjW7FhoMBBs83iFu0XdzHZHHsdR+7 xdVXn1ks1uz+xmKxYsMBVgdWj7/vPzB57Jx1l91jyZKfTB4/Oveyeny5/JktgDWKyyYlNSez LLVI3y6BK2NXt0DBWZGKz68OMzcwThXoYuTkkBAwkZg6dxcrhC0mceHeerYuRi4OIYGTjBJH d1xggXDWMErcvriFHaSKV0BbYtbrrSwgNouAisTf1U+YQGw2AQuJLbfug8VFBaIkDm08CFUv KHFy5hOwuIiAsURj12mwbcwCOxkltp2NBrGFBXwk3r5eygyx7A2jxMnLKxlBEpwCmhK7Vlxm gzhPUuLt+1fMEM2aEq3bf7ND2PIS29/OAYsLAR23/FkLywRGoVlIds9C0jILScsCRuZVjOy5 iZk56eVGmxiBgX5wy2/VHYx3zokcYpTmYFES57XeusdfSCA9sSQ1OzW1ILUovqg0J7X4ECMT B6dUA6PEasVAvTnz5tqvuX2/wufdvJt26b1HssJlWvr3SBjrnc6T4y7darPMYMEfk1ONO5k3 lvxfF8sSqL/IR0/jQerrE7P6v5vn2G5fe6i6gkncZUHQ7YZFx6TkHD3Or6tkSbWYvqDrttHm Ha9ZHn+6nZD0qO+4X1/jTzHuCafTzswuZP/WILLUIEWJpTgj0VCLuag4EQD/9UVqQgIAAA==
Cc: General Area Review Team <gen-art@ietf.org>, Kevin Fleming <kevin@kpfleming.us>, Paul Kyzivat <pkyzivat@alum.mit.edu>, draft-hanes-dispatch-fax-capability.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-hanes-dispatch-fax-capability-06.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Dec 2012 09:01:46 -0000

Hi Paul,

[I am adding Paul to this thread since he was a coauthor of RFC 3840]

please, see below the exchange between Brian and Kevin regarding
draft-hanes-dispatch-fax-capability-06.txt.

This was Brian's original comment:

> Minor issue:
> ------------
> 
>    ... A UA
>    preferring the reception of fax calls MUST include the "sip.fax"
>    media feature tag in the Contact header field of REGISTER messages.
>    To confirm the registration of this preference, a SIP [RFC3261]
>    Registrar MUST then include this tag in the Contact header field of
>    its 200 OK response.
> 
> If the Registrar does not do this (e.g. because it hasn't been updated
> to support the new tag), what does the UA do when it receives the
> 200 OK response that doesn't include the tag?

Paul, can you share your views on this issue?

Thanks,

Gonzalo


On 05/12/2012 6:02 PM, Brian E Carpenter wrote:
> On 05/12/2012 14:12, Kevin Fleming wrote:
>> I suppose it could choose to unregister and re-register in some other way
>> in order to achieve its goals of receiving FAX calls, if it was configured
>> with enough network information to do so.
>>
>> Now that I think about it some more, is a registrar even allowed to return
>> a Contact header that differs from the one the UA supplied in its REGISTER
>> request? I suspect this is *not* allowed, and so if the registrar supports
>> Caller-Pref but the specific tag(s) in question fail some sort of
>> validation process, its only recourse would be to fail the REGISTER request
>> with a suitable error response.
> 
> If that's the standard behaviour, it would of course answer my question.
> 
>    Brian
> 
>>
>>
>> On Wed, Dec 5, 2012 at 6:35 AM, Brian E Carpenter <
>> brian.e.carpenter@gmail.com> wrote:
>>
>>> On 05/12/2012 11:01, Kevin Fleming wrote:
>>>> The language in RFC 3840 doesn't appear to contemplate the situation
>>> you've
>>>> proposed. In its world, registrars can either support prefs (and will
>>>> accept "Require: pref") or they don't, and they don't have knowledge of
>>>> which feature tags are registered with IANA and which are not. Of course,
>>>> they *coud* attempt to validate the tags expressed by the UA, but I don't
>>>> see an explicit way for the registrar to indicate that the UA included
>>>> disallowed tags in its request.
>>> Understood, but in that case I don't see what good the confirmation
>>> of the tag from the registrar to the UA achieves - the UA is not going
>>> to be able to do anything with it (except maybe log whether it was
>>> received).
>>>
>>>     Brian
>>>
>>


From kevin@kpfleming.us  Fri Dec  7 03:22:38 2012
Return-Path: <kevin@kpfleming.us>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24DD521F8878 for <gen-art@ietfa.amsl.com>; Fri,  7 Dec 2012 03:22:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 VLb5nOpTEFaZ for <gen-art@ietfa.amsl.com>; Fri,  7 Dec 2012 03:22:37 -0800 (PST)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 12F3B21F867A for <gen-art@ietf.org>; Fri,  7 Dec 2012 03:22:35 -0800 (PST)
Received: by mail-lb0-f172.google.com with SMTP id y2so362237lbk.31 for <gen-art@ietf.org>; Fri, 07 Dec 2012 03:22:35 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=7ZJODaaJztRnZ7DuESNNi0VqsJvvzil+LXUkcSWt5So=; b=m+qlvtGFLrE3KgziY/GXH6VJ34nZUNQt0YjwGw9Y9jQ1v7wKKVOGDtYfTVCpfu22gz kIWSR+5yibInAWGu5AzLB4hV3ubclewCjeE1Najuq71Yph6ESyGpqEwslJ7jRhgTvEZt 7ERY9o7bkCZxD1OB+UW2gvB1ywfNOisFZYhykOfNxqQMgA8hpkkvMjnbN0XcKqdq6oOm gcFhvqWgfa/26qN5Sy1RnPb9AzqSDMlittHkc948+qKqvYOV1qbrg1n7QLi8TsSC0xJg +JLkFAPC9dfI0/CK2zv84E0oB1k63N6FVVOTYTZ3EbHHpZY1ygmk+IRlZdVDDBG7PhSX AnGA==
MIME-Version: 1.0
Received: by 10.112.29.104 with SMTP id j8mr2441421lbh.0.1354879355031; Fri, 07 Dec 2012 03:22:35 -0800 (PST)
Received: by 10.114.18.144 with HTTP; Fri, 7 Dec 2012 03:22:34 -0800 (PST)
In-Reply-To: <50C1B077.9050004@ericsson.com>
References: <50BF242F.8000709@gmail.com> <CAE+Udoqd_GHaEF6h_HGVZP8AwkKMaVGygKc5sJjcr8X=SsTiKA@mail.gmail.com> <50BF3199.4000109@gmail.com> <CAE+UdoqSZ_d1xTkyrTs-9rFq2OLyo0zZaxA29pqj_fo6vfk1RA@mail.gmail.com> <50BF700A.3010402@gmail.com> <50C1B077.9050004@ericsson.com>
Date: Fri, 7 Dec 2012 06:22:34 -0500
Message-ID: <CAE+UdoqU1tHnfa0SMqu6XWGJY8X9rqrQ0P+mACNNZ5TU+DPaHw@mail.gmail.com>
From: Kevin Fleming <kevin@kpfleming.us>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Content-Type: multipart/alternative; boundary=f46d04016a31ab91e504d0416e91
X-Gm-Message-State: ALoCoQlUnoekPA5YD2RvqOkzfns+o81GZW5BFbCa2FvMFDVu8p7PFkEVQrT6IcZ+OruSxcGCAphs
Cc: General Area Review Team <gen-art@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>, draft-hanes-dispatch-fax-capability.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-hanes-dispatch-fax-capability-06.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Dec 2012 11:22:38 -0000

--f46d04016a31ab91e504d0416e91
Content-Type: text/plain; charset=UTF-8

Paul already answered this question to Brian's satisfaction yesterday.


On Fri, Dec 7, 2012 at 4:01 AM, Gonzalo Camarillo <
Gonzalo.Camarillo@ericsson.com> wrote:

> Hi Paul,
>
> [I am adding Paul to this thread since he was a coauthor of RFC 3840]
>
> please, see below the exchange between Brian and Kevin regarding
> draft-hanes-dispatch-fax-capability-06.txt.
>
> This was Brian's original comment:
>
> > Minor issue:
> > ------------
> >
> >    ... A UA
> >    preferring the reception of fax calls MUST include the "sip.fax"
> >    media feature tag in the Contact header field of REGISTER messages.
> >    To confirm the registration of this preference, a SIP [RFC3261]
> >    Registrar MUST then include this tag in the Contact header field of
> >    its 200 OK response.
> >
> > If the Registrar does not do this (e.g. because it hasn't been updated
> > to support the new tag), what does the UA do when it receives the
> > 200 OK response that doesn't include the tag?
>
> Paul, can you share your views on this issue?
>
> Thanks,
>
> Gonzalo
>
>
> On 05/12/2012 6:02 PM, Brian E Carpenter wrote:
> > On 05/12/2012 14:12, Kevin Fleming wrote:
> >> I suppose it could choose to unregister and re-register in some other
> way
> >> in order to achieve its goals of receiving FAX calls, if it was
> configured
> >> with enough network information to do so.
> >>
> >> Now that I think about it some more, is a registrar even allowed to
> return
> >> a Contact header that differs from the one the UA supplied in its
> REGISTER
> >> request? I suspect this is *not* allowed, and so if the registrar
> supports
> >> Caller-Pref but the specific tag(s) in question fail some sort of
> >> validation process, its only recourse would be to fail the REGISTER
> request
> >> with a suitable error response.
> >
> > If that's the standard behaviour, it would of course answer my question.
> >
> >    Brian
> >
> >>
> >>
> >> On Wed, Dec 5, 2012 at 6:35 AM, Brian E Carpenter <
> >> brian.e.carpenter@gmail.com> wrote:
> >>
> >>> On 05/12/2012 11:01, Kevin Fleming wrote:
> >>>> The language in RFC 3840 doesn't appear to contemplate the situation
> >>> you've
> >>>> proposed. In its world, registrars can either support prefs (and will
> >>>> accept "Require: pref") or they don't, and they don't have knowledge
> of
> >>>> which feature tags are registered with IANA and which are not. Of
> course,
> >>>> they *coud* attempt to validate the tags expressed by the UA, but I
> don't
> >>>> see an explicit way for the registrar to indicate that the UA included
> >>>> disallowed tags in its request.
> >>> Understood, but in that case I don't see what good the confirmation
> >>> of the tag from the registrar to the UA achieves - the UA is not going
> >>> to be able to do anything with it (except maybe log whether it was
> >>> received).
> >>>
> >>>     Brian
> >>>
> >>
>
>

--f46d04016a31ab91e504d0416e91
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Paul already answered this question to Brian&#39;s satisfaction yesterday.<=
div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Fri, Dec 7,=
 2012 at 4:01 AM, Gonzalo Camarillo <span dir=3D"ltr">&lt;<a href=3D"mailto=
:Gonzalo.Camarillo@ericsson.com" target=3D"_blank">Gonzalo.Camarillo@ericss=
on.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi Paul,<br>
<br>
[I am adding Paul to this thread since he was a coauthor of RFC 3840]<br>
<br>
please, see below the exchange between Brian and Kevin regarding<br>
draft-hanes-dispatch-fax-capability-06.txt.<br>
<br>
This was Brian&#39;s original comment:<br>
<br>
&gt; Minor issue:<br>
&gt; ------------<br>
&gt;<br>
&gt; =C2=A0 =C2=A0... A UA<br>
&gt; =C2=A0 =C2=A0preferring the reception of fax calls MUST include the &q=
uot;sip.fax&quot;<br>
&gt; =C2=A0 =C2=A0media feature tag in the Contact header field of REGISTER=
 messages.<br>
&gt; =C2=A0 =C2=A0To confirm the registration of this preference, a SIP [RF=
C3261]<br>
&gt; =C2=A0 =C2=A0Registrar MUST then include this tag in the Contact heade=
r field of<br>
&gt; =C2=A0 =C2=A0its 200 OK response.<br>
&gt;<br>
&gt; If the Registrar does not do this (e.g. because it hasn&#39;t been upd=
ated<br>
&gt; to support the new tag), what does the UA do when it receives the<br>
&gt; 200 OK response that doesn&#39;t include the tag?<br>
<br>
Paul, can you share your views on this issue?<br>
<br>
Thanks,<br>
<br>
Gonzalo<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
On 05/12/2012 6:02 PM, Brian E Carpenter wrote:<br>
&gt; On 05/12/2012 14:12, Kevin Fleming wrote:<br>
&gt;&gt; I suppose it could choose to unregister and re-register in some ot=
her way<br>
&gt;&gt; in order to achieve its goals of receiving FAX calls, if it was co=
nfigured<br>
&gt;&gt; with enough network information to do so.<br>
&gt;&gt;<br>
&gt;&gt; Now that I think about it some more, is a registrar even allowed t=
o return<br>
&gt;&gt; a Contact header that differs from the one the UA supplied in its =
REGISTER<br>
&gt;&gt; request? I suspect this is *not* allowed, and so if the registrar =
supports<br>
&gt;&gt; Caller-Pref but the specific tag(s) in question fail some sort of<=
br>
&gt;&gt; validation process, its only recourse would be to fail the REGISTE=
R request<br>
&gt;&gt; with a suitable error response.<br>
&gt;<br>
&gt; If that&#39;s the standard behaviour, it would of course answer my que=
stion.<br>
&gt;<br>
&gt; =C2=A0 =C2=A0Brian<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; On Wed, Dec 5, 2012 at 6:35 AM, Brian E Carpenter &lt;<br>
&gt;&gt; <a href=3D"mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@g=
mail.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt;&gt; On 05/12/2012 11:01, Kevin Fleming wrote:<br>
&gt;&gt;&gt;&gt; The language in RFC 3840 doesn&#39;t appear to contemplate=
 the situation<br>
&gt;&gt;&gt; you&#39;ve<br>
&gt;&gt;&gt;&gt; proposed. In its world, registrars can either support pref=
s (and will<br>
&gt;&gt;&gt;&gt; accept &quot;Require: pref&quot;) or they don&#39;t, and t=
hey don&#39;t have knowledge of<br>
&gt;&gt;&gt;&gt; which feature tags are registered with IANA and which are =
not. Of course,<br>
&gt;&gt;&gt;&gt; they *coud* attempt to validate the tags expressed by the =
UA, but I don&#39;t<br>
&gt;&gt;&gt;&gt; see an explicit way for the registrar to indicate that the=
 UA included<br>
&gt;&gt;&gt;&gt; disallowed tags in its request.<br>
&gt;&gt;&gt; Understood, but in that case I don&#39;t see what good the con=
firmation<br>
&gt;&gt;&gt; of the tag from the registrar to the UA achieves - the UA is n=
ot going<br>
&gt;&gt;&gt; to be able to do anything with it (except maybe log whether it=
 was<br>
&gt;&gt;&gt; received).<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; =C2=A0 =C2=A0 Brian<br>
&gt;&gt;&gt;<br>
&gt;&gt;<br>
<br>
</div></div></blockquote></div><br></div>

--f46d04016a31ab91e504d0416e91--

From brian.e.carpenter@gmail.com  Fri Dec  7 05:44:05 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D078F21F8965 for <gen-art@ietfa.amsl.com>; Fri,  7 Dec 2012 05:44:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.665
X-Spam-Level: 
X-Spam-Status: No, score=-101.665 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 f0mdZiYU007Z for <gen-art@ietfa.amsl.com>; Fri,  7 Dec 2012 05:44:05 -0800 (PST)
Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com [209.85.212.174]) by ietfa.amsl.com (Postfix) with ESMTP id A723421F893E for <gen-art@ietf.org>; Fri,  7 Dec 2012 05:44:04 -0800 (PST)
Received: by mail-wi0-f174.google.com with SMTP id hm9so1371555wib.13 for <gen-art@ietf.org>; Fri, 07 Dec 2012 05:44:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=FyEuHYud49WD5rpQAdwPaRVxu/g8a9tIMktlWh9CqbI=; b=x3EyYXglbZQgeJG++b5DzL01KouvbHLT9aHl83Xi72cNokf6LMHNPeLa3TpBAb182A bXRppbk/fJu6Bg/DnNU2xQZFCBNh1afDXhpTuvBqAbps2KOjYJbLois1anxyouXAf5RV f6QaD5IFAnJBVpFWnOVDOJxdvMvFXwljjtv5WjSMb+ooTqGtb5tL6j59DdKb/d9ztCkx lWPZNow8VajCpohBrMB6+O/98lZGaTLL1U8CXRwXc93Tg1B0Ao9G4kE5UhGiiksHQJMD Fh/Yg7HGuh0nJm/70hL0nJAt+bxkupGhmCDM1PfhwTAjDREBEP/kGkulFZ/tJK8WPTgz n/5g==
Received: by 10.216.88.5 with SMTP id z5mr2100874wee.140.1354887843855; Fri, 07 Dec 2012 05:44:03 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-219-171.as13285.net. [2.102.219.171]) by mx.google.com with ESMTPS id i2sm27252216wiw.3.2012.12.07.05.44.01 (version=SSLv3 cipher=OTHER); Fri, 07 Dec 2012 05:44:03 -0800 (PST)
Message-ID: <50C1F2B0.2080903@gmail.com>
Date: Fri, 07 Dec 2012 13:44:16 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Kevin Fleming <kevin@kpfleming.us>
References: <50BF242F.8000709@gmail.com>	<CAE+Udoqd_GHaEF6h_HGVZP8AwkKMaVGygKc5sJjcr8X=SsTiKA@mail.gmail.com>	<50BF3199.4000109@gmail.com>	<CAE+UdoqSZ_d1xTkyrTs-9rFq2OLyo0zZaxA29pqj_fo6vfk1RA@mail.gmail.com>	<50BF700A.3010402@gmail.com>	<50C1B077.9050004@ericsson.com> <CAE+UdoqU1tHnfa0SMqu6XWGJY8X9rqrQ0P+mACNNZ5TU+DPaHw@mail.gmail.com>
In-Reply-To: <CAE+UdoqU1tHnfa0SMqu6XWGJY8X9rqrQ0P+mACNNZ5TU+DPaHw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: General Area Review Team <gen-art@ietf.org>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, draft-hanes-dispatch-fax-capability.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-hanes-dispatch-fax-capability-06.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Dec 2012 13:44:05 -0000

Kevin,

Actually it looks to me as if this error case is underspecified in
RFC 3840, which says:

   The REGISTER request MAY contain a Require header field with the
   value "pref" if the client wants to be sure that the registrar
   understands the extensions defined in this specification.  This means
   that the registrar will store the feature parameters, and make them
   available to elements accessing the location service within the
   domain.  In the absence of the Require header field, a registrar that
   does not understand this extension will simply ignore the Contact
   header field parameters.

However, I can't see any description of what happens in the failure
case (Require="pref" but the registrar does not understand). Maybe
it's supposed to be a 400 response, but I'm not sure that follows
inevitably from RFC 3840 and 3261.

That isn't a problem that the current draft can fix. When the draft
appears on the IESG agenda, I will update my review accordingly.

Thanks
   Brian Carpenter

On 07/12/2012 11:22, Kevin Fleming wrote:
> Paul already answered this question to Brian's satisfaction yesterday.
> 
> 
> On Fri, Dec 7, 2012 at 4:01 AM, Gonzalo Camarillo <
> Gonzalo.Camarillo@ericsson.com> wrote:
> 
>> Hi Paul,
>>
>> [I am adding Paul to this thread since he was a coauthor of RFC 3840]
>>
>> please, see below the exchange between Brian and Kevin regarding
>> draft-hanes-dispatch-fax-capability-06.txt.
>>
>> This was Brian's original comment:
>>
>>> Minor issue:
>>> ------------
>>>
>>>    ... A UA
>>>    preferring the reception of fax calls MUST include the "sip.fax"
>>>    media feature tag in the Contact header field of REGISTER messages.
>>>    To confirm the registration of this preference, a SIP [RFC3261]
>>>    Registrar MUST then include this tag in the Contact header field of
>>>    its 200 OK response.
>>>
>>> If the Registrar does not do this (e.g. because it hasn't been updated
>>> to support the new tag), what does the UA do when it receives the
>>> 200 OK response that doesn't include the tag?
>> Paul, can you share your views on this issue?
>>
>> Thanks,
>>
>> Gonzalo
>>
>>
>> On 05/12/2012 6:02 PM, Brian E Carpenter wrote:
>>> On 05/12/2012 14:12, Kevin Fleming wrote:
>>>> I suppose it could choose to unregister and re-register in some other
>> way
>>>> in order to achieve its goals of receiving FAX calls, if it was
>> configured
>>>> with enough network information to do so.
>>>>
>>>> Now that I think about it some more, is a registrar even allowed to
>> return
>>>> a Contact header that differs from the one the UA supplied in its
>> REGISTER
>>>> request? I suspect this is *not* allowed, and so if the registrar
>> supports
>>>> Caller-Pref but the specific tag(s) in question fail some sort of
>>>> validation process, its only recourse would be to fail the REGISTER
>> request
>>>> with a suitable error response.
>>> If that's the standard behaviour, it would of course answer my question.
>>>
>>>    Brian
>>>
>>>>
>>>> On Wed, Dec 5, 2012 at 6:35 AM, Brian E Carpenter <
>>>> brian.e.carpenter@gmail.com> wrote:
>>>>
>>>>> On 05/12/2012 11:01, Kevin Fleming wrote:
>>>>>> The language in RFC 3840 doesn't appear to contemplate the situation
>>>>> you've
>>>>>> proposed. In its world, registrars can either support prefs (and will
>>>>>> accept "Require: pref") or they don't, and they don't have knowledge
>> of
>>>>>> which feature tags are registered with IANA and which are not. Of
>> course,
>>>>>> they *coud* attempt to validate the tags expressed by the UA, but I
>> don't
>>>>>> see an explicit way for the registrar to indicate that the UA included
>>>>>> disallowed tags in its request.
>>>>> Understood, but in that case I don't see what good the confirmation
>>>>> of the tag from the registrar to the UA achieves - the UA is not going
>>>>> to be able to do anything with it (except maybe log whether it was
>>>>> received).
>>>>>
>>>>>     Brian
>>>>>
>>
> 

From brian.e.carpenter@gmail.com  Fri Dec  7 05:47:10 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E87421F8532 for <gen-art@ietfa.amsl.com>; Fri,  7 Dec 2012 05:47:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.366
X-Spam-Level: 
X-Spam-Status: No, score=-101.366 tagged_above=-999 required=5 tests=[AWL=-0.275, BAYES_00=-2.599, J_CHICKENPOX_74=0.6, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 UFzQHg7Aqmip for <gen-art@ietfa.amsl.com>; Fri,  7 Dec 2012 05:47:09 -0800 (PST)
Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com [209.85.212.174]) by ietfa.amsl.com (Postfix) with ESMTP id 5377021F8530 for <gen-art@ietf.org>; Fri,  7 Dec 2012 05:47:09 -0800 (PST)
Received: by mail-wi0-f174.google.com with SMTP id hm9so1374055wib.13 for <gen-art@ietf.org>; Fri, 07 Dec 2012 05:47:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=f8Vp+ddBMr0rfuR8kyPm/VJZZSgmBSGjbG+TUvYMDOk=; b=ABf8hi2XIlYR5l3Culv3xUSVD8LL+SnTfok6nTI+tfq3W8otAFC11YZ6iNgkFQWUuy X29gOhkR6DhR/29k0ZA3Mia1wk1SoEcAL0xf2vu0NlcmJ+BaWARFhjlEFV+giwHqj0nx S8MFzlmr0UC92OK2K6bdat/EcM7ZhyDCAuqyBv9K+ulLO7ev6/zsfjS6uURliSpTF/P0 4v5BXYHDcGG4a/SP9rwP7w4BJQX/Rr1JPcE7qPUcVLYWM+vqsT4lAN+cfCwx1KnDAlG7 ZzgHscsAiyKYRII77C32oeu6QB5C/JoRRN6LRq9+ph03x6v6oDYc8wYY3tcfRHI0A5Zf lJwA==
Received: by 10.216.219.201 with SMTP id m51mr2243237wep.15.1354888028491; Fri, 07 Dec 2012 05:47:08 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-219-171.as13285.net. [2.102.219.171]) by mx.google.com with ESMTPS id h19sm21260643wiv.7.2012.12.07.05.47.06 (version=SSLv3 cipher=OTHER); Fri, 07 Dec 2012 05:47:07 -0800 (PST)
Message-ID: <50C1F369.3090805@gmail.com>
Date: Fri, 07 Dec 2012 13:47:21 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: David Hanes <dhanes@cisco.com>
References: <50BF242F.8000709@gmail.com> <CAE+Udoqd_GHaEF6h_HGVZP8AwkKMaVGygKc5sJjcr8X=SsTiKA@mail.gmail.com> <50BF3199.4000109@gmail.com> <CAE+UdoqSZ_d1xTkyrTs-9rFq2OLyo0zZaxA29pqj_fo6vfk1RA@mail.gmail.com> <50BF700A.3010402@gmail.com> <50C1B077.9050004@ericsson.com> <CAE+UdoqU1tHnfa0SMqu6XWGJY8X9rqrQ0P+mACNNZ5TU+DPaHw@mail.gmail.com> <A7FEAAB1-B211-4896-B328-59B30AC39F61@cisco.com>
In-Reply-To: <A7FEAAB1-B211-4896-B328-59B30AC39F61@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: General Area Review Team <gen-art@ietf.org>, Kevin Fleming <kevin@kpfleming.us>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, draft-hanes-dispatch-fax-capability.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-hanes-dispatch-fax-capability-06.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Dec 2012 13:47:10 -0000

Oops, that crossed with my note.

In that case maybe a small clarification *is* needed in the draft.

Regards
   Brian Carpenter

On 07/12/2012 13:19, David Hanes wrote:
> Hi Kevin,
> 
> Actually, I had just copied the draft authors on that thread and Brian was not on it. Below is Paul's response for everyone's clarification.
> 
> Thanks,
> David
> 
> 
> 
> 
> 
> On 12/6/12 12:17 PM, David Hanes wrote:
>> Hi Paul,
>>
>> I am hoping you can lend us a hand in answering a comment from Brian
>> Carpenter (attached), who is the Gen-ART reviewer for our draft. Being
>> an author of 3840 and instrumental in helping us revise our draft, you
>> seem to be the best person to comment here.
>>
>> In the thread below, Kevin proposes the question, " is a registrar even
>> allowed to return a Contact header that differs from the one the UA
>> supplied in its REGISTER request?". I think that the answer to this
>> question determines how we progress forward in addressing Brian's
>> comment. We would appreciate your thoughts and guidance on this when you
>> have a moment.
> 
> I'll try.
> 
> RFC 3261 doesn't say anything about the registrar saving or returning contact parameters, other than the expiration time and q-value.
> 
> RFC 3840 does that. *If* the registrar supports the "pref" option, then it is required to save the feature parameters (aka feature tags or capabilities), and to return them in queries. Returning them all is MUST strength, so it doesn't have the option of selectively removing some. Things are written so that the registrar need not be aware of *particular* feature tags to support them. Newly defined ones (such as being defined here) are recognized syntactically (via the leading "+").
> 
> If the registrar doesn't support "pref" it may or may not save and return Contact header field parameters. (It is neither required to do so nor forbidden from doing so.) In this case, I suppose it also *could* selectively prune (or add) parameters.
> 
> Also, the registrar has considerable latitude in its operation. As specified in 3261, it stores the registration bindings in an abstract location service. It is permissible for there to be other (unspecified) ways for the location service to be populated and manipulated. (A common case would be for the location service to be pre-populated with some default contacts.) Because of this, one could justify removing parameters from a binding by saying it might have been done by some external agent operating on the location service.
> 
> In general, callee capabilities (feature tags) and caller preference support by the proxy associated with the registrar are optional features, and you shouldn't be too surprised if they aren't supported.
> 
> In the case of the fax capability, I think you will probably want to include it in the registration *without* Require:pref. If it doesn't show up in the response to the REGISTER then you know it wasn't saved. If it did show up, you still don't know if callerprefs pertaining to it will be supported or not. What should you do? Nothing. You may get some non-fax calls and those will then fail. Maybe they will then be forked to another contact that succeeds, or not. That is not the concern of the fax device.
> 
> 	Thanks,
> 	Paul
> 
>> Thanks,
>> David
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> On Dec 7, 2012, at 6:22 AM, Kevin Fleming wrote:
> 
>> Paul already answered this question to Brian's satisfaction yesterday.
>>
>>
>> On Fri, Dec 7, 2012 at 4:01 AM, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> wrote:
>> Hi Paul,
>>
>> [I am adding Paul to this thread since he was a coauthor of RFC 3840]
>>
>> please, see below the exchange between Brian and Kevin regarding
>> draft-hanes-dispatch-fax-capability-06.txt.
>>
>> This was Brian's original comment:
>>
>>> Minor issue:
>>> ------------
>>>
>>>    ... A UA
>>>    preferring the reception of fax calls MUST include the "sip.fax"
>>>    media feature tag in the Contact header field of REGISTER messages.
>>>    To confirm the registration of this preference, a SIP [RFC3261]
>>>    Registrar MUST then include this tag in the Contact header field of
>>>    its 200 OK response.
>>>
>>> If the Registrar does not do this (e.g. because it hasn't been updated
>>> to support the new tag), what does the UA do when it receives the
>>> 200 OK response that doesn't include the tag?
>> Paul, can you share your views on this issue?
>>
>> Thanks,
>>
>> Gonzalo
>>
>>
>>
>>
> 
> 

From dhanes@cisco.com  Fri Dec  7 05:20:00 2012
Return-Path: <dhanes@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BB4D21F867A for <gen-art@ietfa.amsl.com>; Fri,  7 Dec 2012 05:20:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.998
X-Spam-Level: 
X-Spam-Status: No, score=-9.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_74=0.6, RCVD_IN_DNSWL_HI=-8]
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 XRJ1NGw5cFOm for <gen-art@ietfa.amsl.com>; Fri,  7 Dec 2012 05:19:59 -0800 (PST)
Received: from av-tac-rtp.cisco.com (av-tac-rtp.cisco.com [64.102.19.209]) by ietfa.amsl.com (Postfix) with ESMTP id 6305721F84F0 for <gen-art@ietf.org>; Fri,  7 Dec 2012 05:19:59 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id qB7DJn1U025356; Fri, 7 Dec 2012 08:19:49 -0500 (EST)
Received: from rtp-dhanes-8913.cisco.com (rtp-dhanes-8913.cisco.com [10.117.39.196]) by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id qB7DJgrp021005;  Fri, 7 Dec 2012 08:19:43 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: multipart/alternative; boundary=Apple-Mail-42-769543717
From: David Hanes <dhanes@cisco.com>
In-Reply-To: <CAE+UdoqU1tHnfa0SMqu6XWGJY8X9rqrQ0P+mACNNZ5TU+DPaHw@mail.gmail.com>
Date: Fri, 7 Dec 2012 08:19:41 -0500
Message-Id: <A7FEAAB1-B211-4896-B328-59B30AC39F61@cisco.com>
References: <50BF242F.8000709@gmail.com> <CAE+Udoqd_GHaEF6h_HGVZP8AwkKMaVGygKc5sJjcr8X=SsTiKA@mail.gmail.com> <50BF3199.4000109@gmail.com> <CAE+UdoqSZ_d1xTkyrTs-9rFq2OLyo0zZaxA29pqj_fo6vfk1RA@mail.gmail.com> <50BF700A.3010402@gmail.com> <50C1B077.9050004@ericsson.com> <CAE+UdoqU1tHnfa0SMqu6XWGJY8X9rqrQ0P+mACNNZ5TU+DPaHw@mail.gmail.com>
To: Kevin Fleming <kevin@kpfleming.us>
X-Mailer: Apple Mail (2.1085)
X-Mailman-Approved-At: Fri, 07 Dec 2012 05:48:37 -0800
Cc: General Area Review Team <gen-art@ietf.org>, draft-hanes-dispatch-fax-capability.all@tools.ietf.org, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [Gen-art] Gen-ART LC review of draft-hanes-dispatch-fax-capability-06.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Dec 2012 13:20:00 -0000

--Apple-Mail-42-769543717
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi Kevin,

Actually, I had just copied the draft authors on that thread and Brian =
was not on it. Below is Paul's response for everyone's clarification.

Thanks,
David





On 12/6/12 12:17 PM, David Hanes wrote:
> Hi Paul,
>=20
> I am hoping you can lend us a hand in answering a comment from Brian
> Carpenter (attached), who is the Gen-ART reviewer for our draft. Being
> an author of 3840 and instrumental in helping us revise our draft, you
> seem to be the best person to comment here.
>=20
> In the thread below, Kevin proposes the question, " is a registrar =
even
> allowed to return a Contact header that differs from the one the UA
> supplied in its REGISTER request?". I think that the answer to this
> question determines how we progress forward in addressing Brian's
> comment. We would appreciate your thoughts and guidance on this when =
you
> have a moment.

I'll try.

RFC 3261 doesn't say anything about the registrar saving or returning =
contact parameters, other than the expiration time and q-value.

RFC 3840 does that. *If* the registrar supports the "pref" option, then =
it is required to save the feature parameters (aka feature tags or =
capabilities), and to return them in queries. Returning them all is MUST =
strength, so it doesn't have the option of selectively removing some. =
Things are written so that the registrar need not be aware of =
*particular* feature tags to support them. Newly defined ones (such as =
being defined here) are recognized syntactically (via the leading "+").

If the registrar doesn't support "pref" it may or may not save and =
return Contact header field parameters. (It is neither required to do so =
nor forbidden from doing so.) In this case, I suppose it also *could* =
selectively prune (or add) parameters.

Also, the registrar has considerable latitude in its operation. As =
specified in 3261, it stores the registration bindings in an abstract =
location service. It is permissible for there to be other (unspecified) =
ways for the location service to be populated and manipulated. (A common =
case would be for the location service to be pre-populated with some =
default contacts.) Because of this, one could justify removing =
parameters from a binding by saying it might have been done by some =
external agent operating on the location service.

In general, callee capabilities (feature tags) and caller preference =
support by the proxy associated with the registrar are optional =
features, and you shouldn't be too surprised if they aren't supported.

In the case of the fax capability, I think you will probably want to =
include it in the registration *without* Require:pref. If it doesn't =
show up in the response to the REGISTER then you know it wasn't saved. =
If it did show up, you still don't know if callerprefs pertaining to it =
will be supported or not. What should you do? Nothing. You may get some =
non-fax calls and those will then fail. Maybe they will then be forked =
to another contact that succeeds, or not. That is not the concern of the =
fax device.

	Thanks,
	Paul

> Thanks,
> David










On Dec 7, 2012, at 6:22 AM, Kevin Fleming wrote:

> Paul already answered this question to Brian's satisfaction yesterday.
>=20
>=20
> On Fri, Dec 7, 2012 at 4:01 AM, Gonzalo Camarillo =
<Gonzalo.Camarillo@ericsson.com> wrote:
> Hi Paul,
>=20
> [I am adding Paul to this thread since he was a coauthor of RFC 3840]
>=20
> please, see below the exchange between Brian and Kevin regarding
> draft-hanes-dispatch-fax-capability-06.txt.
>=20
> This was Brian's original comment:
>=20
> > Minor issue:
> > ------------
> >
> >    ... A UA
> >    preferring the reception of fax calls MUST include the "sip.fax"
> >    media feature tag in the Contact header field of REGISTER =
messages.
> >    To confirm the registration of this preference, a SIP [RFC3261]
> >    Registrar MUST then include this tag in the Contact header field =
of
> >    its 200 OK response.
> >
> > If the Registrar does not do this (e.g. because it hasn't been =
updated
> > to support the new tag), what does the UA do when it receives the
> > 200 OK response that doesn't include the tag?
>=20
> Paul, can you share your views on this issue?
>=20
> Thanks,
>=20
> Gonzalo
>=20
>=20
>=20
>=20


--Apple-Mail-42-769543717
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi =
Kevin,<div><br></div><div>Actually, I had just copied the draft authors =
on that thread and Brian was not on it. Below is Paul's response for =
everyone's =
clarification.</div><div><br></div><div>Thanks,</div><div>David</div><div>=
<br></div><div><br></div><div><br></div><div><br></div><div><br></div><div=
>On 12/6/12 12:17 PM, David Hanes wrote:<br><blockquote type=3D"cite">Hi =
Paul,<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I am hoping you =
can lend us a hand in answering a comment from =
Brian<br></blockquote><blockquote type=3D"cite">Carpenter (attached), =
who is the Gen-ART reviewer for our draft. =
Being<br></blockquote><blockquote type=3D"cite">an author of 3840 and =
instrumental in helping us revise our draft, =
you<br></blockquote><blockquote type=3D"cite">seem to be the best person =
to comment here.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">In the thread =
below, Kevin proposes the question, " is a registrar =
even<br></blockquote><blockquote type=3D"cite">allowed to return a =
Contact header that differs from the one the =
UA<br></blockquote><blockquote type=3D"cite">supplied in its REGISTER =
request?". I think that the answer to this<br></blockquote><blockquote =
type=3D"cite">question determines how we progress forward in addressing =
Brian's<br></blockquote><blockquote type=3D"cite">comment. We would =
appreciate your thoughts and guidance on this when =
you<br></blockquote><blockquote type=3D"cite">have a =
moment.<br></blockquote><br>I'll try.<br><br>RFC 3261 doesn't say =
anything about the registrar saving or returning contact parameters, =
other than the expiration time and q-value.<br><br>RFC 3840 does that. =
*If* the registrar supports the "pref" option, then it is required to =
save the feature parameters (aka feature tags or capabilities), and to =
return them in queries. Returning them all is MUST strength, so it =
doesn't have the option of selectively removing some. Things are written =
so that the registrar need not be aware of *particular* feature tags to =
support them. Newly defined ones (such as being defined here) are =
recognized syntactically (via the leading "+").<br><br>If the registrar =
doesn't support "pref" it may or may not save and return Contact header =
field parameters. (It is neither required to do so nor forbidden from =
doing so.) In this case, I suppose it also *could* selectively prune (or =
add) parameters.<br><br>Also, the registrar has considerable latitude in =
its operation. As specified in 3261, it stores the registration bindings =
in an abstract location service. It is permissible for there to be other =
(unspecified) ways for the location service to be populated and =
manipulated. (A common case would be for the location service to be =
pre-populated with some default contacts.) Because of this, one could =
justify removing parameters from a binding by saying it might have been =
done by some external agent operating on the location service.<br><br>In =
general, callee capabilities (feature tags) and caller preference =
support by the proxy associated with the registrar are optional =
features, and you shouldn't be too surprised if they aren't =
supported.<br><br>In the case of the fax capability, I think you will =
probably want to include it in the registration *without* Require:pref. =
If it doesn't show up in the response to the REGISTER then you know it =
wasn't saved. If it did show up, you still don't know if callerprefs =
pertaining to it will be supported or not. What should you do? Nothing. =
You may get some non-fax calls and those will then fail. Maybe they will =
then be forked to another contact that succeeds, or not. That is not the =
concern of the fax device.<br><br><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>Thanks,<br><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
</span>Paul<br><br><blockquote =
type=3D"cite">Thanks,<br></blockquote><blockquote =
type=3D"cite">David<br></blockquote></div><div><br></div><div><br></div><d=
iv><br></div><div><br></div><div><br></div><div><br></div><div><br></div><=
div><br></div><div><br><div><div>On Dec 7, 2012, at 6:22 AM, Kevin =
Fleming wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8">Paul already answered this question to Brian's =
satisfaction yesterday.<div class=3D"gmail_extra"><br><br><div =
class=3D"gmail_quote">On Fri, Dec 7, 2012 at 4:01 AM, Gonzalo Camarillo =
<span dir=3D"ltr">&lt;<a href=3D"mailto:Gonzalo.Camarillo@ericsson.com" =
target=3D"_blank">Gonzalo.Camarillo@ericsson.com</a>&gt;</span> =
wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; =
border-left-width: 1px; border-left-color: rgb(204, 204, 204); =
border-left-style: solid; padding-left: 1ex; position: static; z-index: =
auto; ">Hi Paul,<br>
<br>
[I am adding Paul to this thread since he was a coauthor of RFC =
3840]<br>
<br>
please, see below the exchange between Brian and Kevin regarding<br>
draft-hanes-dispatch-fax-capability-06.txt.<br>
<br>
This was Brian's original comment:<br>
<br>
&gt; Minor issue:<br>
&gt; ------------<br>
&gt;<br>
&gt; &nbsp; &nbsp;... A UA<br>
&gt; &nbsp; &nbsp;preferring the reception of fax calls MUST include the =
"sip.fax"<br>
&gt; &nbsp; &nbsp;media feature tag in the Contact header field of =
REGISTER messages.<br>
&gt; &nbsp; &nbsp;To confirm the registration of this preference, a SIP =
[RFC3261]<br>
&gt; &nbsp; &nbsp;Registrar MUST then include this tag in the Contact =
header field of<br>
&gt; &nbsp; &nbsp;its 200 OK response.<br>
&gt;<br>
&gt; If the Registrar does not do this (e.g. because it hasn't been =
updated<br>
&gt; to support the new tag), what does the UA do when it receives =
the<br>
&gt; 200 OK response that doesn't include the tag?<br>
<br>
Paul, can you share your views on this issue?<br>
<br>
Thanks,<br>
<br>
Gonzalo<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br><br>
</div></div></blockquote></div><br></div>
</blockquote></div><br></div></body></html>=

--Apple-Mail-42-769543717--

From pkyzivat@alum.mit.edu  Fri Dec  7 07:59:30 2012
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 089E421F8AC5 for <gen-art@ietfa.amsl.com>; Fri,  7 Dec 2012 07:59:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.367
X-Spam-Level: 
X-Spam-Status: No, score=-0.367 tagged_above=-999 required=5 tests=[AWL=0.070,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  RDNS_NONE=0.1]
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 0SPWjkEQHBl8 for <gen-art@ietfa.amsl.com>; Fri,  7 Dec 2012 07:59:29 -0800 (PST)
Received: from qmta01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:16]) by ietfa.amsl.com (Postfix) with ESMTP id 72B0321F8AD3 for <gen-art@ietf.org>; Fri,  7 Dec 2012 07:59:27 -0800 (PST)
Received: from omta24.westchester.pa.mail.comcast.net ([76.96.62.76]) by qmta01.westchester.pa.mail.comcast.net with comcast id Ycuy1k0031ei1Bg51fzSFp; Fri, 07 Dec 2012 15:59:26 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta24.westchester.pa.mail.comcast.net with comcast id YfzR1k00D3ZTu2S3kfzR8X; Fri, 07 Dec 2012 15:59:26 +0000
Message-ID: <50C2125C.6090907@alum.mit.edu>
Date: Fri, 07 Dec 2012 10:59:24 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <50BF242F.8000709@gmail.com>	<CAE+Udoqd_GHaEF6h_HGVZP8AwkKMaVGygKc5sJjcr8X=SsTiKA@mail.gmail.com>	<50BF3199.4000109@gmail.com>	<CAE+UdoqSZ_d1xTkyrTs-9rFq2OLyo0zZaxA29pqj_fo6vfk1RA@mail.gmail.com>	<50BF700A.3010402@gmail.com>	<50C1B077.9050004@ericsson.com> <CAE+UdoqU1tHnfa0SMqu6XWGJY8X9rqrQ0P+mACNNZ5TU+DPaHw@mail.gmail.com> <50C1F2B0.2080903@gmail.com>
In-Reply-To: <50C1F2B0.2080903@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1354895966; bh=dZNaH53jzTCwPOkY73OLd4IdoiP/G004Yt3gPf+QPPQ=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=YR1xSLCbuDUdmNhvGi75aQrw6RStUSsgkV1pGGbomhTqanx2Co0GbszFRF1G5FFlW lpfdGocb2Jl2hM/+JISRXlpwSuHDef+x1zmWuAvtz3P158YDYhkjJSt7TubIoMKePB 4MNcMpBSl3HOX69YDOF+IiVEsd8F7ElvqPjoC+yOeA6JKfOkxpBs6mb+zWR7xhBsLO J01tCx9+sjsrCAmcdNujBrHui76N/eleL2UrxFxGFuys6Qf5eIOybWcwNUrLWA916r X0nEj+080IevqJfcNWEMSQl8fwYlTsi4hJbIex5mVUwVoEUHUpoR3J3yRfAsQWMHh6 6cmzJ3b0zft+g==
Cc: General Area Review Team <gen-art@ietf.org>, Kevin Fleming <kevin@kpfleming.us>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, draft-hanes-dispatch-fax-capability.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-hanes-dispatch-fax-capability-06.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Dec 2012 15:59:30 -0000

On 12/7/12 8:44 AM, Brian E Carpenter wrote:
> Kevin,
>
> Actually it looks to me as if this error case is underspecified in
> RFC 3840, which says:
>
>     The REGISTER request MAY contain a Require header field with the
>     value "pref" if the client wants to be sure that the registrar
>     understands the extensions defined in this specification.  This means
>     that the registrar will store the feature parameters, and make them
>     available to elements accessing the location service within the
>     domain.  In the absence of the Require header field, a registrar that
>     does not understand this extension will simply ignore the Contact
>     header field parameters.
>
> However, I can't see any description of what happens in the failure
> case (Require="pref" but the registrar does not understand). Maybe
> it's supposed to be a 400 response, but I'm not sure that follows
> inevitably from RFC 3840 and 3261.

RFC3261 has a specific error for this: 420 (Bad Extension).
This very standard behavior. There is no need for drafts that specify 
use of Require to spell this out.

	Thanks,
	Paul

> That isn't a problem that the current draft can fix. When the draft
> appears on the IESG agenda, I will update my review accordingly.
>
> Thanks
>     Brian Carpenter
>
> On 07/12/2012 11:22, Kevin Fleming wrote:
>> Paul already answered this question to Brian's satisfaction yesterday.
>>
>>
>> On Fri, Dec 7, 2012 at 4:01 AM, Gonzalo Camarillo <
>> Gonzalo.Camarillo@ericsson.com> wrote:
>>
>>> Hi Paul,
>>>
>>> [I am adding Paul to this thread since he was a coauthor of RFC 3840]
>>>
>>> please, see below the exchange between Brian and Kevin regarding
>>> draft-hanes-dispatch-fax-capability-06.txt.
>>>
>>> This was Brian's original comment:
>>>
>>>> Minor issue:
>>>> ------------
>>>>
>>>>     ... A UA
>>>>     preferring the reception of fax calls MUST include the "sip.fax"
>>>>     media feature tag in the Contact header field of REGISTER messages.
>>>>     To confirm the registration of this preference, a SIP [RFC3261]
>>>>     Registrar MUST then include this tag in the Contact header field of
>>>>     its 200 OK response.
>>>>
>>>> If the Registrar does not do this (e.g. because it hasn't been updated
>>>> to support the new tag), what does the UA do when it receives the
>>>> 200 OK response that doesn't include the tag?
>>> Paul, can you share your views on this issue?
>>>
>>> Thanks,
>>>
>>> Gonzalo
>>>
>>>
>>> On 05/12/2012 6:02 PM, Brian E Carpenter wrote:
>>>> On 05/12/2012 14:12, Kevin Fleming wrote:
>>>>> I suppose it could choose to unregister and re-register in some other
>>> way
>>>>> in order to achieve its goals of receiving FAX calls, if it was
>>> configured
>>>>> with enough network information to do so.
>>>>>
>>>>> Now that I think about it some more, is a registrar even allowed to
>>> return
>>>>> a Contact header that differs from the one the UA supplied in its
>>> REGISTER
>>>>> request? I suspect this is *not* allowed, and so if the registrar
>>> supports
>>>>> Caller-Pref but the specific tag(s) in question fail some sort of
>>>>> validation process, its only recourse would be to fail the REGISTER
>>> request
>>>>> with a suitable error response.
>>>> If that's the standard behaviour, it would of course answer my question.
>>>>
>>>>     Brian
>>>>
>>>>>
>>>>> On Wed, Dec 5, 2012 at 6:35 AM, Brian E Carpenter <
>>>>> brian.e.carpenter@gmail.com> wrote:
>>>>>
>>>>>> On 05/12/2012 11:01, Kevin Fleming wrote:
>>>>>>> The language in RFC 3840 doesn't appear to contemplate the situation
>>>>>> you've
>>>>>>> proposed. In its world, registrars can either support prefs (and will
>>>>>>> accept "Require: pref") or they don't, and they don't have knowledge
>>> of
>>>>>>> which feature tags are registered with IANA and which are not. Of
>>> course,
>>>>>>> they *coud* attempt to validate the tags expressed by the UA, but I
>>> don't
>>>>>>> see an explicit way for the registrar to indicate that the UA included
>>>>>>> disallowed tags in its request.
>>>>>> Understood, but in that case I don't see what good the confirmation
>>>>>> of the tag from the registrar to the UA achieves - the UA is not going
>>>>>> to be able to do anything with it (except maybe log whether it was
>>>>>> received).
>>>>>>
>>>>>>      Brian
>>>>>>
>>>
>>
>


From brian.e.carpenter@gmail.com  Fri Dec  7 08:42:19 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C68D21F8640 for <gen-art@ietfa.amsl.com>; Fri,  7 Dec 2012 08:42:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.655
X-Spam-Level: 
X-Spam-Status: No, score=-101.655 tagged_above=-999 required=5 tests=[AWL=0.036, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 FoJhTZm8wHHu for <gen-art@ietfa.amsl.com>; Fri,  7 Dec 2012 08:42:18 -0800 (PST)
Received: from mail-wg0-f46.google.com (mail-wg0-f46.google.com [74.125.82.46]) by ietfa.amsl.com (Postfix) with ESMTP id 4CD2D21F860F for <gen-art@ietf.org>; Fri,  7 Dec 2012 08:42:18 -0800 (PST)
Received: by mail-wg0-f46.google.com with SMTP id dr13so293032wgb.13 for <gen-art@ietf.org>; Fri, 07 Dec 2012 08:42:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=7iW/UTuaJFpSyeSAp18EYTVD5jyOnChPfRycoXM3JqM=; b=0CoUaoySOoc8XJL3S+RgbPjo+nGKfHhSNQzjWmG13/Acl5qOUN4pDjaoJKdBpVk2Ct 1UlITQANu6yQM2xJv+SxemAktatdoVnUtO36fmW2i9PogJN4r3Zp27wA6piiYDSiluWS rT8HGX87Tp4S/D3SsER0iXk9MMlZiHtMDdZEoCIRZcNIlkJ4PoFFl0LbDzpVBU9jeGlc 5foRDoxros6tzcHd+tkthOBFj4CSFg4ds1LLo1ZnacUellunHoLlICgkWwZfZyiYO3v8 NAV/QB3HKolzJEUxS7otm7U4ErubuMqIq4/n1oXij1oD0qYjMrcRQPb2K4/OfHedH9V6 2AMA==
Received: by 10.180.80.201 with SMTP id t9mr9671099wix.0.1354898537229; Fri, 07 Dec 2012 08:42:17 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-219-171.as13285.net. [2.102.219.171]) by mx.google.com with ESMTPS id p3sm27831659wic.8.2012.12.07.08.42.14 (version=SSLv3 cipher=OTHER); Fri, 07 Dec 2012 08:42:15 -0800 (PST)
Message-ID: <50C21C75.5070309@gmail.com>
Date: Fri, 07 Dec 2012 16:42:29 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
References: <50BF242F.8000709@gmail.com>	<CAE+Udoqd_GHaEF6h_HGVZP8AwkKMaVGygKc5sJjcr8X=SsTiKA@mail.gmail.com>	<50BF3199.4000109@gmail.com>	<CAE+UdoqSZ_d1xTkyrTs-9rFq2OLyo0zZaxA29pqj_fo6vfk1RA@mail.gmail.com>	<50BF700A.3010402@gmail.com>	<50C1B077.9050004@ericsson.com> <CAE+UdoqU1tHnfa0SMqu6XWGJY8X9rqrQ0P+mACNNZ5TU+DPaHw@mail.gmail.com> <50C1F2B0.2080903@gmail.com> <50C2125C.6090907@alum.mit.edu>
In-Reply-To: <50C2125C.6090907@alum.mit.edu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: General Area Review Team <gen-art@ietf.org>, Kevin Fleming <kevin@kpfleming.us>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, draft-hanes-dispatch-fax-capability.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-hanes-dispatch-fax-capability-06.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Dec 2012 16:42:19 -0000

> RFC3261 has a specific error for this: 420 (Bad Extension).

OK, excellent. Sorry to have gone on about this but SIP is a big
mouthful for a generalist reviewer.

Regards
   Brian Carpenter


On 07/12/2012 15:59, Paul Kyzivat wrote:
> On 12/7/12 8:44 AM, Brian E Carpenter wrote:
>> Kevin,
>>
>> Actually it looks to me as if this error case is underspecified in
>> RFC 3840, which says:
>>
>>     The REGISTER request MAY contain a Require header field with the
>>     value "pref" if the client wants to be sure that the registrar
>>     understands the extensions defined in this specification.  This means
>>     that the registrar will store the feature parameters, and make them
>>     available to elements accessing the location service within the
>>     domain.  In the absence of the Require header field, a registrar that
>>     does not understand this extension will simply ignore the Contact
>>     header field parameters.
>>
>> However, I can't see any description of what happens in the failure
>> case (Require="pref" but the registrar does not understand). Maybe
>> it's supposed to be a 400 response, but I'm not sure that follows
>> inevitably from RFC 3840 and 3261.
> 
> RFC3261 has a specific error for this: 420 (Bad Extension).
> This very standard behavior. There is no need for drafts that specify
> use of Require to spell this out.
> 
>     Thanks,
>     Paul
> 
>> That isn't a problem that the current draft can fix. When the draft
>> appears on the IESG agenda, I will update my review accordingly.
>>
>> Thanks
>>     Brian Carpenter
>>
>> On 07/12/2012 11:22, Kevin Fleming wrote:
>>> Paul already answered this question to Brian's satisfaction yesterday.
>>>
>>>
>>> On Fri, Dec 7, 2012 at 4:01 AM, Gonzalo Camarillo <
>>> Gonzalo.Camarillo@ericsson.com> wrote:
>>>
>>>> Hi Paul,
>>>>
>>>> [I am adding Paul to this thread since he was a coauthor of RFC 3840]
>>>>
>>>> please, see below the exchange between Brian and Kevin regarding
>>>> draft-hanes-dispatch-fax-capability-06.txt.
>>>>
>>>> This was Brian's original comment:
>>>>
>>>>> Minor issue:
>>>>> ------------
>>>>>
>>>>>     ... A UA
>>>>>     preferring the reception of fax calls MUST include the "sip.fax"
>>>>>     media feature tag in the Contact header field of REGISTER
>>>>> messages.
>>>>>     To confirm the registration of this preference, a SIP [RFC3261]
>>>>>     Registrar MUST then include this tag in the Contact header
>>>>> field of
>>>>>     its 200 OK response.
>>>>>
>>>>> If the Registrar does not do this (e.g. because it hasn't been updated
>>>>> to support the new tag), what does the UA do when it receives the
>>>>> 200 OK response that doesn't include the tag?
>>>> Paul, can you share your views on this issue?
>>>>
>>>> Thanks,
>>>>
>>>> Gonzalo
>>>>
>>>>
>>>> On 05/12/2012 6:02 PM, Brian E Carpenter wrote:
>>>>> On 05/12/2012 14:12, Kevin Fleming wrote:
>>>>>> I suppose it could choose to unregister and re-register in some other
>>>> way
>>>>>> in order to achieve its goals of receiving FAX calls, if it was
>>>> configured
>>>>>> with enough network information to do so.
>>>>>>
>>>>>> Now that I think about it some more, is a registrar even allowed to
>>>> return
>>>>>> a Contact header that differs from the one the UA supplied in its
>>>> REGISTER
>>>>>> request? I suspect this is *not* allowed, and so if the registrar
>>>> supports
>>>>>> Caller-Pref but the specific tag(s) in question fail some sort of
>>>>>> validation process, its only recourse would be to fail the REGISTER
>>>> request
>>>>>> with a suitable error response.
>>>>> If that's the standard behaviour, it would of course answer my
>>>>> question.
>>>>>
>>>>>     Brian
>>>>>
>>>>>>
>>>>>> On Wed, Dec 5, 2012 at 6:35 AM, Brian E Carpenter <
>>>>>> brian.e.carpenter@gmail.com> wrote:
>>>>>>
>>>>>>> On 05/12/2012 11:01, Kevin Fleming wrote:
>>>>>>>> The language in RFC 3840 doesn't appear to contemplate the
>>>>>>>> situation
>>>>>>> you've
>>>>>>>> proposed. In its world, registrars can either support prefs (and
>>>>>>>> will
>>>>>>>> accept "Require: pref") or they don't, and they don't have
>>>>>>>> knowledge
>>>> of
>>>>>>>> which feature tags are registered with IANA and which are not. Of
>>>> course,
>>>>>>>> they *coud* attempt to validate the tags expressed by the UA, but I
>>>> don't
>>>>>>>> see an explicit way for the registrar to indicate that the UA
>>>>>>>> included
>>>>>>>> disallowed tags in its request.
>>>>>>> Understood, but in that case I don't see what good the confirmation
>>>>>>> of the tag from the registrar to the UA achieves - the UA is not
>>>>>>> going
>>>>>>> to be able to do anything with it (except maybe log whether it was
>>>>>>> received).
>>>>>>>
>>>>>>>      Brian
>>>>>>>
>>>>
>>>
>>
> 
> 

From martin.thomson@gmail.com  Fri Dec  7 10:28:28 2012
Return-Path: <martin.thomson@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69B4521F8742 for <gen-art@ietfa.amsl.com>; Fri,  7 Dec 2012 10:28:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.741
X-Spam-Level: 
X-Spam-Status: No, score=-4.741 tagged_above=-999 required=5 tests=[AWL=-1.142, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 A9N2iFgW6JVD for <gen-art@ietfa.amsl.com>; Fri,  7 Dec 2012 10:28:27 -0800 (PST)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id A82D821F86AE for <gen-art@ietf.org>; Fri,  7 Dec 2012 10:28:26 -0800 (PST)
Received: by mail-lb0-f172.google.com with SMTP id y2so708621lbk.31 for <gen-art@ietf.org>; Fri, 07 Dec 2012 10:28:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=hG/gxc4h9WY+BH4DKS8PTMF0PeDblEoYjdfNBb7xGF8=; b=XCq86BU18GEK5ZXxNaJJnpXflkRWqxsRobcWri4ar+cQS9jv32cR8l583ujixqDzqp n9m1f1//hyt8mAkAuemypaf/KgJQmMXSGNUp492ahJRWBxDhvsniFuYI0P2FHBb1xajt /NG1Joj7qMsOz72vmpaUZc+Zm4nQuSPOzqh0636zpvJAZ6XNv2PcS5ags15j9IODolvD jbSvsdTJ4jF43H6b8MHt+KAm9H++d0uND5pb8zgTAUk6RwFbraDGQUCoL4skAveWtlMR nsUGp0NbwQ8hvU++86qpfWYlojX0NuBPqzk3+CqLHqskyPoreYEz/NjdFhflwMWtY8cy Fezw==
MIME-Version: 1.0
Received: by 10.112.23.136 with SMTP id m8mr2903286lbf.16.1354904905605; Fri, 07 Dec 2012 10:28:25 -0800 (PST)
Received: by 10.112.98.200 with HTTP; Fri, 7 Dec 2012 10:28:25 -0800 (PST)
In-Reply-To: <016001cdd454$7be5ede0$73b1c9a0$@augustcellars.com>
References: <CABkgnnW_bUGEQSeupWSmw5d8gT-jWDreCptihhvemzGU6pzuWw@mail.gmail.com> <016001cdd454$7be5ede0$73b1c9a0$@augustcellars.com>
Date: Fri, 7 Dec 2012 10:28:25 -0800
Message-ID: <CABkgnnXVZ6aHFEFA1Vfj9H3Jjqv8CbN6cJTM3Rb4LREb7FBgbQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Jim Schaad <ietf@augustcellars.com>
Content-Type: text/plain; charset=UTF-8
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, draft-schaad-pkix-rfc2875-bis.all@tools.ietf.org
Subject: Re: [Gen-art] GenART review of draft-schaad-pkix-rfc2875-bis-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Dec 2012 18:28:29 -0000

On 7 December 2012 00:25, Jim Schaad <ietf@augustcellars.com> wrote:
>> Needs more ASN.1
>
> I'm lost with this, what do you believe needs to be added?  The ASN.1 as it stands is complete.

'twas in jest.  Don't worry about it.  I didn't see any errors, but
I'm not a very good ASN.1 parser.

From alexey.melnikov@isode.com  Fri Dec  7 11:03:59 2012
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC42D21F8925 for <gen-art@ietfa.amsl.com>; Fri,  7 Dec 2012 11:03:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.523
X-Spam-Level: 
X-Spam-Status: No, score=-102.523 tagged_above=-999 required=5 tests=[AWL=0.076, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 f3U0aWBGQEoo for <gen-art@ietfa.amsl.com>; Fri,  7 Dec 2012 11:03:59 -0800 (PST)
Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id 29A9321F875E for <gen-art@ietf.org>; Fri,  7 Dec 2012 11:03:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1354907038; d=isode.com; s=selector; i=@isode.com; bh=oa8mmGpumve4ZY4EniXN6RVd3PhXpKKd6j9Hiy3J6Y0=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=LP1Qh8Pdl2NSRRrEghhRKS6pRE3kU7Bq0K/XBv3bbgHbEtUe6zyuKhZwIpLkXgQGaoFWwf mtDf4bUU0CYN2YUZLlzhk2ZlXz1qNBI2/8SE6TWsuhp3dEbw2NojylqHJxoY1iJP/Iot2d au+vmPEzAM20jmXd53dQ07V+80tC2lw=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by statler.isode.com (submission channel) via TCP with ESMTPA  id <UMI9ngBEKCJE@statler.isode.com>; Fri, 7 Dec 2012 19:03:58 +0000
Message-ID: <50C23DB0.6040805@isode.com>
Date: Fri, 07 Dec 2012 19:04:16 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
To: "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-6renum-static-problem.all@tools.ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Gen-art] GenART review of draft-ietf-6renum-static-problem-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Dec 2012 19:04:00 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-6renum-static-problem-02
Reviewer: Alexey Melnikov
Review Date: 2012-12-07
IETF LC End Date: 2012-12-12
IESG Telechat date: 2012-12-13

Summary: Ready for publication.

Major issues: none
Minor issues: none
Nits/editorial comments: none

From gonzalo.camarillo@ericsson.com  Tue Dec 11 00:13:29 2012
Return-Path: <gonzalo.camarillo@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D4D921F86C7 for <gen-art@ietfa.amsl.com>; Tue, 11 Dec 2012 00:13:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 HYdLx0nnhY95 for <gen-art@ietfa.amsl.com>; Tue, 11 Dec 2012 00:13:28 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 0112E21F8632 for <gen-art@ietf.org>; Tue, 11 Dec 2012 00:13:27 -0800 (PST)
X-AuditID: c1b4fb2d-b7f316d0000028db-19-50c6eb25ffb9
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id F6.42.10459.52BE6C05; Tue, 11 Dec 2012 09:13:25 +0100 (CET)
Received: from [131.160.126.41] (153.88.115.8) by esessmw0197.eemea.ericsson.se (153.88.115.88) with Microsoft SMTP Server id 8.3.279.1; Tue, 11 Dec 2012 09:13:24 +0100
Message-ID: <50C6EB24.1020301@ericsson.com>
Date: Tue, 11 Dec 2012 10:13:24 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Flemming Andreasen <fandreas@cisco.com>
References: <50B35AAF.20104@isode.com> <50BE3DF4.6040206@cisco.com>
In-Reply-To: <50BE3DF4.6040206@cisco.com>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrELMWRmVeSWpSXmKPExsUyM+Jvja7q62MBBi0r+S1mrC6yeLGtl8Xi /QVdi6uvPrM4sHhM+b2R1WPJkp9MHqeaDT2+XP7MFsASxWWTkpqTWZZapG+XwJVx6N4PxoLt ShXXb11hb2DcLNXFyMkhIWAicf3jbjYIW0ziwr31QDYXh5DASUaJa0vOM0M4axgl9m64zgJS xSugLdF1dhYziM0ioCrx/9VLsDibgIXEllv3wWxRgSiJQxsPskPUC0qcnPkEKM7BIQLUO3WB BchMZoEZjBIvf15lAqkRFvCSuPJoEyOILSTgLPG8uxOsl1NAU+LV009Q10lKvH3/Cmwvs4Ce xJSrLYwQtrzE9rdzmCF6tSWWP2thmcAoNAvJ6llIWmYhaVnAyLyKkT03MTMnvdxwEyMwnA9u +a27g/HUOZFDjNIcLErivFxJ+/2FBNITS1KzU1MLUovii0pzUosPMTJxcEo1MCpd6AvJ7MrU +tQQu1X32xdmjbe3H54tsV5Y4cj/VHz3gp8btmtmzpDZv/Rd8cvSAM5fcSev3EyxmRfw6yXD iufpn1TYRPmPOH47cjJ6gscDY6tG4YM5lk2vrz95dDZCX7nSgEGtZePT7RqcMveablazMX1I bteT93VZ+Wm28IW2Vb9ta6wWzVBiKc5INNRiLipOBAD/9ZZFNQIAAA==
Cc: draft-ietf-mmusic-sdp-media-capabilities.all@tools.ietf.org, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-mmusic-sdp-media-capabilities-15
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Dec 2012 08:13:29 -0000

Hi,

I have not seen any answer to the email below (I may have missed it) in
which Flemming proposed some new text to address Alexey's review. What
is the status here?

Cheers,

Gonzalo

On 04/12/2012 8:16 PM, Flemming Andreasen wrote:
> Hi Alexey
> 
> Thank you for your review of the document - comments below:
> 
> On 11/26/12 7:03 AM, Alexey Melnikov wrote:
>> I am the assigned Gen-ART reviewer for this draft. For background on
>> Gen-ART, please see the FAQ at
>>   <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>
>> Please resolve these comments along with any other Last Call comments
>> you may receive.
>>
>> Document: draft-ietf-mmusic-sdp-media-capabilities-15
>> Reviewer: Alexey Melnikov
>> Review Date: 2012-11-26
>> IETF LC End Date: 2012-11-12
>> IESG Telechat date: not scheduled
>>
>> Summary:  This document is ready for publication as Proposed Standard,
>> with nits.
>>
>> Nits/editorial comments:
>>
>> This might be obvious to a SIP implementer, but the media type/subtype
>> definition RFC is not referenced anywhere. Should it be?
>>
> I don't believe so. The document is an extension of SDP (RFC 4566) which
> maintains its own media type name space and registry and hence it simply
> follows the rules of SDP (as defined in RFC 4566, which did change from
> the old SDP spec defined in RFC 2327).
> 
> RFC 4288 (which I presume you are referring to here) should not apply.
> 
> 
> 
>> 3.3.5. The Latent Configuration Attribute
>>
>>    Latent configurations may be announced by use of the latent
>>    configuration attribute, which is defined in a manner very similar to
>>    the potential configuration attribute.  The latent configuration
>>    attribute combines the properties of a media line and a potential
>>    configuration.  The media type (mt=) and the transport protocol(s)
>>    (t=) MUST be specified since the latent configuration is independent
>>    of any media line present.  In most cases, the media configuration
>>    (m=) parameter MUST be present as well (see Section 4 for examples).
>>
>> This doesn't look like a correct use of MUST, please reword not to use
>> any RFC 2119 keyword or at least provide a pointer to a document that
>> contains the original requirement.
> How about this:
> <quote>
>           Latent configurations may be announced by use of the latent
>           configuration attribute, which is defined in a manner very
> similar
>           to the potential configuration attribute. The latent
> configuration
>           attribute combines the properties of a media line and a potential
>           configuration. A latent configuration MUST include a media
> type (mt=) and a transport protocol configuration parameter
>       since the latent configuration is independent
>           of any media line present. In most cases, the media configuration
>           (m=) parameter needs to be present as well (see Section 4 for
> examples).
> </quote>
>>
>>    The lcfg attribute is a media level attribute.
>>
>>  [...]
>>
>>    If a cryptographic attribute, such as the SDES "a=crypto:" attribute
>>    [RFC4568], is referenced by a latent configuration through an acap
>>    attribute, any keying material required in the conventional
>>    attribute, such as the SDES key/salt string, MUST be included in
>>    order to satisfy formatting rules for the attribute.  The actual
>>    value(s) of the keying material SHOULD be meaningless, and the
>>
>> Can you please elaborate on what are you trying to say here?
>>
> Is this better:
> <quote>
>          If a cryptographic attribute, such as the SDES "a=crypto:"
>           attribute [RFC4568], is referenced by a latent
>           configuration through an acap attribute, any keying material
>           required in the conventional attribute, such as the SDES key/salt
>           string, MUST be included in order to satisfy formatting rules for
>           the attribute. Since the keying material will be visible but
> not actually used at this stage (since it's a latent configuration),
>       the value(s) of the keying material SHOULD be meaningless, and the
> receiver of the lcfg attribute
>       MUST ignore the values.
> </quote>
> 
>> receiver of the lcfg attribute MUST ignore the values.
>> .
>>
> 
> Thanks
> 
> -- Flemming
> 


From suresh.krishnan@ericsson.com  Tue Dec 11 21:24:30 2012
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B2EB21F8983 for <gen-art@ietfa.amsl.com>; Tue, 11 Dec 2012 21:24:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 PpIo84hJfiWq for <gen-art@ietfa.amsl.com>; Tue, 11 Dec 2012 21:24:26 -0800 (PST)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id C3D2D21F8654 for <gen-art@ietf.org>; Tue, 11 Dec 2012 21:24:26 -0800 (PST)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id qBC5ONUn011708 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 11 Dec 2012 23:24:23 -0600
Received: from [164.48.125.9] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.178) with Microsoft SMTP Server (TLS) id 8.3.279.1; Wed, 12 Dec 2012 00:24:22 -0500
Message-ID: <50C8146B.8090707@ericsson.com>
Date: Wed, 12 Dec 2012 00:21:47 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: <draft-ietf-tcpm-initcwnd.all@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: [Gen-art] Gen-ART Telechat review of draft-ietf-tcpm-initcwnd-06.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Dec 2012 05:24:30 -0000

I have been selected as the General Area Review Team (Gen-ART)
reviewer for this draft (for background on Gen-ART, please see
http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).

Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document: draft-ietf-tcpm-initcwnd-06
Reviewer: Suresh Krishnan
Review Date: 2012/12/11
IESG Telechat date: 2012/12/13

Summary: This document is well written and is ready for publication as
an Experimental RFC. I do have some minor comments you may wish to address.

Minor
=====

* Introduction

Intuitively I feel that an increased value of initcwnd is useful because
of the sizeable increase in the BDP (mainly due to the increase in
bandwidth). Is this correct? If so, it would be worth mentioning in the
introduction.

* Section 2

I am not clear on why this document has to explicitly *allow* existing
implementations to have smaller initcwnd . Isn't this automatically the
case?

"This increase is optional: a TCP MAY start with an initial window that
is smaller than 10 segments."

* Section 3

Not sure how the authors arrived at the following conclusion.

"A larger initial window will incentivize applications to use fewer
concurrent TCP connections."

Since the application (e.g. browser) developer and the TCP stack
developer are usually different, it is not clear why the application
developer would stop using multiple concurrent connections. Can you
clarify this a bit.

* Section 8

Isn't this only an issue for users on slow links which *also* have low RTTs?

Nits
=====

* RFC6077 is listed in the references but not used in the document. Remove?

* Idnits complained about a line longer than 72 chars. I located this
line to be the title line of Section 6 "Disadvantages of...Connection"

Thanks
Suresh


From peter@akayla.com  Tue Dec 11 21:46:23 2012
Return-Path: <peter@akayla.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAF1D21F8617; Tue, 11 Dec 2012 21:46:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 YzQ1eOKk6GSd; Tue, 11 Dec 2012 21:46:18 -0800 (PST)
Received: from p3plsmtpa09-08.prod.phx3.secureserver.net (p3plsmtpa09-08.prod.phx3.secureserver.net [173.201.193.237]) by ietfa.amsl.com (Postfix) with ESMTP id 65A1221F886B; Tue, 11 Dec 2012 21:45:59 -0800 (PST)
Received: from spectre ([173.8.184.78]) by p3plsmtpa09-08.prod.phx3.secureserver.net with  id aVlQ1k0011huGat01VlQyp; Tue, 11 Dec 2012 22:45:24 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-avt-rtp-evrc-nw.all@tools.ietf.org>
Date: Tue, 11 Dec 2012 21:45:23 -0800
Message-ID: <002a01cdd82b$e1a913c0$a4fb3b40$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac3YJzTUtnrb4hGMSyOFNd5zviBrVQ==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART review of draft-ietf-avt-rtp-evrc-nw-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Dec 2012 05:46:23 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at <
http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments you
may receive.

Document: draft-ietf-avt-rtp-evrc-nw-08
Reviewer: Peter Yee
Review Date: Dec-11-2012
IETF LC End Date: Dec-11-2012
IESG Telechat date: Unknown

Summary: This draft is basically ready for publication, but has a few nits
that should be fixed before publication. [Ready with nits.]

This Standards Track draft specifies RTP payload formats for use with the
EVRC-NW.  It contains IANA registration requests.

Major issues:

Minor issues:

Nits/editorial comments:

Section 1, 2nd sentence: decide whether you want to capitalize the packet
format names (Header-Free, Interleaved/Bundled) and then them use
consistently throughout the document.  RFC 3558 uses upper case names
mostly, but is not quite a paragon of consistency.

Section 4, 3rd sentence: change "zero bit" to "zero-bit".

Section 4, table, 1st row: insert a space after "Blank"  and adjust spacing
to maintain alignment of the columns.  Change "0 bit" to "0 bits".

Section 5, 2nd paragraph, 3rd sentence: change "8kHz" to "8 kHz".  Change
"16kHz" to "16 kHz".

Section 6, 3rd numbered item, 2nd sentence: change "identfication" to
"identification".

Section 7, 1st sentence: change ";" to ",".

Section 9.1.2: change "Interoperability considertaions" to "Interoperability
considerations".

Section 9.1.3, mode-set-recv paragraph, 5th sentence: change "narroband" to
"narrowband".

Section 9.1.3: change " Interoperability considertaions" to "
Interoperability considerations".

Section 10, 1st paragraph, 2nd sentence: delete the comma after
"preference".

Section 10, numbered list: I'm not sure why this is a numbered list since
the preceding paragraph makes no direct link to it.  Consider demoting the
list items to individual paragraphs.

Section 10, 1st numbered item, 1st sentence: consider rewriting "inform the
capability of " as "advertise the capability for" or "inform the capability
for". 

Section 10, 2nd numbered item, 1st sentence: rewrite "inform the" as
"indicate a".

Section 11, 2nd paragraph, 4th sentence: change "potentially-high" to
"potentially high"

Section 11, 2nd paragraph, last sentence: change "is used" to "be used".

Section 14, 2nd bullet item, 2nd sentence: capitalize "may" and "should".

Section 14, 3rd bullet item: change "receive only" to "receive-only".

I like using the serial comma (the one before "and" in a list of 3 of more
items) for clarity and to reduce confusion, but did not submit the list of
missing commas for this document -- there are a few.  Let me know if you
care.





From alexey.melnikov@isode.com  Wed Dec 12 11:13:28 2012
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD7D621E8088 for <gen-art@ietfa.amsl.com>; Wed, 12 Dec 2012 11:13:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.48
X-Spam-Level: 
X-Spam-Status: No, score=-102.48 tagged_above=-999 required=5 tests=[AWL=0.119, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 AkgNWUPv+kSy for <gen-art@ietfa.amsl.com>; Wed, 12 Dec 2012 11:13:28 -0800 (PST)
Received: from waldorf.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id BACF121E810D for <gen-art@ietf.org>; Wed, 12 Dec 2012 11:13:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1355339605; d=isode.com; s=selector; i=@isode.com; bh=fGA/ivfAncdA4Kd2RJEpFQ9b7+lUeHonhklykoecG8E=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=iqYKIgSl+5Ga2Q5+1fxhtw3ocjJWxpd5ddF/rtzIsRLRYNetuw+o5h/wsmIgPFEEilwjJF dlnB3Id7EOaWTMbun1TnBmaBoeASFTqjwAUjZLUKbsoz/h9rjWWX9v6FcLr7ccoLIP554V Zj59aKsIPLnkllY/P9Sl9jPg7MjIFqE=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by waldorf.isode.com (submission channel) via TCP with ESMTPA  id <UMjXVAB1sLnq@waldorf.isode.com>; Wed, 12 Dec 2012 19:13:25 +0000
Message-ID: <50C8D762.1090709@isode.com>
Date: Wed, 12 Dec 2012 19:13:38 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
To: Flemming Andreasen <fandreas@cisco.com>
References: <50B35AAF.20104@isode.com> <50BE3DF4.6040206@cisco.com>
In-Reply-To: <50BE3DF4.6040206@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-mmusic-sdp-media-capabilities.all@tools.ietf.org, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-mmusic-sdp-media-capabilities-15
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Dec 2012 19:13:29 -0000

On 04/12/2012 18:16, Flemming Andreasen wrote:
> Hi Alexey,
Hi Flemming,
> Thank you for your review of the document - comments below:
>
> On 11/26/12 7:03 AM, Alexey Melnikov wrote:
>> I am the assigned Gen-ART reviewer for this draft. For background on
>> Gen-ART, please see the FAQ at
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>
>> Please resolve these comments along with any other Last Call comments
>> you may receive.
>>
>> Document: draft-ietf-mmusic-sdp-media-capabilities-15
>> Reviewer: Alexey Melnikov
>> Review Date: 2012-11-26
>> IETF LC End Date: 2012-11-12
>> IESG Telechat date: not scheduled
>>
>> Summary:  This document is ready for publication as Proposed Standard,
>> with nits.
>>
>> Nits/editorial comments:
>>
>> This might be obvious to a SIP implementer, but the media 
>> type/subtype definition RFC is not referenced anywhere. Should it be?
>>
> I don't believe so. The document is an extension of SDP (RFC 4566) 
> which maintains its own media type name space and registry and hence 
> it simply follows the rules of SDP (as defined in RFC 4566, which did 
> change from the old SDP spec defined in RFC 2327).
>
> RFC 4288 (which I presume you are referring to here) should not apply.
I think SDP has to be in agreement with RFC 4288 or we have a bigger 
problem. In particular media type syntax. But I am Ok with no change in 
this area.
>> 3.3.5. The Latent Configuration Attribute
>>
>>    Latent configurations may be announced by use of the latent
>>    configuration attribute, which is defined in a manner very similar to
>>    the potential configuration attribute.  The latent configuration
>>    attribute combines the properties of a media line and a potential
>>    configuration.  The media type (mt=) and the transport protocol(s)
>>    (t=) MUST be specified since the latent configuration is independent
>>    of any media line present.  In most cases, the media configuration
>>    (m=) parameter MUST be present as well (see Section 4 for examples).
>>
>> This doesn't look like a correct use of MUST, please reword not to 
>> use any RFC 2119 keyword or at least provide a pointer to a document 
>> that contains the original requirement.
> How about this:
> <quote>
>           Latent configurations may be announced by use of the latent
>           configuration attribute, which is defined in a manner very 
> similar
>           to the potential configuration attribute. The latent 
> configuration
>           attribute combines the properties of a media line and a 
> potential
>           configuration. A latent configuration MUST include a media 
> type (mt=) and a transport protocol configuration parameter
>       since the latent configuration is independent
>           of any media line present. In most cases, the media 
> configuration
>           (m=) parameter needs to be present as well (see Section 4 
> for examples).
> </quote>
Yes, this is exactly what I had in mind. Thanks.
>>    The lcfg attribute is a media level attribute.
>>
>>  [...]
>>
>>    If a cryptographic attribute, such as the SDES "a=crypto:" attribute
>>    [RFC4568], is referenced by a latent configuration through an acap
>>    attribute, any keying material required in the conventional
>>    attribute, such as the SDES key/salt string, MUST be included in
>>    order to satisfy formatting rules for the attribute.  The actual
>>    value(s) of the keying material SHOULD be meaningless, and the
>>
>> Can you please elaborate on what are you trying to say here?
>>
> Is this better:
> <quote>
>          If a cryptographic attribute, such as the SDES "a=crypto:"
>           attribute [RFC4568], is referenced by a latent
>           configuration through an acap attribute, any keying material
>           required in the conventional attribute, such as the SDES 
> key/salt
>           string, MUST be included in order to satisfy formatting 
> rules for
>           the attribute. Since the keying material will be visible but 
> not actually used at this stage (since it's a latent configuration),
>       the value(s) of the keying material SHOULD be meaningless, and 
> the receiver of the lcfg attribute
>       MUST ignore the values.
> </quote>
This is better. I was actually most wondering about the meaning of 
"meaningless". Did you mean "not a real value you would use for a real 
exchange"?
>> receiver of the lcfg attribute MUST ignore the values.
>> .
Best Regards,
Alexey



From fandreas@cisco.com  Wed Dec 12 14:08:24 2012
Return-Path: <fandreas@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D8D11F0CD0 for <gen-art@ietfa.amsl.com>; Wed, 12 Dec 2012 14:08:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 7wpTQOwXoSE5 for <gen-art@ietfa.amsl.com>; Wed, 12 Dec 2012 14:08:23 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 5831721F8A60 for <gen-art@ietf.org>; Wed, 12 Dec 2012 14:08:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4932; q=dns/txt; s=iport; t=1355350103; x=1356559703; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=VuVI2sTx3bgqmBb3pBeBUyPDuVcGL0e2CahfDf8TgCg=; b=FfOzdQhLlW5Pkf+Gn6FCWOQIPVzJLLcpH+tDYqfnfqzZzAaXh9L8ADhQ 8+D5kyQE4Xn1TKS0YlYBv0cVYlDVJSDanOdIwmckOubTVzmqBqDCCuGpB edMcAyVKJFcD4bwXofDJnOUN7T1VITvNBDWvwVyKS4zPapUIfWmM56rXQ U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArwHAHX/yFCtJV2b/2dsb2JhbABFg0i7URZzgh4BAQEDATg8BAEQCxQECRYPCQMCAQIBRQYNAQcBAYgHBgy9foxLhEMDiGCJdoMzgRyPLIMR
X-IronPort-AV: E=Sophos;i="4.84,269,1355097600"; d="scan'208";a="152305638"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-7.cisco.com with ESMTP; 12 Dec 2012 22:08:22 +0000
Received: from rtp-fandreas-8718.cisco.com (rtp-fandreas-8718.cisco.com [10.117.7.89]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id qBCM8LqW030330;  Wed, 12 Dec 2012 22:08:22 GMT
Message-ID: <50C90055.9090900@cisco.com>
Date: Wed, 12 Dec 2012 17:08:21 -0500
From: Flemming Andreasen <fandreas@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>
References: <50B35AAF.20104@isode.com> <50BE3DF4.6040206@cisco.com> <50C8D762.1090709@isode.com>
In-Reply-To: <50C8D762.1090709@isode.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-mmusic-sdp-media-capabilities.all@tools.ietf.org, "gen-art@ietf.org" <gen-art@ietf.org>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-mmusic-sdp-media-capabilities-15
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Dec 2012 22:08:24 -0000

On 12/12/12 2:13 PM, Alexey Melnikov wrote:
> On 04/12/2012 18:16, Flemming Andreasen wrote:
>> Hi Alexey,
> Hi Flemming,
>> Thank you for your review of the document - comments below:
>>
>> On 11/26/12 7:03 AM, Alexey Melnikov wrote:
>>> I am the assigned Gen-ART reviewer for this draft. For background on
>>> Gen-ART, please see the FAQ at
>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>
>>> Please resolve these comments along with any other Last Call comments
>>> you may receive.
>>>
>>> Document: draft-ietf-mmusic-sdp-media-capabilities-15
>>> Reviewer: Alexey Melnikov
>>> Review Date: 2012-11-26
>>> IETF LC End Date: 2012-11-12
>>> IESG Telechat date: not scheduled
>>>
>>> Summary:  This document is ready for publication as Proposed Standard,
>>> with nits.
>>>
>>> Nits/editorial comments:
>>>
>>> This might be obvious to a SIP implementer, but the media 
>>> type/subtype definition RFC is not referenced anywhere. Should it be?
>>>
>> I don't believe so. The document is an extension of SDP (RFC 4566) 
>> which maintains its own media type name space and registry and hence 
>> it simply follows the rules of SDP (as defined in RFC 4566, which did 
>> change from the old SDP spec defined in RFC 2327).
>>
>> RFC 4288 (which I presume you are referring to here) should not apply.
> I think SDP has to be in agreement with RFC 4288 or we have a bigger 
> problem. In particular media type syntax. But I am Ok with no change 
> in this area.
>>> 3.3.5. The Latent Configuration Attribute
>>>
>>>    Latent configurations may be announced by use of the latent
>>>    configuration attribute, which is defined in a manner very 
>>> similar to
>>>    the potential configuration attribute.  The latent configuration
>>>    attribute combines the properties of a media line and a potential
>>>    configuration.  The media type (mt=) and the transport protocol(s)
>>>    (t=) MUST be specified since the latent configuration is independent
>>>    of any media line present.  In most cases, the media configuration
>>>    (m=) parameter MUST be present as well (see Section 4 for examples).
>>>
>>> This doesn't look like a correct use of MUST, please reword not to 
>>> use any RFC 2119 keyword or at least provide a pointer to a document 
>>> that contains the original requirement.
>> How about this:
>> <quote>
>>           Latent configurations may be announced by use of the latent
>>           configuration attribute, which is defined in a manner very 
>> similar
>>           to the potential configuration attribute. The latent 
>> configuration
>>           attribute combines the properties of a media line and a 
>> potential
>>           configuration. A latent configuration MUST include a media 
>> type (mt=) and a transport protocol configuration parameter
>>       since the latent configuration is independent
>>           of any media line present. In most cases, the media 
>> configuration
>>           (m=) parameter needs to be present as well (see Section 4 
>> for examples).
>> </quote>
> Yes, this is exactly what I had in mind. Thanks.
>>>    The lcfg attribute is a media level attribute.
>>>
>>>  [...]
>>>
>>>    If a cryptographic attribute, such as the SDES "a=crypto:" attribute
>>>    [RFC4568], is referenced by a latent configuration through an acap
>>>    attribute, any keying material required in the conventional
>>>    attribute, such as the SDES key/salt string, MUST be included in
>>>    order to satisfy formatting rules for the attribute.  The actual
>>>    value(s) of the keying material SHOULD be meaningless, and the
>>>
>>> Can you please elaborate on what are you trying to say here?
>>>
>> Is this better:
>> <quote>
>>          If a cryptographic attribute, such as the SDES "a=crypto:"
>>           attribute [RFC4568], is referenced by a latent
>>           configuration through an acap attribute, any keying material
>>           required in the conventional attribute, such as the SDES 
>> key/salt
>>           string, MUST be included in order to satisfy formatting 
>> rules for
>>           the attribute. Since the keying material will be visible 
>> but not actually used at this stage (since it's a latent configuration),
>>       the value(s) of the keying material SHOULD be meaningless, and 
>> the receiver of the lcfg attribute
>>       MUST ignore the values.
>> </quote>
> This is better. I was actually most wondering about the meaning of 
> "meaningless". Did you mean "not a real value you would use for a real 
> exchange"?
Indeed - much better stated that way. I've updated the text accordingly 
and just submitted the updated document. Thanks again for the review and 
comments.

Regards

-- Fleming

>>> receiver of the lcfg attribute MUST ignore the values.
>>> .
> Best Regards,
> Alexey
>
>
> .
>


From mahoney@nostrum.com  Thu Dec 13 15:29:30 2012
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E443621F89D0 for <gen-art@ietfa.amsl.com>; Thu, 13 Dec 2012 15:29:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
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 yD2jOrtaPUdF for <gen-art@ietfa.amsl.com>; Thu, 13 Dec 2012 15:29:26 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 5546C21F897D for <gen-art@ietf.org>; Thu, 13 Dec 2012 15:29:26 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local ([4.30.77.1]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qBDNTPWd010122 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 13 Dec 2012 17:29:25 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <50CA64D5.2040108@nostrum.com>
Date: Thu, 13 Dec 2012 17:29:25 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 4.30.77.1 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2012-12-13
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Dec 2012 23:29:31 -0000

Hi all,

The following reviewers have assignments:

Reviewer           LC end      Draft

Alexey Melnikov   2013-01-03   draft-ietf-roll-p2p-rpl-15

Miguel Garcia     2012-12-21   draft-ietf-v6ops-464xlat-08

Peter McCann      2012-12-19   draft-ietf-core-coap-13 *

Peter Yee         2012-12-25   draft-ietf-6man-udpchecksums-06 **

Richard Barnes    2012-12-25   draft-ietf-6man-udpzero-08 **

Roni Even         2012-12-25   draft-ietf-appsawg-json-patch-08 ***

Suresh Krishnan   2012-12-25   draft-ietf-appsawg-json-pointer-07 ***

Vijay Gurbani     2012-12-24   draft-ietf-oauth-assertions-08

Wassim Haddad     2013-01-04   draft-ietf-trill-oam-req-04

* AD-requested early review
** 2nd LC
*** on the 2013-01-10 telechat


I have made the assignments in the review tool:
http://art.tools.ietf.org/tools/art/genart/


However, the assignment spreadsheets are not available due to WebDAV 
issues.
I've notified Henrik of the problem.


The standard template is included below.

Thanks,

Jean

-------------------------------------------------------------------

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

From mahoney@nostrum.com  Thu Dec 13 15:39:31 2012
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F10521F87F6 for <gen-art@ietfa.amsl.com>; Thu, 13 Dec 2012 15:39:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
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 TBVmFCJXw1yP for <gen-art@ietfa.amsl.com>; Thu, 13 Dec 2012 15:39:28 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 4642321F8527 for <gen-art@ietf.org>; Thu, 13 Dec 2012 15:39:28 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local ([4.30.77.1]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qBDNdNlI011237 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 13 Dec 2012 17:39:23 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <50CA672B.1050904@nostrum.com>
Date: Thu, 13 Dec 2012 17:39:23 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 4.30.77.1 is authenticated by a trusted mechanism)
Subject: [Gen-art] Assignments for the 2012-12-20 telechat
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Dec 2012 23:39:31 -0000

Hi all,

The following reviewers have assignments:

Reviewer             LC end      Draft

Alexey Melnikov      2012-11-12  draft-ietf-mmusic-sdp-media-capabilities-16 *

Christer Holmberg    2012-12-13  draft-ietf-tcpm-experimental-options-03

Francis Dupont       2012-12-17  draft-ietf-sipclf-format-09

Joel Halpern         2012-12-17  draft-ietf-sipclf-problem-statement-11 **

Miguel Garcia        2012-10-22  draft-ietf-fecframe-simple-rs-05 *

Peter Yee            2012-12-11  draft-ietf-avt-rtp-evrc-nw-09 *

* Earlier draft reviewed
** Already reviewed


I have made the assignments in the review tool:
http://art.tools.ietf.org/tools/art/genart/

However, assignment spreadsheets are not available due to WebDAV issues.


For your convenience, the review boilerplate template is included below.

Note that reviews should ideally be posted to the gen-art mailing list
by COB on Tuesday:
http://wiki.tools.ietf.org/area/gen/trac/wiki/

Jean

-------------------------------------------------------------------

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
< http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

From christer.holmberg@ericsson.com  Fri Dec 14 05:29:17 2012
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6A5821F86B7 for <gen-art@ietfa.amsl.com>; Fri, 14 Dec 2012 05:29:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.211
X-Spam-Level: 
X-Spam-Status: No, score=-6.211 tagged_above=-999 required=5 tests=[AWL=0.037,  BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, 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 Hfx+nQLyZhV4 for <gen-art@ietfa.amsl.com>; Fri, 14 Dec 2012 05:29:17 -0800 (PST)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id AB31821F85B2 for <gen-art@ietf.org>; Fri, 14 Dec 2012 05:29:12 -0800 (PST)
X-AuditID: c1b4fb30-b7f736d0000010de-f3-50cb29a78616
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 37.DD.04318.7A92BC05; Fri, 14 Dec 2012 14:29:11 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.119]) by ESESSHC021.ericsson.se ([153.88.183.81]) with mapi id 14.02.0318.001; Fri, 14 Dec 2012 14:29:10 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Genart review of draft-ietf-tcpm-experimental-options-03.txt
Thread-Index: Ac3Z/v+ddXXMBSRqTVqF4iknB0Uklw==
Date: Fri, 14 Dec 2012 13:29:10 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B055BE3@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.17]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B055BE3ESESSMB209ericsso_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrBLMWRmVeSWpSXmKPExsUyM+Jvje5yzdMBBstuC1s8/PyV3eLqq88s DkweS5b8ZPL4cvkzWwBTFJdNSmpOZllqkb5dAlfGz8M72AvuKFSs6VdsYGyX7WLk4JAQMJGY v7myi5ETyBSTuHBvPVsXIxeHkMAhRonDr6YwQzhLGCWuzL3OCtLAJmAh0f1PG6RBREBTYu6K t0wgNrNApcScnT9YQEqEBVwl/u9NhSjxkjgwZTIzhK0ncejLanYQm0VAVeJn51IWEJtXwFti 8sdrYDWMQDd8P7UGaqS4xK0n85kgbhOQWLLnPDOELSrx8vE/VojzFSWW98tBlOdLHLhxkhVi pKDEyZlPWCYwCs9CMmkWkrJZSMog4joSC3Z/YoOwtSWWLXzNDGOfOfCYCVl8ASP7Kkb23MTM nPRy802MwNg4uOW3wQ7GTffFDjFKc7AoifPqqe73FxJITyxJzU5NLUgtii8qzUktPsTIxMEp 1cC46KzNu7YW09s1drMv7EmczsQT7am4a9sftkTO06xdS1Z+iDM9/GbXg7d3dVa5/Zz7Y83l HZKb+28dlufzWlW7gufLojsFcqrdNdNadCbFv3N7GVvAfTfF3sdjS8nD5QJTjrMWlvY6r3C2 VJ3r45Fxt2Ff1emPvKvtL39/EJF7+fjnonmTX525oMRSnJFoqMVcVJwIAAR9aP1bAgAA
Cc: "draft-ietf-tcpm-experimental-options.all@tools.ietf.org" <draft-ietf-tcpm-experimental-options.all@tools.ietf.org>
Subject: [Gen-art] Genart review of draft-ietf-tcpm-experimental-options-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Dec 2012 13:29:17 -0000

--_000_7594FB04B1934943A5C02806D1A2204B055BE3ESESSMB209ericsso_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at < http://wiki.tools.ietf.org/area/gen/trac/wiki/Ge=
nArtfaq>.

Please wait for direction from your document shepherd or AD before posting =
a new version of the draft.

Document: draft-ietf-tcpm-experimental-options-03.txt
Reviewer: Christer Holmberg
Review Date: 14 December 2012
IETF LC End Date: 13 December 2012
IESG Telechat date: 20 December 2012

Summary: The draft is ready for publication, without any comments.

Major issues: -

Minor issues: -

Nits/editorial comments: -

Regards,

Christer

--_000_7594FB04B1934943A5C02806D1A2204B055BE3ESESSMB209ericsso_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I am the assigned Gen-ART reviewer for this draft. F=
or background on Gen-ART, please see the FAQ at &lt;
<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://=
wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please wait for direction from your document shepher=
d or AD before posting a new version of the draft.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Document: draft-ietf-tcpm-experimental-options-03.tx=
t<o:p></o:p></p>
<p class=3D"MsoNormal">Reviewer: Christer Holmberg<o:p></o:p></p>
<p class=3D"MsoNormal">Review Date: 14 December 2012<o:p></o:p></p>
<p class=3D"MsoNormal">IETF LC End Date: 13 December 2012<o:p></o:p></p>
<p class=3D"MsoNormal">IESG Telechat date: 20 December 2012<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Summary: The draft is ready for publication, without=
 any comments.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Major issues: -<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Minor issues: -<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Nits/editorial comments: -<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Regards,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Christer<o:p></o:p></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B055BE3ESESSMB209ericsso_--

From mary.ietf.barnes@gmail.com  Fri Dec 14 10:02:34 2012
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B52321F8AB4 for <gen-art@ietfa.amsl.com>; Fri, 14 Dec 2012 10:02:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.112
X-Spam-Level: 
X-Spam-Status: No, score=-103.112 tagged_above=-999 required=5 tests=[AWL=-0.413, BAYES_00=-2.599, GB_I_LETTER=-2, J_CHICKENPOX_56=0.6, MANGLED_LIST=2.3, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 kryvkC2hvYqY for <gen-art@ietfa.amsl.com>; Fri, 14 Dec 2012 10:02:30 -0800 (PST)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 49BB621F8A12 for <gen-art@ietf.org>; Fri, 14 Dec 2012 10:02:29 -0800 (PST)
Received: by mail-la0-f44.google.com with SMTP id d3so3016860lah.31 for <gen-art@ietf.org>; Fri, 14 Dec 2012 10:02:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=jUfYGSr154GTOsSXP59/OxjnBw0WevTdDhmVsn2xTWM=; b=SgjjRCwWxsuULpm6Hw1JyqVyM63fj4/WcDF6sWzvmPtEzRZfFB8zczYeslm2VeS7U+ vuUzxMg8aB2NLU5TE5pQyCQtemogaSx/oOmqN4oRCPTcTOIy78gFSB+LNoMoeJwchSNB VWyfTAPk70iMOpwRl3o8efzdL79PuJx23uPT/3TBnXh7AFa3Bd3H67C7cSqsYD4XpHEf oP7z6/x803mQOsBRzAQvBTv5HBAk2YQwY4rd5QJncPm6mubex+7W+Rw7ge6DhfamMvLs H8I96uXDZoJvxmlQI13J9mjGsbQn4pyZL2JQO2/dzD9632xUmOLwJI4OXf8NS7DA9hN9 b49w==
MIME-Version: 1.0
Received: by 10.152.162.1 with SMTP id xw1mr3527843lab.3.1355508148933; Fri, 14 Dec 2012 10:02:28 -0800 (PST)
Received: by 10.114.20.41 with HTTP; Fri, 14 Dec 2012 10:02:28 -0800 (PST)
Date: Fri, 14 Dec 2012 12:02:28 -0600
Message-ID: <CAHBDyN5j_kHWLvxv4xc=Hp2Hq65Sm95+ko3E6oAX0pNH=OojCg@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-p2psip-base.all@tools.ietf.org
Subject: [Gen-art] Gen-ART: Re-review of draft-ietf-p2psip-base-23
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Dec 2012 18:02:34 -0000

Russ asked that I re-review the updated document.

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document: draft-ietf-p2psip-base-23
Reviewer:  Mary Barnes
Review Date: 14 December 2012
Re-Review started Date (-21):  28 March 2012 (was told a new version
was coming out)
Original Review Date (-17) : 6 August 2011
IETF LC End Date: 22 July 2011

Summary: Not Ready.

I reviewed through section 6 of this version (section 5 of -17)
against my comments on the -17 . Since many of my comments had not
been addressed, I'm not going to take the time to re-review the
remainder of the document.

I also *strongly* recommend that you ensure Henning has reviewed this
document *before* it gets into the RFC editor's queue.  He has fairly
strict (and quite accurate) views on grammar and structure but it
really isn't good to have so many changes go in at AUTH48 as there is
a risk of introducing true technical bugs or changing something that
was carefully crafted to achieve WG consensus:
http://www.cs.columbia.edu/~hgs/etc/writing-bugs.html


Comments:
=3D=3D=3D=3D=3D=3D=3D=3D=3D

I have reviewed my previous comments on this document -17 as compared
to the -23.  Comments from the -17 that remain are prefaced with [-17]

Major:
------

General:
--[-17] The message names are used inconsistently.  The IANA registry
has the message codes all lower case.  There are places in the
examples and the body of the document where the _req part is missing,
there is no "_", the first letters are Upper case, etc.  The messages
are also used in a general sense - e.g., "MUST perform an Attach",
which should really be stated as "MUST send an attach_req message).
[-23]  For the latter point, Cullen responded that this isn't really
just talking about sending a message but rather performing a function
that results in a message being sent.

However, I still contend that there is inconsistency and the whole
concept of an Attach function/process/whatever is not well defined.
There are times when "attached" appears to be used purely as a verb
rather than referring to the functionality, but it is not always
clear.  For example, the last two sentences in section 3.4:
   "Instead, we use the Attach request to establish a
   connection.  Attach uses ICE [RFC5245] to establish the connection.
   It is assumed that the reader is familiar with ICE."
I will note that the only mention of "Attach" previously was in the
definitions for Connection Table ("Attach handshakes") and Routing
Table ("some peers will have Attached").  The word "Attach" is used
with the _req or the word "request" in places like the following in
section 3.4 (1st sentence):   "There are two cases where Attach is not
used."  I have no idea really whether this means this Attach
function/process is not needed or the message is not required to be
sent.

Major - detailed:

- Section 3.4, last paragraph:  Accepting Cullen's comment that this
text is not normative, I'll let my first set of -17 comments on this
one go.  However, the following is still not clear to me:
What is meant by the "specified link set" - is that referring to all
the nearby peers or the peers+enough others?  Or is this more clearly
(and normatively) specified elsewhere, such that a reference could be
added.

- [-17 5.1.2] Section 6.1.2:
-- Last paragraph (9) mixes normative text with in an example. The
normative text needs to be separated from the example - e.g., split
some of the sentences into the normative behavior and then the
example. The example should be written in terms of what happens (which
is what was done in the previous examples in this section and not what
SHOULD, MAY or MUST happen).      For example, this sentence:
   "Node A MUST implement an algorithm that ensures that
   A returns a response to this request to node B with the destination
   list [B, Z, Y, X], provided that the node to which A forwards the
   request follows the same contract.
should have a generic normative statement rather than saying "Node A
MUST".  It should be something like: "A node must implement an
algorithm that ensures it returns a response =85", then the same
sentence can be a "For example, Node A MUST=85"

- [-17 5.3.2.1] Section 6.3.2.1:
--1st paragraph: shouldn't this be normative?
"the configuration document has a sequence number..." ->  "the
configuration document MUST contain a sequence number which MUST be
monotonically increasing mod 65535"

- [-17 5.3.2.2] -Section 6.3.2.2:
--Paragraph after second structure, suggest the following changes:
---"the generation counters should" ->  "the generation counters SHOULD"
---"An implementation could use.." -> "An implementation MAY use=85"
---"the node confirms that the generation counter matches" -> "the
node MUST confirm that the generation counter matches"
---"If it does not match, it is silently dropped." -> "If it does not
match, it MUST be silently dropped."

- [-17 5.3.3.1] Section 6.3.3.1:
--1st para: "a request returns" -> "a request MUST return"
--1st para: "then the message code is the response code that matches
the request" ->
"then the message code MUST be set to the response code that matches
the request"
--2nd para: "message code is set" ->  "message code MUST be set"

- [-17 5.3.4] Section 6.3.4 - needs normative language:
--1st paragraph after GenericCertificate structure:
---"All signatures are formatted" -> "Alls signatures MUST be formatted"
---"The input structure=85varies.." ->  "The input structure =85 MAY vary=
=85"

- [-23] Review stops at section 6.4.2


Minor:
------
- idnits identifies 5 errors (downrefs).  There are also unused
references and 22 warnings that should be reviewed - the ones, in
particular, which should be fixed are with regards to normative
language usage.

- While Cullen responded to this comment with an explanation, there
was no change to clarify the text:
- [-17] Section 1.2.1, 2nd paragraph: I don't understand the example
as to why a single application requires multiple usages - i.e, why
voicemail?  Isn't the intent to say that an application might need to
use both SIP and XMPP - i.e., you wouldn't define a "usage" for an
application, would you?

- [-17] Section 2. Some of the definitions use terms that are not yet
defined, so that's not particularly helpful - i.e,. Attach and Update
are used. In some cases (e.g., Connection Table), you could just
delete the statement with the reference.

- [-17] Section 3.1, 1st para: This sentence doesn't grok because the
concept of "overlay parameters" hasn't been mentioned before this
section nor has the concept of a "configuration document".
  "The overlay parameters are specified in a configuration document."
At a minimum those terms should be defined in the terminology section
and introduced in the intro paragraph in section 3.

- [-17] Section 3.3, last paragraph.  Add a reference to 5.4.2.4
after "RouteQuery method"

- [-17] Section 5.1.2:
--1st paragraph: I have no idea what the "other three cases" references.

- [-17 Section 5.3] Section 6.3:  The three parts of the messages are
listed and the last sentence says that "The following sections
describe the format of each part of the message", but there are 4
sub-sections in 5.3, with the first section NOT describing one of the
three parts of the messages.  I suggest to strike that last sentence
and just put references to the sections in the list items for each of
the three messages

- [-17 Section 5.6] Section 6.6:
-- The last three paragraphs are confusing.
---In particular, it's not clear what algorithms are being referenced
in this sentence:
  "We will first define each of these algorithms, then
   define overlay link protocols that use them."
--- In the note paragraph, I believe "These protocols have been
chosen=85" is referring to the three overlay link protocols supported by
RELOAD per this document.
---The Note to implementors paragraph seems out of context
--- Per my next comment, I suggest to move the detailed discussion of
future overlay link protocols to the appendix, so some of this text
may be relevant only to that.

-[ -17 5.6.1] Section 6.6.1:  I suggest that the sub-sections in this
section be moved to an appendix and a reference to such be added.

[-23] Did not review beyond section 6.

Nits:
-----

- [-17] Section 2.
--General: It would be helpful if the terms were alphabetized.
[Note, Cullen's response was that this causes forward reference
problems, but that's unavoidable. If the terms are alphabetized, it is
much easier to find them. ]
--Node: "We use the term "Node" to refer to =85" -> "Refers to =85" or
something to make it more consistent with the format for the other
terms.

- Section 6.1.1, last bullet:  "later" -> "latter"

- Section 6.1.3: Shouldn't this be "For example," rather than "I.e.,"?
 If "I.e.," is appropriate in that those are the only routing
algorithms which might be used, then I would suggest adjusting the
sentence structure by using words rather than the abbreviation (it's
debatable whether the latter is grammatically correct) to something
like.  "This means that a node=85".

- [-17 5.5.1.6] Section 6.5.1.6: Add references for SCTP and DCCP.

[-23] Did not review beyond nits identified for section 6.

From mahoney@nostrum.com  Fri Dec 14 11:59:40 2012
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 376BE21F876A for <gen-art@ietfa.amsl.com>; Fri, 14 Dec 2012 11:59:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
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 NhYZkpa-0ZJ7 for <gen-art@ietfa.amsl.com>; Fri, 14 Dec 2012 11:59:39 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 73ED121F8597 for <gen-art@ietf.org>; Fri, 14 Dec 2012 11:59:39 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-45-100.dllstx.fios.verizon.net [173.71.45.100]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qBEJxchO052649 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Fri, 14 Dec 2012 13:59:38 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <50CB852A.4070100@nostrum.com>
Date: Fri, 14 Dec 2012 13:59:38 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: gen-art@ietf.org
References: <50CA672B.1050904@nostrum.com>
In-Reply-To: <50CA672B.1050904@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 173.71.45.100 is authenticated by a trusted mechanism)
Subject: Re: [Gen-art] Assignments for the 2012-12-20 telechat
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Dec 2012 19:59:40 -0000

Hi all,

The following new documents have been added to the agenda:

Ben Campbell draft-ietf-karp-routing-tcp-analysis-06 *

Elwyn Davies draft-ietf-sidr-usecases-05

Thanks,

Jean

On 12/13/12 5:39 PM, A. Jean Mahoney wrote:
> Hi all,
>
> The following reviewers have assignments:
>
> Reviewer             LC end      Draft
>
> Alexey Melnikov      2012-11-12 
> draft-ietf-mmusic-sdp-media-capabilities-16 *
>
> Christer Holmberg    2012-12-13 draft-ietf-tcpm-experimental-options-03
>
> Francis Dupont       2012-12-17  draft-ietf-sipclf-format-09
>
> Joel Halpern         2012-12-17 draft-ietf-sipclf-problem-statement-11 **
>
> Miguel Garcia        2012-10-22  draft-ietf-fecframe-simple-rs-05 *
>
> Peter Yee            2012-12-11  draft-ietf-avt-rtp-evrc-nw-09 *
>
> * Earlier draft reviewed
> ** Already reviewed
>
>
> I have made the assignments in the review tool:
> http://art.tools.ietf.org/tools/art/genart/
>
> However, assignment spreadsheets are not available due to WebDAV issues.
>
>
> For your convenience, the review boilerplate template is included below.
>
> Note that reviews should ideally be posted to the gen-art mailing list
> by COB on Tuesday:
> http://wiki.tools.ietf.org/area/gen/trac/wiki/
>
> Jean
>
> -------------------------------------------------------------------
>
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> < http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please wait for direction from your document shepherd
> or AD before posting a new version of the draft.
>
> Document:
> Reviewer:
> Review Date:
> IETF LC End Date:
> IESG Telechat date: (if known)
>
> Summary:
>
> Major issues:
>
> Minor issues:
>
> Nits/editorial comments:
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From mary.ietf.barnes@gmail.com  Fri Dec 14 12:55:47 2012
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AB1721F8A6B for <gen-art@ietfa.amsl.com>; Fri, 14 Dec 2012 12:55:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.549
X-Spam-Level: 
X-Spam-Status: No, score=-103.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 TyCb5qQDmgYq for <gen-art@ietfa.amsl.com>; Fri, 14 Dec 2012 12:55:43 -0800 (PST)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 06E0E21F8A28 for <gen-art@ietf.org>; Fri, 14 Dec 2012 12:55:42 -0800 (PST)
Received: by mail-lb0-f172.google.com with SMTP id y2so3163248lbk.31 for <gen-art@ietf.org>; Fri, 14 Dec 2012 12:55:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=LgqFjGS5OuE4m64P3A62/EUChz2jOJHkP7PhkU7pwMM=; b=Don3vV1pNonaz+35RJ5semHLhdsJxQ2EAbi3ErhCFZE4uQwJ07KDYcO3NCU7hDzk2g c/+4qJAOIFzsdrUXUkvLpr/l3kEF7jERfmFMPTUwM0WLJQqzld9bkQvKfEFe3ml8Yy4Z tpgst1oiYubSNR28LH3ohsADhMBdgpxIuO0r01mmbtv6/CLkxTb7U+nCDvBBvx+ladCM nriNGS6ywIwt20IsCHJOZwSqawzJY6fN0BLM4pzoeE8f9InbpEyb4IS+H13IWoju5eVG h6FvVRPvb+gFWFIwP/hdZHMPwlE1bW1ZRpXgiOpq3Rp3cHJ/vhvQj0UoocoVKAYKJriM aBLg==
MIME-Version: 1.0
Received: by 10.152.129.197 with SMTP id ny5mr3842991lab.43.1355518541919; Fri, 14 Dec 2012 12:55:41 -0800 (PST)
Received: by 10.114.20.41 with HTTP; Fri, 14 Dec 2012 12:55:41 -0800 (PST)
Date: Fri, 14 Dec 2012 14:55:41 -0600
Message-ID: <CAHBDyN6Tbsx+oQ7162XyMZpRszAgnyji_odARPaLHD5pS0Ekeg@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: draft-ietf-mboned-auto-multicast.all@tools.ietf.org,  "gen-art@ietf.org" <gen-art@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [Gen-art] Gen-ART LC review: draft-ietf-mboned-auto-multicast-14
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Dec 2012 20:55:47 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document: draft-ietf-mboned-auto-multicast-14
Reviewer:  Mary Barnes
Review Date:  14 Dec 2012
IETF LC End Date: 19 Dec 2012

Summary:  Ready with comment/nits.

Minor comments:
----------------

References:
- There is a normative downref to RFC 1321.  Does this need to be a
normative reference? Note, I could not find the shepherd write-up in
the tracker to see if this had been noted and explained.

Nits:
-----
IDNITS identifies the following:
- there are 15 instances of two long of lines
- there is an obsolete reference to RFC 2236 (Obsoleted by RFC 3376)
- there are a number of unused references that can likely be removed.

- General: please add #s to all the figures

- Section 4.1.3, 1st sentence: shouldn't "relay services gateways" be
"relay services gateway"

- Appendix A.1, 2nd paragraph:  "Section Section 5.3.6" -> "Section 5.3.6"

From gonzalo.camarillo@ericsson.com  Fri Dec 14 13:17:20 2012
Return-Path: <gonzalo.camarillo@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73AC321F8B07 for <gen-art@ietfa.amsl.com>; Fri, 14 Dec 2012 13:17:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.784
X-Spam-Level: 
X-Spam-Status: No, score=-105.784 tagged_above=-999 required=5 tests=[AWL=-0.435, BAYES_00=-2.599, GB_I_LETTER=-2, HELO_EQ_SE=0.35, J_CHICKENPOX_56=0.6, MANGLED_LIST=2.3, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 2YxsEyxUDOk7 for <gen-art@ietfa.amsl.com>; Fri, 14 Dec 2012 13:17:16 -0800 (PST)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 86A6B21F8AFD for <gen-art@ietf.org>; Fri, 14 Dec 2012 13:17:15 -0800 (PST)
X-AuditID: c1b4fb25-b7fb26d000006129-54-50cb975ab06b
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 02.48.24873.A579BC05; Fri, 14 Dec 2012 22:17:14 +0100 (CET)
Received: from [141.137.12.23] (153.88.115.8) by esessmw0256.eemea.ericsson.se (153.88.115.97) with Microsoft SMTP Server id 8.3.279.1; Fri, 14 Dec 2012 22:17:13 +0100
Message-ID: <50CB9757.5080502@ericsson.com>
Date: Fri, 14 Dec 2012 23:17:11 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Mary Barnes <mary.ietf.barnes@gmail.com>
References: <CAHBDyN5j_kHWLvxv4xc=Hp2Hq65Sm95+ko3E6oAX0pNH=OojCg@mail.gmail.com>
In-Reply-To: <CAHBDyN5j_kHWLvxv4xc=Hp2Hq65Sm95+ko3E6oAX0pNH=OojCg@mail.gmail.com>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrLLMWRmVeSWpSXmKPExsUyM+JvjW7U9NMBBo8n8FnsuqJl0fH/F4vF 1VefWSxevbjJbvF5/35mB1aPnbPusnssWfKTyePikm+MHl8uf2bzWHXnC2sAaxSXTUpqTmZZ apG+XQJXRs/uC2wFF/wq+madYG1gXGPXxcjJISFgInGk6w4zhC0mceHeejYQW0jgJKPEx6fl XYxcQPZqRokp7y6zgCR4BbQlfm/ZwwhiswioSqxqXA/WzCZgIbHl1n2wGlGBKIlDGw+yQ9QL Spyc+QQsLiKgI/Ht81s2kKHMAqsYJVZ+PcfaxcjBISxgI9F9UQ1icYDEyc+7wOZzCgRKdCx9 wwRxnKTE2/evwHYxCxhIHFk0hxXClpdo3jqbGaJXW2L5sxaWCYxCs5CsnoWkZRaSlgWMzKsY 2XMTM3PSy402MQKD/OCW36o7GO+cEznEKM3BoiTOa711j7+QQHpiSWp2ampBalF8UWlOavEh RiYOTqkGxqyJnv7VTX9yBDeJiFXxsonvmvubf7ml0355DSWVcCn/5T26+/at7bpRdmCLPu/u O2ue1lsVtfz0DSpX43R7XjspM0VRaflH8/VrClqUjE9nHGv4IfVWRG3OjY6nzyO6FI7+WimZ 8kSxZZLe1JLCm/PknQQ0N0ve3/W+Wa47upr/7iEmG1EpJZbijERDLeai4kQAawNWgUACAAA=
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-p2psip-base.all@tools.ietf.org, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Gen-art] Gen-ART: Re-review of draft-ietf-p2psip-base-23
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Dec 2012 21:17:20 -0000

Hi Mary,

thanks for your review. I am adding Dean to this thread since he is
currently editing the document.

Cheers,

Gonzalo

On 14/12/2012 8:02 PM, Mary Barnes wrote:
> Russ asked that I re-review the updated document.
> 
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> 
> Document: draft-ietf-p2psip-base-23
> Reviewer:  Mary Barnes
> Review Date: 14 December 2012
> Re-Review started Date (-21):  28 March 2012 (was told a new version
> was coming out)
> Original Review Date (-17) : 6 August 2011
> IETF LC End Date: 22 July 2011
> 
> Summary: Not Ready.
> 
> I reviewed through section 6 of this version (section 5 of -17)
> against my comments on the -17 . Since many of my comments had not
> been addressed, I'm not going to take the time to re-review the
> remainder of the document.
> 
> I also *strongly* recommend that you ensure Henning has reviewed this
> document *before* it gets into the RFC editor's queue.  He has fairly
> strict (and quite accurate) views on grammar and structure but it
> really isn't good to have so many changes go in at AUTH48 as there is
> a risk of introducing true technical bugs or changing something that
> was carefully crafted to achieve WG consensus:
> http://www.cs.columbia.edu/~hgs/etc/writing-bugs.html
> 
> 
> Comments:
> =========
> 
> I have reviewed my previous comments on this document -17 as compared
> to the -23.  Comments from the -17 that remain are prefaced with [-17]
> 
> Major:
> ------
> 
> General:
> --[-17] The message names are used inconsistently.  The IANA registry
> has the message codes all lower case.  There are places in the
> examples and the body of the document where the _req part is missing,
> there is no "_", the first letters are Upper case, etc.  The messages
> are also used in a general sense - e.g., "MUST perform an Attach",
> which should really be stated as "MUST send an attach_req message).
> [-23]  For the latter point, Cullen responded that this isn't really
> just talking about sending a message but rather performing a function
> that results in a message being sent.
> 
> However, I still contend that there is inconsistency and the whole
> concept of an Attach function/process/whatever is not well defined.
> There are times when "attached" appears to be used purely as a verb
> rather than referring to the functionality, but it is not always
> clear.  For example, the last two sentences in section 3.4:
>    "Instead, we use the Attach request to establish a
>    connection.  Attach uses ICE [RFC5245] to establish the connection.
>    It is assumed that the reader is familiar with ICE."
> I will note that the only mention of "Attach" previously was in the
> definitions for Connection Table ("Attach handshakes") and Routing
> Table ("some peers will have Attached").  The word "Attach" is used
> with the _req or the word "request" in places like the following in
> section 3.4 (1st sentence):   "There are two cases where Attach is not
> used."  I have no idea really whether this means this Attach
> function/process is not needed or the message is not required to be
> sent.
> 
> Major - detailed:
> 
> - Section 3.4, last paragraph:  Accepting Cullen's comment that this
> text is not normative, I'll let my first set of -17 comments on this
> one go.  However, the following is still not clear to me:
> What is meant by the "specified link set" - is that referring to all
> the nearby peers or the peers+enough others?  Or is this more clearly
> (and normatively) specified elsewhere, such that a reference could be
> added.
> 
> - [-17 5.1.2] Section 6.1.2:
> -- Last paragraph (9) mixes normative text with in an example. The
> normative text needs to be separated from the example - e.g., split
> some of the sentences into the normative behavior and then the
> example. The example should be written in terms of what happens (which
> is what was done in the previous examples in this section and not what
> SHOULD, MAY or MUST happen).      For example, this sentence:
>    "Node A MUST implement an algorithm that ensures that
>    A returns a response to this request to node B with the destination
>    list [B, Z, Y, X], provided that the node to which A forwards the
>    request follows the same contract.
> should have a generic normative statement rather than saying "Node A
> MUST".  It should be something like: "A node must implement an
> algorithm that ensures it returns a response …", then the same
> sentence can be a "For example, Node A MUST…"
> 
> - [-17 5.3.2.1] Section 6.3.2.1:
> --1st paragraph: shouldn't this be normative?
> "the configuration document has a sequence number..." ->  "the
> configuration document MUST contain a sequence number which MUST be
> monotonically increasing mod 65535"
> 
> - [-17 5.3.2.2] -Section 6.3.2.2:
> --Paragraph after second structure, suggest the following changes:
> ---"the generation counters should" ->  "the generation counters SHOULD"
> ---"An implementation could use.." -> "An implementation MAY use…"
> ---"the node confirms that the generation counter matches" -> "the
> node MUST confirm that the generation counter matches"
> ---"If it does not match, it is silently dropped." -> "If it does not
> match, it MUST be silently dropped."
> 
> - [-17 5.3.3.1] Section 6.3.3.1:
> --1st para: "a request returns" -> "a request MUST return"
> --1st para: "then the message code is the response code that matches
> the request" ->
> "then the message code MUST be set to the response code that matches
> the request"
> --2nd para: "message code is set" ->  "message code MUST be set"
> 
> - [-17 5.3.4] Section 6.3.4 - needs normative language:
> --1st paragraph after GenericCertificate structure:
> ---"All signatures are formatted" -> "Alls signatures MUST be formatted"
> ---"The input structure…varies.." ->  "The input structure … MAY vary…"
> 
> - [-23] Review stops at section 6.4.2
> 
> 
> Minor:
> ------
> - idnits identifies 5 errors (downrefs).  There are also unused
> references and 22 warnings that should be reviewed - the ones, in
> particular, which should be fixed are with regards to normative
> language usage.
> 
> - While Cullen responded to this comment with an explanation, there
> was no change to clarify the text:
> - [-17] Section 1.2.1, 2nd paragraph: I don't understand the example
> as to why a single application requires multiple usages - i.e, why
> voicemail?  Isn't the intent to say that an application might need to
> use both SIP and XMPP - i.e., you wouldn't define a "usage" for an
> application, would you?
> 
> - [-17] Section 2. Some of the definitions use terms that are not yet
> defined, so that's not particularly helpful - i.e,. Attach and Update
> are used. In some cases (e.g., Connection Table), you could just
> delete the statement with the reference.
> 
> - [-17] Section 3.1, 1st para: This sentence doesn't grok because the
> concept of "overlay parameters" hasn't been mentioned before this
> section nor has the concept of a "configuration document".
>   "The overlay parameters are specified in a configuration document."
> At a minimum those terms should be defined in the terminology section
> and introduced in the intro paragraph in section 3.
> 
> - [-17] Section 3.3, last paragraph.  Add a reference to 5.4.2.4
> after "RouteQuery method"
> 
> - [-17] Section 5.1.2:
> --1st paragraph: I have no idea what the "other three cases" references.
> 
> - [-17 Section 5.3] Section 6.3:  The three parts of the messages are
> listed and the last sentence says that "The following sections
> describe the format of each part of the message", but there are 4
> sub-sections in 5.3, with the first section NOT describing one of the
> three parts of the messages.  I suggest to strike that last sentence
> and just put references to the sections in the list items for each of
> the three messages
> 
> - [-17 Section 5.6] Section 6.6:
> -- The last three paragraphs are confusing.
> ---In particular, it's not clear what algorithms are being referenced
> in this sentence:
>   "We will first define each of these algorithms, then
>    define overlay link protocols that use them."
> --- In the note paragraph, I believe "These protocols have been
> chosen…" is referring to the three overlay link protocols supported by
> RELOAD per this document.
> ---The Note to implementors paragraph seems out of context
> --- Per my next comment, I suggest to move the detailed discussion of
> future overlay link protocols to the appendix, so some of this text
> may be relevant only to that.
> 
> -[ -17 5.6.1] Section 6.6.1:  I suggest that the sub-sections in this
> section be moved to an appendix and a reference to such be added.
> 
> [-23] Did not review beyond section 6.
> 
> Nits:
> -----
> 
> - [-17] Section 2.
> --General: It would be helpful if the terms were alphabetized.
> [Note, Cullen's response was that this causes forward reference
> problems, but that's unavoidable. If the terms are alphabetized, it is
> much easier to find them. ]
> --Node: "We use the term "Node" to refer to …" -> "Refers to …" or
> something to make it more consistent with the format for the other
> terms.
> 
> - Section 6.1.1, last bullet:  "later" -> "latter"
> 
> - Section 6.1.3: Shouldn't this be "For example," rather than "I.e.,"?
>  If "I.e.," is appropriate in that those are the only routing
> algorithms which might be used, then I would suggest adjusting the
> sentence structure by using words rather than the abbreviation (it's
> debatable whether the latter is grammatically correct) to something
> like.  "This means that a node…".
> 
> - [-17 5.5.1.6] Section 6.5.1.6: Add references for SCTP and DCCP.
> 
> [-23] Did not review beyond nits identified for section 6.
> 


From ron.even.tlv@gmail.com  Sat Dec 15 23:34:55 2012
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3730521F84E8; Sat, 15 Dec 2012 23:34:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 wjfp90a-4jaB; Sat, 15 Dec 2012 23:34:54 -0800 (PST)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6A4BD21F84E7; Sat, 15 Dec 2012 23:34:53 -0800 (PST)
Received: by mail-ee0-f44.google.com with SMTP id b47so2715118eek.31 for <multiple recipients>; Sat, 15 Dec 2012 23:34:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; bh=lDGDOPjJCRWKcNG48D1WIzSlzziQH4uEQZsASR8tF00=; b=uWlVKRsQVQAphHR9FohG3sLfRfO0m6Kq89MgEs0R2sAHf8hxHD6VeBh1siY6s3dwY6 85hoKkSoAegSJA+K8mbA4wfNnZ7wP5w2+kc7/P67P0ateqhAmbhuKNeGt/81af9nYfkc QYOOyfJN3JBY4txossT8Uhgc5y4R7+NrnFTlPSa+0tKSzd0V/4ly1OqbADyda57hoQ80 2Pmaz23HsgKU8fwIYLA3Nr3RuI6ZfmQ0KLbbKEVg1PUj/Tjq/I8eWlcDzrOpOW9dNoII I0x53CQsBeDWUcs/AWpM/47dZw9d7BR7GsDZ5HIW/hoqt1bsKBEYaI0GmVCgGEdDMSWV X+FQ==
Received: by 10.14.219.3 with SMTP id l3mr30237826eep.5.1355643292542; Sat, 15 Dec 2012 23:34:52 -0800 (PST)
Received: from RoniE (bzq-79-176-185-176.red.bezeqint.net. [79.176.185.176]) by mx.google.com with ESMTPS id 46sm20727493eeg.4.2012.12.15.23.34.48 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 15 Dec 2012 23:34:51 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <ietf@ietf.org>, <draft-ietf-appsawg-json-patch.all@tools.ietf.org>
Date: Sun, 16 Dec 2012 09:32:03 +0200
Message-ID: <023301cddb5f$73eb02d0$5bc10870$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0234_01CDDB70.37749620"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac3bX3EjFnMrNpEpREWWeLmjX+vykQ==
Content-Language: en-us
Cc: gen-art@ietf.org
Subject: [Gen-art] Gen-ART LC review of draft-ietf-appsawg-json-patch-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Dec 2012 07:34:55 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0234_01CDDB70.37749620
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

 

Please resolve these comments along with any other Last Call comments you
may receive.

 

Document: draft-ietf-appsawg-json-patch-08

Reviewer: Roni Even

Review Date:2012-12-16

IETF LC End Date: 2012-12-25

IESG Telechat date: 2013-1-10

 

Summary: This draft is almost  ready for publication.

 

 

Major issues:

 

Minor issues:

1.       The document has as the intended status "Informational" while the
last call says that the intended status is proposed standard?

 

 

Nits/editorial comments:

1.	In the IANA section the "Encoding considerations:  binary". I
noticed that RFC 4627 has a broader description:

"Encoding considerations: 8bit if UTF-8; binary if UTF-16 or UTF-32

JSON may be represented using UTF-8, UTF-16, or UTF-32.  When JSON is
written in UTF-8, JSON is 8bit compatible.  When JSON is written in UTF-16
or UTF-32, the binary content-transfer-encoding   must be used."

 

 


------=_NextPart_000_0234_01CDDB70.37749620
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:789938108;
	mso-list-type:hybrid;
	mso-list-template-ids:-835678812 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1
	{mso-list-id:1666859179;
	mso-list-type:hybrid;
	mso-list-template-ids:560766234 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK1"></a><a name=3D"OLE_LINK2">I am the assigned Gen-ART =
reviewer for this draft. For background on Gen-ART, please see the FAQ =
at &lt;</a><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Please resolve these comments along with any other =
Last Call comments you may receive.<o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>draft-ietf-=
appsawg-json-patch-08</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2012&#8211;12&#8211;16<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2012&#8211;12&#8211;25<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: 2013-1-10<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is almost&nbsp; ready for publication</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>.<o:p></o:p=
></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>The =
document has as the intended status &#8220;Informational&#8221; while =
the last call says that the intended status is proposed =
standard?<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><ol style=3D'margin-top:0in' start=3D1 =
type=3D1><li class=3DMsoNormal style=3D'mso-list:l0 level1 lfo2'>In the =
IANA section the &#8220;Encoding considerations:&nbsp; binary&#8221;. I =
noticed that RFC 4627 has a broader description:<o:p></o:p></li></ol><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin=
-left:.5in;margin-bottom:.0001pt;line-height:normal'>&#8220;Encoding =
considerations: 8bit if UTF-8; binary if UTF-16 or =
UTF-32<o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin=
-left:.5in;margin-bottom:.0001pt;line-height:normal'>JSON may be =
represented using UTF-8, UTF-16, or UTF-32.&nbsp; When JSON is written =
in UTF-8, JSON is 8bit compatible.&nbsp; When JSON is written in UTF-16 =
or UTF-32, the binary content-transfer-encoding&nbsp;&nbsp; must be =
used.&#8221;<o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin=
-left:.5in;margin-bottom:.0001pt;line-height:normal'><o:p>&nbsp;</o:p></p=
><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0234_01CDDB70.37749620--


From ron.even.tlv@gmail.com  Sun Dec 16 14:59:59 2012
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A43F21F863B; Sun, 16 Dec 2012 14:59:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 0ssmhKEvjmlD; Sun, 16 Dec 2012 14:59:58 -0800 (PST)
Received: from mail-ea0-f172.google.com (mail-ea0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1A21521F8635; Sun, 16 Dec 2012 14:59:57 -0800 (PST)
Received: by mail-ea0-f172.google.com with SMTP id a1so2149598eaa.31 for <multiple recipients>; Sun, 16 Dec 2012 14:59:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; bh=4wn3IOb3NI2Fe3DGv/8NajVs1/ivCeLBXNe+YCXUWHI=; b=NXvXheB/yBz9OsBFBgT7kg4eUHtgAQ8InAyNPGXy+llQU3Xtyc4i7xrzgkadzsK/Vb rNchpbqWgLrGLxwPEc+K1he9bxAaCRuKTt6hYFP38OC/41cg9r00nvDh87aEkPLxgNIf FW5SgDqCvMooW85dMydjlmxxCvl4eIDMfXHBiCi+FR/KYmf7+SKQfupLOr+oCAOi5Dps mHPi7fXWhR5OOgjcl5ZH6qgzu95jIy7Usi/qABKSi1Gl5GDuF8BSvaaM/XuHMGEC3duS es07jjK6OCeoN+Tj/DMeTsmsHoZyr9NychXWBvKNoZgaiOlmQplJaN/zNwKGGAcr6ZO+ c1aQ==
Received: by 10.14.0.133 with SMTP id 5mr35096112eeb.29.1355698797268; Sun, 16 Dec 2012 14:59:57 -0800 (PST)
Received: from RoniE (bzq-79-176-185-176.red.bezeqint.net. [79.176.185.176]) by mx.google.com with ESMTPS id f49sm25280183eep.12.2012.12.16.14.59.53 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 16 Dec 2012 14:59:56 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <ietf@ietf.org>
Date: Mon, 17 Dec 2012 00:57:08 +0200
Message-ID: <026d01cddbe0$afb19320$0f14b960$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_026E_01CDDBF1.733AFF60"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac3b4KyqaBiVYCC7SBib9omClLXGWA==
Content-Language: en-us
Cc: gen-art@ietf.org, draft-daboo-ical-vcard-parameter-encoding.all@tools.ietf.org
Subject: [Gen-art] Gen-ART LC review of draft-daboo-ical-vcard-parameter-encoding-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Dec 2012 22:59:59 -0000

This is a multipart message in MIME format.

------=_NextPart_000_026E_01CDDBF1.733AFF60
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

 

Please resolve these comments along with any other Last Call comments you
may receive.

 

Document: draft-daboo-ical-vcard-parameter-encoding-02

Reviewer: Roni Even

Review Date:2012-12-17

IETF LC End Date: 2012-12-14

IESG Telechat date: 

 

Summary: This draft is ready for publication as Standard track RFC.

 

 

Major issues:

 

Minor issues:

 

Nits/editorial comments:

 


------=_NextPart_000_026E_01CDDBF1.733AFF60
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK1"></a><a name=3D"OLE_LINK2">I am the assigned Gen-ART =
reviewer for this draft. For background on Gen-ART, please see the FAQ =
at &lt;</a><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Please resolve these comments along with any other =
Last Call comments you may receive.<o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span style=3D'font-family:"Courier =
New"'>draft-daboo-ical-vcard-parameter-encoding-02</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2012&#8211;12&#8211;17<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2012&#8211;12&#8211;14<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: <o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is ready for publication as Standard track RFC</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>.<o:p></o:p=
></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_026E_01CDDBF1.733AFF60--


From mnot@mnot.net  Sun Dec 16 19:25:48 2012
Return-Path: <mnot@mnot.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FC2C21F8554; Sun, 16 Dec 2012 19:25:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.965
X-Spam-Level: 
X-Spam-Status: No, score=-103.965 tagged_above=-999 required=5 tests=[AWL=-1.366, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 4q7yZIEu835E; Sun, 16 Dec 2012 19:25:47 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id 1924521F89AC; Sun, 16 Dec 2012 19:25:46 -0800 (PST)
Received: from [192.168.1.80] (unknown [118.209.33.170]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 40484509B5; Sun, 16 Dec 2012 22:25:43 -0500 (EST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <023301cddb5f$73eb02d0$5bc10870$@gmail.com>
Date: Mon, 17 Dec 2012 14:25:40 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <CA1BECA0-5084-4833-8EA8-EC507C7913E8@mnot.net>
References: <023301cddb5f$73eb02d0$5bc10870$@gmail.com>
To: Roni Even <ron.even.tlv@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: draft-ietf-appsawg-json-patch.all@tools.ietf.org, gen-art@ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-appsawg-json-patch-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Dec 2012 03:25:48 -0000

Both fixed in SVN; thanks for the review.


On 16/12/2012, at 6:32 PM, Roni Even <ron.even.tlv@gmail.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART, please see the FAQ at =
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> =20
>=20
> Please resolve these comments along with any other Last Call comments =
you may receive.
>=20
> =20
> Document: draft-ietf-appsawg-json-patch-08
> Reviewer: Roni Even
> Review Date:2012=9612=9616
> IETF LC End Date: 2012=9612=9625
> IESG Telechat date: 2013-1-10
> =20
> Summary: This draft is almost  ready for publication.
> =20
> =20
> Major issues:
> =20
> Minor issues:
> 1.       The document has as the intended status =93Informational=94 =
while the last call says that the intended status is proposed standard?
> =20
> =20
> Nits/editorial comments:
>=20
> 	=95 In the IANA section the =93Encoding considerations:  =
binary=94. I noticed that RFC 4627 has a broader description:
> =93Encoding considerations: 8bit if UTF-8; binary if UTF-16 or UTF-32
> JSON may be represented using UTF-8, UTF-16, or UTF-32.  When JSON is =
written in UTF-8, JSON is 8bit compatible.  When JSON is written in =
UTF-16 or UTF-32, the binary content-transfer-encoding   must be used.=94
> =20
> =20
>=20

--
Mark Nottingham   http://www.mnot.net/




From miguel.a.garcia@ericsson.com  Mon Dec 17 05:41:30 2012
Return-Path: <miguel.a.garcia@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D7CF21F8555 for <gen-art@ietfa.amsl.com>; Mon, 17 Dec 2012 05:41:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.068
X-Spam-Level: 
X-Spam-Status: No, score=-6.068 tagged_above=-999 required=5 tests=[AWL=0.181,  BAYES_00=-2.599, HELO_EQ_SE=0.35, 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 bjWWGtlBTvSH for <gen-art@ietfa.amsl.com>; Mon, 17 Dec 2012 05:41:30 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id C2F7C21F8AC7 for <gen-art@ietf.org>; Mon, 17 Dec 2012 05:41:29 -0800 (PST)
X-AuditID: c1b4fb2d-b7f316d0000028db-ae-50cf21084419
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id C3.1E.10459.8012FC05; Mon, 17 Dec 2012 14:41:28 +0100 (CET)
Received: from [159.107.24.196] (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.94) with Microsoft SMTP Server id 8.3.279.1; Mon, 17 Dec 2012 14:41:28 +0100
Message-ID: <50CF2106.3040900@ericsson.com>
Date: Mon, 17 Dec 2012 14:41:26 +0100
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Vincent Roca <vincent.roca@inria.fr>,  Mathieu Cunche <mathieu.cunche@inria.fr>, Jerome Lacan <jerome.lacan@isae.fr>,  Amine Bouabdallah <abouabdallah@cdta.dz>, Kazuhisa Matsuzono <kazuhisa@sfc.wide.ad.jp>,  Martin Stiemerling <martin.stiemerling@neclab.eu>, fecframe-chairs@tools.ietf.org
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrCLMWRmVeSWpSXmKPExsUyM+JvjS6H4vkAg/U7FCyuvVnIaHHzUgur xdVXn1ksunuvsVicetjDYtHRd5XN4tymOIueVf0sDhwed6ffYfFYsuQnk8ekF4dYPCafa2Tx mHHsJbvHxdfXmT2+XP7MFsAexWWTkpqTWZZapG+XwJVxp3M7a8FNtorpx0+yNTDuZu1i5OSQ EDCROLLvJjuELSZx4d56ti5GLg4hgZOMEpPnPWaBcNYwSmxovA9WxSugLXF+xVuwbhYBVYkL d/6ygNhsAuYSrRs3gtWICoRIXP/+iBGiXlDi5MwnYINEBDYySTS8+MwGkmAW0Jc48mc3E4gt LGAtsXjuRCaIuK3EhTnXWSBseYntb+cwg9hCApoSk28uZZ7AyD8LydxZSFpmIWlZwMi8ipE9 NzEzJ73ccBMjMKQPbvmtu4Px1DmRQ4zSHCxK4rxcSfv9hQTSE0tSs1NTC1KL4otKc1KLDzEy cXBKNTBqBx9PT4jR7ty9NXp72GPjbX8+Xzgetrv2jNVHFTnxRblbgpMuuqlUXes2MF56asVR USPeF1wsLfrnz91b9pDV1btohdK51XqrprNMj36jdmVehPcM72Cxrtrfun3eG9MaI+Nd58zS vG637teEnq0HFZaauv+t+3NS3+TEirTftz4k3LJ33XJdiaU4I9FQi7moOBEA0c25uTcCAAA=
Cc: General Area Review Team <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-fecframe-simple-rs-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Dec 2012 13:41:30 -0000

I have been selected as the General Area Review Team (Gen-ART)
reviewer for this draft. For background on Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>

Please resolve these comments along with any other comments you may receive.

Document: draft-ietf-fecframe-simple-rs-05
Reviewer: Miguel Garcia <Miguel.A.Garcia@ericsson.com>
Review Date: 2012-12-17
IETF LC End Date: 2012-12-22
IESG Telechat date:

Summary: This document is ready for publication as a standards track RFC.

Major issues: none

Minor issues: none

Nits/editorial comments:

I reviewed version -4 of this document, and at that time I had a couple 
of minor or editorial issues. All of them have been addressed in version 
05, so, the document is ready.

/Miguel
-- 
Miguel A. Garcia
+34-91-339-3608
Ericsson Spain


From gjshep@gmail.com  Mon Dec 17 07:32:33 2012
Return-Path: <gjshep@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4083B21F8B06 for <gen-art@ietfa.amsl.com>; Mon, 17 Dec 2012 07:32:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.203
X-Spam-Level: 
X-Spam-Status: No, score=-102.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1,  USER_IN_WHITELIST=-100]
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 5HZ5gZprwC+T for <gen-art@ietfa.amsl.com>; Mon, 17 Dec 2012 07:32:32 -0800 (PST)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 86E4D21F8B04 for <gen-art@ietf.org>; Mon, 17 Dec 2012 07:32:32 -0800 (PST)
Received: by mail-da0-f44.google.com with SMTP id z20so2590186dae.31 for <gen-art@ietf.org>; Mon, 17 Dec 2012 07:32:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to; bh=yMheSiNem9SrBjciKr2bjOuuvYr+kkKvYHjLLjTdrU4=; b=c/nee9qAPMPflFVkNgA791vcJG4NIIO36E7V8veiSCkDVYLNFh7gBzwG1UeCVGsJAw AF1dBHyP/WoaZNgQ3CrNI0dX/uCNJcqpwSdfUB4kc0J/Vanjm2GvVHISdbOL21ngz6Ps fmx46xt7RwnfsYhVzsRLqJXlaAFEQnTy/qJPF1wGrnJxCpPvxGJO0z3djdfZpAZ0COCu 2ktnk4cLNe5Xp5PmC01YeTBNbXYuFZ1KQRt7K8muuZsmO+gc3d4rFlAD4HUrhYu15WKn 6wmzELrDilkqyT+YxJTyqHqDS8gipk2et5nL5Xpqs+BKmm9zdyY1q/M6PQGSsHEV+kSS T8pQ==
Received: by 10.68.227.73 with SMTP id ry9mr43976018pbc.73.1355758352308; Mon, 17 Dec 2012 07:32:32 -0800 (PST)
Received: from [10.91.214.211] (mobile-166-137-215-068.mycingular.net. [166.137.215.68]) by mx.google.com with ESMTPS id t1sm8755890paw.11.2012.12.17.07.32.28 (version=SSLv3 cipher=OTHER); Mon, 17 Dec 2012 07:32:31 -0800 (PST)
References: <50CF2106.3040900@ericsson.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <50CF2106.3040900@ericsson.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <9DD1DF4A-97DC-4B04-BC49-7502DED92A6F@gmail.com>
X-Mailer: iPhone Mail (10A523)
From: Greg Shepherd <gjshep@gmail.com>
Date: Mon, 17 Dec 2012 07:32:24 -0800
To: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
X-Mailman-Approved-At: Mon, 17 Dec 2012 07:36:57 -0800
Cc: Mathieu Cunche <mathieu.cunche@inria.fr>, "fecframe-chairs@tools.ietf.org" <fecframe-chairs@tools.ietf.org>, Vincent Roca <vincent.roca@inria.fr>, Kazuhisa Matsuzono <kazuhisa@sfc.wide.ad.jp>, Jerome Lacan <jerome.lacan@isae.fr>, Amine Bouabdallah <abouabdallah@cdta.dz>, Martin Stiemerling <martin.stiemerling@neclab.eu>, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-fecframe-simple-rs-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Dec 2012 15:32:33 -0000

Thanks Miguel!

Greg

Sent from my iPhone

On Dec 17, 2012, at 5:41, "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com> w=
rote:

> I have been selected as the General Area Review Team (Gen-ART)
> reviewer for this draft. For background on Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>=20
> Please resolve these comments along with any other comments you may receiv=
e.
>=20
> Document: draft-ietf-fecframe-simple-rs-05
> Reviewer: Miguel Garcia <Miguel.A.Garcia@ericsson.com>
> Review Date: 2012-12-17
> IETF LC End Date: 2012-12-22
> IESG Telechat date:
>=20
> Summary: This document is ready for publication as a standards track RFC.
>=20
> Major issues: none
>=20
> Minor issues: none
>=20
> Nits/editorial comments:
>=20
> I reviewed version -4 of this document, and at that time I had a couple of=
 minor or editorial issues. All of them have been addressed in version 05, s=
o, the document is ready.
>=20
> /Miguel
> --=20
> Miguel A. Garcia
> +34-91-339-3608
> Ericsson Spain
>=20

From pbryan@anode.ca  Mon Dec 17 09:17:29 2012
Return-Path: <pbryan@anode.ca>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1B0C21F8B6E; Mon, 17 Dec 2012 09:17:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 Vc6FeGE8uFjq; Mon, 17 Dec 2012 09:17:27 -0800 (PST)
Received: from maple.anode.ca (maple.anode.ca [72.14.183.184]) by ietfa.amsl.com (Postfix) with ESMTP id 5028F21F8B32; Mon, 17 Dec 2012 09:17:27 -0800 (PST)
Received: from [10.126.22.61] (nat-204-14-239-210-sfo.net.salesforce.com [204.14.239.210]) by maple.anode.ca (Postfix) with ESMTPSA id 575FB6A3A; Mon, 17 Dec 2012 17:17:26 +0000 (UTC)
From: "Paul C. Bryan" <pbryan@anode.ca>
To: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CA1BECA0-5084-4833-8EA8-EC507C7913E8@mnot.net>
References: <023301cddb5f$73eb02d0$5bc10870$@gmail.com> <CA1BECA0-5084-4833-8EA8-EC507C7913E8@mnot.net>
Content-Type: multipart/alternative; boundary="=-vVdoXRaiQCXJBx99gYas"
Date: Mon, 17 Dec 2012 09:17:19 -0800
Message-ID: <1355764639.3017.8.camel@pbryan-wsl.internal.salesforce.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.3 
X-Mailman-Approved-At: Mon, 17 Dec 2012 09:29:14 -0800
Cc: draft-ietf-appsawg-json-patch.all@tools.ietf.org, gen-art@ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-appsawg-json-patch-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Dec 2012 17:17:29 -0000

--=-vVdoXRaiQCXJBx99gYas
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit

Incidentally, early (draft-pbryan-json-patch-*) drafts were aligned with
JSON; later feedback when adopted by the IETF APPSAWG changed it to
binary (starting in draft-ietf-appsawg-json-patch-00). The grounds for
this was a consensus that the JSON draft was wrong to have made it 8bit
for UTF-8.

Paul

On Mon, 2012-12-17 at 14:25 +1100, Mark Nottingham wrote:

> Both fixed in SVN; thanks for the review.
> 
> 
> On 16/12/2012, at 6:32 PM, Roni Even <ron.even.tlv@gmail.com> wrote:
> 
> > I am the assigned Gen-ART reviewer for this draft. For background on Gen-ART, please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> > 
> >  
> > 
> > Please resolve these comments along with any other Last Call comments you may receive.
> > 
> >  
> > Document: draft-ietf-appsawg-json-patch-08
> > Reviewer: Roni Even
> > Review Date:2012â€“12â€“16
> > IETF LC End Date: 2012â€“12â€“25
> > IESG Telechat date: 2013-1-10
> >  
> > Summary: This draft is almost  ready for publication.
> >  
> >  
> > Major issues:
> >  
> > Minor issues:
> > 1.       The document has as the intended status â€œInformationalâ€� while the last call says that the intended status is proposed standard?
> >  
> >  
> > Nits/editorial comments:
> > 
> > 	â€¢ In the IANA section the â€œEncoding considerations:  binaryâ€�. I noticed that RFC 4627 has a broader description:
> > â€œEncoding considerations: 8bit if UTF-8; binary if UTF-16 or UTF-32
> > JSON may be represented using UTF-8, UTF-16, or UTF-32.  When JSON is written in UTF-8, JSON is 8bit compatible.  When JSON is written in UTF-16 or UTF-32, the binary content-transfer-encoding   must be used.â€�
> >  
> >  
> > 
> 
> --
> Mark Nottingham   http://www.mnot.net/
> 
> 
> 



--=-vVdoXRaiQCXJBx99gYas
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.28.3">
</HEAD>
<BODY>
Incidentally, early (draft-pbryan-json-patch-*) drafts were aligned with JSON; later feedback when adopted by the IETF APPSAWG changed it to binary (starting in draft-ietf-appsawg-json-patch-00). The grounds for this was a consensus that the JSON draft was wrong to have made it 8bit for UTF-8.<BR>
<BR>
Paul<BR>
<BR>
On Mon, 2012-12-17 at 14:25 +1100, Mark Nottingham wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
Both fixed in SVN; thanks for the review.


On 16/12/2012, at 6:32 PM, Roni Even &lt;<A HREF="mailto:ron.even.tlv@gmail.com">ron.even.tlv@gmail.com</A>&gt; wrote:

&gt; I am the assigned Gen-ART reviewer for this draft. For background on Gen-ART, please see the FAQ at &lt;<A HREF="http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</A>&gt;.
&gt; 
&gt;  
&gt; 
&gt; Please resolve these comments along with any other Last Call comments you may receive.
&gt; 
&gt;  
&gt; Document: draft-ietf-appsawg-json-patch-08
&gt; Reviewer: Roni Even
&gt; Review Date:2012&#8211;12&#8211;16
&gt; IETF LC End Date: 2012&#8211;12&#8211;25
&gt; IESG Telechat date: 2013-1-10
&gt;  
&gt; Summary: This draft is almost  ready for publication.
&gt;  
&gt;  
&gt; Major issues:
&gt;  
&gt; Minor issues:
&gt; 1.       The document has as the intended status &#8220;Informational&#8221; while the last call says that the intended status is proposed standard?
&gt;  
&gt;  
&gt; Nits/editorial comments:
&gt; 
&gt; 	&#8226; In the IANA section the &#8220;Encoding considerations:  binary&#8221;. I noticed that RFC 4627 has a broader description:
&gt; &#8220;Encoding considerations: 8bit if UTF-8; binary if UTF-16 or UTF-32
&gt; JSON may be represented using UTF-8, UTF-16, or UTF-32.  When JSON is written in UTF-8, JSON is 8bit compatible.  When JSON is written in UTF-16 or UTF-32, the binary content-transfer-encoding   must be used.&#8221;
&gt;  
&gt;  
&gt; 

--
Mark Nottingham   <A HREF="http://www.mnot.net/">http://www.mnot.net/</A>



</PRE>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>

--=-vVdoXRaiQCXJBx99gYas--


From mahoney@nostrum.com  Mon Dec 17 13:56:11 2012
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4459C21F89C0 for <gen-art@ietfa.amsl.com>; Mon, 17 Dec 2012 13:56:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
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 WevFUKBdOAuo for <gen-art@ietfa.amsl.com>; Mon, 17 Dec 2012 13:56:06 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id B3A5C21F89CA for <gen-art@ietf.org>; Mon, 17 Dec 2012 13:56:05 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-45-100.dllstx.fios.verizon.net [173.71.45.100]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qBHLu2JR068724 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Mon, 17 Dec 2012 15:56:04 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <50CF94F1.9070609@nostrum.com>
Date: Mon, 17 Dec 2012 15:56:01 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 173.71.45.100 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2012-12-17
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Dec 2012 21:56:11 -0000

Hi all,

The following reviewers have assignments:


Reviewer           LC end      Draft

Ben Campbell      2013-01-07 draft-ietf-dhc-relay-id-suboption-11 *

Brian Carpenter   2013-01-14 draft-ietf-sidr-rpki-rtr-protocol-mib-04

Christer Holmberg 2013-01-04 draft-ietf-mpls-tp-itu-t-identifiers-06

* On the 2013-01-10 telechat


I have made the assignments in the review tool:
http://art.tools.ietf.org/tools/art/genart/


The standard template is included below.

Thanks,

Jean

-------------------------------------------------------------------

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

From mnot@mnot.net  Mon Dec 17 16:10:47 2012
Return-Path: <mnot@mnot.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7446121F86F5; Mon, 17 Dec 2012 16:10:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.753
X-Spam-Level: 
X-Spam-Status: No, score=-103.753 tagged_above=-999 required=5 tests=[AWL=-1.154, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 uOZI75UR5Lx2; Mon, 17 Dec 2012 16:10:46 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id B326A21F86B8; Mon, 17 Dec 2012 16:10:46 -0800 (PST)
Received: from [192.168.1.80] (unknown [118.209.33.170]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 3EA6C509B5; Mon, 17 Dec 2012 19:10:43 -0500 (EST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <1355764639.3017.8.camel@pbryan-wsl.internal.salesforce.com>
Date: Tue, 18 Dec 2012 11:10:41 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <A474180D-347E-44C6-8651-225CC05EBFC1@mnot.net>
References: <023301cddb5f$73eb02d0$5bc10870$@gmail.com> <CA1BECA0-5084-4833-8EA8-EC507C7913E8@mnot.net> <1355764639.3017.8.camel@pbryan-wsl.internal.salesforce.com>
To: Paul C. Bryan <pbryan@anode.ca>
X-Mailer: Apple Mail (2.1499)
Cc: draft-ietf-appsawg-json-patch.all@tools.ietf.org, gen-art@ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-appsawg-json-patch-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Dec 2012 00:10:47 -0000

Ah, thanks for the context; will change it back.


On 18/12/2012, at 4:17 AM, Paul C. Bryan <pbryan@anode.ca> wrote:

> Incidentally, early (draft-pbryan-json-patch-*) drafts were aligned =
with JSON; later feedback when adopted by the IETF APPSAWG changed it to =
binary (starting in draft-ietf-appsawg-json-patch-00). The grounds for =
this was a consensus that the JSON draft was wrong to have made it 8bit =
for UTF-8.
>=20
> Paul
>=20
> On Mon, 2012-12-17 at 14:25 +1100, Mark Nottingham wrote:
>> Both fixed in SVN; thanks for the review.
>>=20
>>=20
>> On 16/12/2012, at 6:32 PM, Roni Even <
>> ron.even.tlv@gmail.com
>> > wrote:
>>=20
>> > I am the assigned Gen-ART reviewer for this draft. For background =
on Gen-ART, please see the FAQ at <
>> http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq
>> >.
>> >=20
>> > =20
>> >=20
>> > Please resolve these comments along with any other Last Call =
comments you may receive.
>> >=20
>> > =20
>> > Document: draft-ietf-appsawg-json-patch-08
>> > Reviewer: Roni Even
>> > Review Date:2012=9612=9616
>> > IETF LC End Date: 2012=9612=9625
>> > IESG Telechat date: 2013-1-10
>> > =20
>> > Summary: This draft is almost  ready for publication.
>> > =20
>> > =20
>> > Major issues:
>> > =20
>> > Minor issues:
>> > 1.       The document has as the intended status =93Informational=94 =
while the last call says that the intended status is proposed standard?
>> > =20
>> > =20
>> > Nits/editorial comments:
>> >=20
>> > 	=95 In the IANA section the =93Encoding considerations:  =
binary=94. I noticed that RFC 4627 has a broader description:
>> > =93Encoding considerations: 8bit if UTF-8; binary if UTF-16 or =
UTF-32
>> > JSON may be represented using UTF-8, UTF-16, or UTF-32.  When JSON =
is written in UTF-8, JSON is 8bit compatible.  When JSON is written in =
UTF-16 or UTF-32, the binary content-transfer-encoding   must be used.=94
>> > =20
>> > =20
>> >=20
>>=20
>> --
>> Mark Nottingham  =20
>> http://www.mnot.net/
>>=20
>>=20
>>=20
>>=20
>>=20
>=20

--
Mark Nottingham   http://www.mnot.net/




From mahoney@nostrum.com  Tue Dec 18 11:08:52 2012
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A06021F8596 for <gen-art@ietfa.amsl.com>; Tue, 18 Dec 2012 11:08:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
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 TTmiPY9PVwPI for <gen-art@ietfa.amsl.com>; Tue, 18 Dec 2012 11:08:51 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id A317B21F8594 for <gen-art@ietf.org>; Tue, 18 Dec 2012 11:08:51 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-45-100.dllstx.fios.verizon.net [173.71.45.100]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qBIJ8oJ3024083 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Tue, 18 Dec 2012 13:08:50 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <50D0BF42.6030508@nostrum.com>
Date: Tue, 18 Dec 2012 13:08:50 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 173.71.45.100 is authenticated by a trusted mechanism)
Subject: [Gen-art] Review assignment spreadsheets are available
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Dec 2012 19:08:52 -0000

Hi all,

The spreadsheets are updated and available:

http://wiki.tools.ietf.org/dav/genart/gen-art.html
http://wiki.tools.ietf.org/dav/genart/gen-art-by-reviewer.html


I hadn't been able to upload files because the WebDAV lock database was 
lost when the machine went down last week. Henrik has set things back up 
again. Please let me know if you spot any problems.

Thanks,

Jean


From ben@nostrum.com  Tue Dec 18 12:14:48 2012
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACB7521F86D6; Tue, 18 Dec 2012 12:14:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.445
X-Spam-Level: 
X-Spam-Status: No, score=-102.445 tagged_above=-999 required=5 tests=[AWL=0.155, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
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 fpf4p2m+Gs-U; Tue, 18 Dec 2012 12:14:48 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 2764B21F85D1; Tue, 18 Dec 2012 12:14:47 -0800 (PST)
Received: from [10.0.1.14] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qBIKEk7J031269 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 18 Dec 2012 14:14:47 -0600 (CST) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Tue, 18 Dec 2012 14:14:49 -0600
Message-Id: <AEDD0F1A-EA31-4C3A-B1BF-BD16C9196740@nostrum.com>
To: "draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org" <draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
Received-SPF: pass (nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
Subject: [Gen-art] Gen-ART Telechat Review of draft-ietf-karp-routing-tcp-analysis-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Dec 2012 20:14:48 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
< http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document: draft-ietf-karp-routing-tcp-analysis-07
Reviewer: Ben Campbell
Review Date: 2012-12-18
IESG Telechat date: 2012-12-20

Summary: Ready for publication as an informational RFC. There are still =
a couple of nits that might be worth consideration prior to final =
publication.

Note: This review is incremental to my review of version 05 at last =
call. All of my comments in that review have been resolved except as =
described in this message.

** Major issues:

None

** Minor issues:

None

** Nits/editorial comments:

-- The 2119 paragraph was removed, but there's still an orphaned 2119 =
entry in the informational reference section.

-- There's a new IANA considerations section. However, I suggest it =
contain a full sentence to the effect of "This document makes no =
requests of IANA" rather than simply "None".  (OTOH, this may get =
removed before final publication anyway...)



From vkg@bell-labs.com  Tue Dec 18 12:22:37 2012
Return-Path: <vkg@bell-labs.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 470E721F8878 for <gen-art@ietfa.amsl.com>; Tue, 18 Dec 2012 12:22:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.877
X-Spam-Level: 
X-Spam-Status: No, score=-108.877 tagged_above=-999 required=5 tests=[AWL=1.722, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 wW3pi7gSgC-l for <gen-art@ietfa.amsl.com>; Tue, 18 Dec 2012 12:22:36 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 8F60521F885C for <gen-art@ietf.org>; Tue, 18 Dec 2012 12:22:36 -0800 (PST)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id qBIKMShY010737 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 18 Dec 2012 14:22:28 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id qBIKMQfM029045 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 18 Dec 2012 14:22:27 -0600
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id qBIKMMVq002381; Tue, 18 Dec 2012 14:22:22 -0600 (CST)
Message-ID: <50D0D0E3.8030909@bell-labs.com>
Date: Tue, 18 Dec 2012 14:24:03 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: draft-ietf-oauth-assertions@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10
Cc: General Area Review Team <gen-art@ietf.org>, oauth-chairs@tools.ietf.org, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: [Gen-art] Gen-ART review of draft-ietf-oauth-assertions-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Dec 2012 20:22:37 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-oauth-assertions-08
Reviewer: Vijay K. Gurbani
Review Date: Dec-18-2012
IETF LC End Date: Dec-24-2012
IESG Telechat date: Unknown

This document is ready as a Proposed Standard.

Major: 0
Minor: 0
Nits: 0

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web:   http://ect.bell-labs.com/who/vkg/

From ben@nostrum.com  Tue Dec 18 14:50:13 2012
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39C0021E8047; Tue, 18 Dec 2012 14:50:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.46
X-Spam-Level: 
X-Spam-Status: No, score=-102.46 tagged_above=-999 required=5 tests=[AWL=0.140, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
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 Y2oNf1kfmyj3; Tue, 18 Dec 2012 14:50:12 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id F0EE021E8045; Tue, 18 Dec 2012 14:50:11 -0800 (PST)
Received: from [10.0.1.14] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qBIMo6lw048047 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 18 Dec 2012 16:50:08 -0600 (CST) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <50D0EA56.3050308@inex.ie>
Date: Tue, 18 Dec 2012 16:50:08 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <566F175C-1DD4-414A-AB7D-27BF33156694@nostrum.com>
References: <AEDD0F1A-EA31-4C3A-B1BF-BD16C9196740@nostrum.com> <50D0EA56.3050308@inex.ie>
To: Nick Hilliard <nick@inex.ie>
X-Mailer: Apple Mail (2.1499)
Received-SPF: pass (nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org" <draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat Review of draft-ietf-karp-routing-tcp-analysis-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Dec 2012 22:50:13 -0000

I think Nick's email was a review of the document in general, rather =
than commentary on my review in particular. But since it was addressed =
to me, I do have one comment in response:

On Dec 18, 2012, at 4:12 PM, Nick Hilliard <nick@inex.ie> wrote:

> On 18/12/2012 20:14, Ben Campbell wrote:
>> ** Nits/editorial comments:
>>=20
>> -- The 2119 paragraph was removed, but there's still an orphaned 2119 =
entry in the informational reference section.
>=20
> I'm not sure that this was a good idea.  There are a lot of "has to"s =
in
> this text, and it's not clear to me whether they are phrased like that =
as a
> way of getting around 2119, or what's going on.  Whatever the reason, =
"has
> to" sounds very informal and probably not suitable for a document like
> this.  Could we have some clarification as to why "has to" doesn't =
mean
> "MUST" (or even "SHOULD").

I don't think so. This draft does not establish a standard, or define a =
protocol. While I don't speak for the authors, I don't think it's =
intended to make normative statements about anything. The language is =
descriptive, not prescriptive.

(I agree "has to" is an awkward substitute for the non-normative "must". =
I agree that "must" should generally be avoided when there can be =
confusion about the normativeness of a statement. I'm not sure that's =
the case here, since the whole doc is non-normative. And I think we =
could find better language even when the confusion is possible.)




From meral.shirazipour@ericsson.com  Tue Dec 18 22:13:42 2012
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88BAC21F8480 for <gen-art@ietfa.amsl.com>; Tue, 18 Dec 2012 22:13:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 exquVnrwRUVv for <gen-art@ietfa.amsl.com>; Tue, 18 Dec 2012 22:13:41 -0800 (PST)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id 3E2C021F84E0 for <gen-art@ietf.org>; Tue, 18 Dec 2012 22:13:40 -0800 (PST)
Received: from EUSAAHC008.ericsson.se ([147.117.188.96]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id qBJ6Dcdd028192 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 19 Dec 2012 00:13:39 -0600
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.02.0318.004; Wed, 19 Dec 2012 01:13:38 -0500
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "draft-ietf-v6ops-icp-guidance.all@tools.ietf.org" <draft-ietf-v6ops-icp-guidance.all@tools.ietf.org>
Thread-Topic: Gen-ART Last Call review of draft-ietf-v6ops-icp-guidance-04
Thread-Index: Ac3dr7YN5094nK67Tc6ETP3bexvDAQ==
Date: Wed, 19 Dec 2012 06:13:36 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A036B4E@eusaamb107.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.135]
Content-Type: multipart/alternative; boundary="_000_ABCAA4EF18F17B4FB619EA93DEF7939A036B4Eeusaamb107ericsso_"
MIME-Version: 1.0
Cc: "gen-art@ietf.org" <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART Last Call review of draft-ietf-v6ops-icp-guidance-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Dec 2012 06:13:42 -0000

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A036B4Eeusaamb107ericsso_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at http://wiki.tools.ietf.org/area/gen/trac/wiki/GenA=
rtfaq  .

Please resolve these comments along with any other Last Call comments you m=
ay receive.

Document: draft-ietf-v6ops-icp-guidance-04
Reviewer: Meral Shirazipour
Review Date: 2012-12-19
IETF LC End Date: 2012-12-20
IESG Telechat date: 2013-01-10



Summary:
This draft is almost ready to be published as Informational RFC but I do ha=
ve some comments.


Nits/editorial comments:
-[Page 3], last line, "The most importance" --should be--> "The most import=
ant"
-[Page 3], line 3, "on a unplanned"--should be--> "on an unplanned"
-[Page 6], paragraph 2 starting "There is an anecdote of..."--suggestion-->=
 This anecdote could be removed as the point is clear enough from the remai=
ning text in Section 3.
-[Page 10], last sentence, "TLS" --first use--> "Transport Layer Security (=
TLS)"
-[Page 11], diagram, please add Figure number and caption.
-[Page 12], Section 8 Servers. Question: is it relevant to add some text re=
garding middleboxes and expected behavior?
-[Page 16], last paragraph, "AAAA records are provid."--typo-->"AAAA record=
s are provided."
-[Page 22], Section 18.2.  Informative References, please update draft refe=
rences to their latest version: I-D.ietf-6renum-enterprise,I-D.ietf-6renum-=
static-problem,I-D.ietf-v6ops-6204bis, and I-D.matthews-v6ops-design-guidel=
ines.



Best Regards,
Meral

---
Meral Shirazipour
Ericsson
Research
www.ericsson.com

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A036B4Eeusaamb107ericsso_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-CA" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I am the assigned Gen-ART reviewer for this draft. F=
or background on Gen-ART, please see the FAQ at
<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://=
wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a> &nbsp;.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please resolve these comments along with any other L=
ast Call comments you may receive.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Document: draft-ietf-v6ops-icp-guidance-04<o:p></o:p=
></p>
<p class=3D"MsoNormal">Reviewer: Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Review Date: 2012-12-19<o:p></o:p></p>
<p class=3D"MsoNormal">IETF LC End Date: 2012-12-20<o:p></o:p></p>
<p class=3D"MsoNormal">IESG Telechat date: 2013-01-10<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Summary:<o:p></o:p></p>
<p class=3D"MsoNormal">This draft is almost ready to be published as Inform=
ational RFC but I do have some comments.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Nits/editorial comments:<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 3], last line, &quot;The most importance&quot=
; --should be--&gt; &quot;The most important&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 3], line 3, &quot;on a unplanned&quot;--shoul=
d be--&gt; &quot;on an unplanned&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 6], paragraph 2 starting &quot;There is an an=
ecdote of...&quot;--suggestion--&gt; This anecdote could be removed as the =
point is clear enough from the remaining text in Section 3.<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 10], last sentence, &quot;TLS&quot; --first u=
se--&gt; &quot;Transport Layer Security (TLS)&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 11], diagram, please add Figure number and ca=
ption.<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 12], Section 8 Servers. Question: is it relev=
ant to add some text regarding middleboxes and expected behavior?<o:p></o:p=
></p>
<p class=3D"MsoNormal">-[Page 16], last paragraph, &quot;AAAA records are p=
rovid.&quot;--typo--&gt;&quot;AAAA records are provided.&quot;<o:p></o:p></=
p>
<p class=3D"MsoNormal">-[Page 22], Section 18.2.&nbsp; Informative Referenc=
es, please update draft references to their latest version: I-D.ietf-6renum=
-enterprise,I-D.ietf-6renum-static-problem,I-D.ietf-v6ops-6204bis, and I-D.=
matthews-v6ops-design-guidelines.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">Meral<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">---<o:p></o:p></p>
<p class=3D"MsoNormal">Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Ericsson<o:p></o:p></p>
<p class=3D"MsoNormal">Research<o:p></o:p></p>
<p class=3D"MsoNormal">www.ericsson.com<o:p></o:p></p>
</div>
</body>
</html>

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A036B4Eeusaamb107ericsso_--

From brian.e.carpenter@gmail.com  Tue Dec 18 23:59:59 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4180421F8A88 for <gen-art@ietfa.amsl.com>; Tue, 18 Dec 2012 23:59:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.601
X-Spam-Level: 
X-Spam-Status: No, score=-101.601 tagged_above=-999 required=5 tests=[AWL=0.090, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 2OVR6Yva1oGf for <gen-art@ietfa.amsl.com>; Tue, 18 Dec 2012 23:59:58 -0800 (PST)
Received: from mail-wg0-f54.google.com (mail-wg0-f54.google.com [74.125.82.54]) by ietfa.amsl.com (Postfix) with ESMTP id 3D8D421F8A53 for <gen-art@ietf.org>; Tue, 18 Dec 2012 23:59:58 -0800 (PST)
Received: by mail-wg0-f54.google.com with SMTP id fg15so748190wgb.21 for <gen-art@ietf.org>; Tue, 18 Dec 2012 23:59:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Xtp7ch77RZfeGcJGweQ972muEYIVDlbxXzAcFTGYKbg=; b=mzaic+sLNN5wnn1LLG+SGFVNRdXq1sT3zlEyT03Jp4qhQjMwh1LL7U+Q/gDs2VcLNr H8iLlDCRHfROQQ/NdHRFIz/+ZAZKzjVkNNHlf67UZWr7gcug6IOVr1nM0XTYTdgOMcFr 6ppoozhD43VvnHjnPcFqggAO9jlFK1YiL5T/1lQiVrG9sMy/2hRWySNfV+V9bS9F/M1d y/EdwH8aehWo3/NnzKqwbK8rv4wDAU7aitFU9I+itp+W/wHInekTJbZjc6cG8CD8+fy1 omsoYk4sHPnj4TNHnQ1cMclGr1Hk8XDzK/6zgvC0G7oOM+oGxSUt8B5pBHZ9FC6WhONa DYmA==
X-Received: by 10.180.107.5 with SMTP id gy5mr2245090wib.30.1355903997402; Tue, 18 Dec 2012 23:59:57 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-217-235.as13285.net. [2.102.217.235]) by mx.google.com with ESMTPS id y3sm19454922wix.6.2012.12.18.23.59.55 (version=SSLv3 cipher=OTHER); Tue, 18 Dec 2012 23:59:56 -0800 (PST)
Message-ID: <50D17402.8010803@gmail.com>
Date: Wed, 19 Dec 2012 08:00:02 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Meral Shirazipour <meral.shirazipour@ericsson.com>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A036B4E@eusaamb107.ericsson.se>
In-Reply-To: <ABCAA4EF18F17B4FB619EA93DEF7939A036B4E@eusaamb107.ericsson.se>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-v6ops-icp-guidance.all@tools.ietf.org" <draft-ietf-v6ops-icp-guidance.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-v6ops-icp-guidance-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Dec 2012 07:59:59 -0000

Thanks Meral. We will take care of these if a new version is required;
otherwise they can be handled by the RFC Editor.

Regards
   Brian


On 19/12/2012 06:13, Meral Shirazipour wrote:
> I am the assigned Gen-ART reviewer for this draft. For background on Gen-ART, please see the FAQ at http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq  .
> 
> Please resolve these comments along with any other Last Call comments you may receive.
> 
> Document: draft-ietf-v6ops-icp-guidance-04
> Reviewer: Meral Shirazipour
> Review Date: 2012-12-19
> IETF LC End Date: 2012-12-20
> IESG Telechat date: 2013-01-10
> 
> 
> 
> Summary:
> This draft is almost ready to be published as Informational RFC but I do have some comments.
> 
> 
> Nits/editorial comments:
> -[Page 3], last line, "The most importance" --should be--> "The most important"
> -[Page 3], line 3, "on a unplanned"--should be--> "on an unplanned"
> -[Page 6], paragraph 2 starting "There is an anecdote of..."--suggestion--> This anecdote could be removed as the point is clear enough from the remaining text in Section 3.
> -[Page 10], last sentence, "TLS" --first use--> "Transport Layer Security (TLS)"
> -[Page 11], diagram, please add Figure number and caption.
> -[Page 12], Section 8 Servers. Question: is it relevant to add some text regarding middleboxes and expected behavior?
> -[Page 16], last paragraph, "AAAA records are provid."--typo-->"AAAA records are provided."
> -[Page 22], Section 18.2.  Informative References, please update draft references to their latest version: I-D.ietf-6renum-enterprise,I-D.ietf-6renum-static-problem,I-D.ietf-v6ops-6204bis, and I-D.matthews-v6ops-design-guidelines.
> 
> 
> 
> Best Regards,
> Meral
> 
> ---
> Meral Shirazipour
> Ericsson
> Research
> www.ericsson.com
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art

From nick@inex.ie  Tue Dec 18 14:12:49 2012
Return-Path: <nick@inex.ie>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0187821F8602; Tue, 18 Dec 2012 14:12:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[AWL=-0.300,  BAYES_00=-2.599, J_CHICKENPOX_73=0.6, NO_RELAYS=-0.001]
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 d86HkjU-5MDq; Tue, 18 Dec 2012 14:12:48 -0800 (PST)
Received: from mail.acquirer.com (mail.netability.ie [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id A810921F84FD; Tue, 18 Dec 2012 14:12:46 -0800 (PST)
X-Envelope-To: ietf@ietf.org
Received: from cupcake.foobar.org ([IPv6:2001:4d68:2002:100:5ca5:acc:abce:62e4]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id qBIMB0jY027671 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 18 Dec 2012 22:11:05 GMT (envelope-from nick@inex.ie)
Message-ID: <50D0EA56.3050308@inex.ie>
Date: Tue, 18 Dec 2012 22:12:38 +0000
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Ben Campbell <ben@nostrum.com>
References: <AEDD0F1A-EA31-4C3A-B1BF-BD16C9196740@nostrum.com>
In-Reply-To: <AEDD0F1A-EA31-4C3A-B1BF-BD16C9196740@nostrum.com>
X-Enigmail-Version: 1.4.6
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 19 Dec 2012 00:24:32 -0800
Cc: "draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org" <draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat Review of draft-ietf-karp-routing-tcp-analysis-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Dec 2012 22:12:49 -0000

On 18/12/2012 20:14, Ben Campbell wrote:
> ** Nits/editorial comments:
>
> -- The 2119 paragraph was removed, but there's still an orphaned 2119 entry in the informational reference section.

I'm not sure that this was a good idea.  There are a lot of "has to"s in
this text, and it's not clear to me whether they are phrased like that as a
way of getting around 2119, or what's going on.  Whatever the reason, "has
to" sounds very informal and probably not suitable for a document like
this.  Could we have some clarification as to why "has to" doesn't mean
"MUST" (or even "SHOULD").

--

-   protocol stack from CPU-utilization based attacks.TCP Robustness
+   protocol stack from CPU-utilization based attacks. TCP Robustness

--

I have a general issue with the statement "TCP MD5 [RFC2385] has been
obsoleted by TCP-AO [RFC5925]."  At this time, I'm not aware of any live
TCP-AO implementations.  So while I understand that md5 is effectively
obsolete from the specification point of view, from the point of view of
operational reality it's still the only show in town (no-one uses ipsec for
this).

Secondly, as a general comment about the TCP MD5 option, no-one that I know
uses it as a serious security mechanism, but instead as a means of putting
the equivalent of a padlock on the barn door.  This does two things: 1. it
stops bgp sessions from being accidentally re-used (e.g. at IXPs or on
commercial providers who are re-using access ports), and 2. it simply
raises the bar in terms of difficulty.  If your barnyard door has a
padlock, and the one beside doesn't, the average lazy human being will
attempt to poke at the one which doesn't.

>From an operational view, i would generally see the difference between
tcp/md5 and tcp/sha1 (via tcp-ao) as being similar to the difference
between a 5 pin and a 7 pin barrel lock.  Both look like a lock on the
outside, and the thief is probably going to smash a window to get in
anyway, or look for the key which the owners left under the mat.

--

There is a second operational issue which may merit mention here, namely
the issue of ensuring that whatever session layer authentication is
implemented on an actual network device, that it doesn't create more
problems than it solves.  Specifically, if session layer authentication is
pushed too far down the protocol stack, cryptographic authentication can
occur before other basic checks which might be a whole pile less CPU
intensive.  There was a scare about this several years ago when it turned
out that a well-known vendor had implemented tcp md5 checksumming before
more basic tcp session checks (e.g. seq numbers, ttl, etc).  In the event,
this turned out to be a red herring because md5 is sufficiently gentle on
the CPU that it didn't make much difference in reality.

However, there is cryptographic value in using more computationally
intensive hashing algorithms, and if routers (which often have relatively
slow general CPUs or route-processor CPUs) were to get trashed with a large
flood of packets which were signed with a cpu-intensive hashing algorithm,
and if the checksum were to be implemented in the wrong place in the TCP
stack, then this could become an actual problem.

I don't know whether these things should be noted in the draft.

--

It may be useful to consider whether to acknowledge the existence of rfc
6192 in the context of providing a link to what other steps might be useful
to secure routers.

--

>    pairs of routers when using TCP MD5.  It is well known that the
>    longer the same key is used, the greater the chance that it can be
>    guessed or exposed

I'm split between {{cn}} and [[Wikipedia:OBVIOUS]].  Hmmm, life's little
decisions.

--

>    Routers lack comprehensive key management and keys derived from it
>    that they can use to authenticate data.

clumsy wording (and grammatically incorrect).

--

>    Authentication, tamper protection, and encryption all require the use

should that second comma be dropped?  Not sure what the ietf style dictates.

--

>    Authentication, tamper protection, and encryption all require the use
>    of keys by sender and receiver.  An automated KMP therefore has to
>    include a way to distribute MKT between two end points with little or
>    no administration overhead.  It has to cover automatic key rollover.

"has to" has to become "MUST", shouldn't it?

Also, the third sentence is a semantic repeat of the second - and much
easier to understand, too.

--

-    that, where PCEs are discovered and not configured, the PCC cannot
+    that where PCEs are discovered and not configured, the PCC cannot

--

-   [draft-zheng-mpls-ldp-hello-crypto-auth-04] suggest a new
+   [draft-zheng-mpls-ldp-hello-crypto-auth-04] suggests a new

--

>             An LSR can reduce the threat of spoofed Extended Hellos by
>    filtering them and accepting Hellos from sources permitted by an
>    access lists.

"permitted by an access list".

--

>  However, performing the filtering using access lists
>    requires LSR resource, and the LSR is still vulnerable to the IP
>    source address spoofing.

This is a little clumsy.  Maybe rephrase as: "However, filtering with
access lists requires LSR resources, and the LSR may still be vulnerable to
IP source address spoofing."

"may" rather than is.  This will depend on the iACL policy of the network.

--

> Spoofed Hello messages are observed and reported as real
>    problem in production networks.

s/problem/problems/

{{cn}}

--

>    The Message Authentication Codes (MACs) used by TCP MD5 option, is
>    considered too weak

oops, grammar.

--

> Cryptographic research suggests that both these
>    MAC algorithms defined are fairly secure.

Today's "fairly secure" algorithms are tomorrow's swiss cheese:

> http://www.eetimes.com/electronics-news/4051745/Chinese-researchers-compromise-SHA-1-hashing-algorithm

I would explicitly avoid the use of ".* secure", and if the authors feel
the need to make any statement about them, that it should be prefixed by
woolly, hand-wavey, get-out-of-jail-free phrases, e.g. "at the time of
authorship, there are no publicly known attacks on this algorithm which
reduce the strength to complexity of less than 1 in X", or however
crypto-heads like to phrase that sort of thing.  Right now, that phrase is
headed towards algorithmic oblivion.

--

> LDP [RFC5036] does not provide any security
>    mechanisms for use with Hello messages except for some configuration
>    which may help protect against bogus discovery events.  These
>    configurations include directly connected links and interfaces.

suggest rewording:

LDP [RFC5036] does not provide any security mechanisms for use with Hello
messages, although operational workarounds may be implemented such as
using directly interfaces.

--

There are possibly more nits in there - I haven't exhaustively gone through
all the text, but it needs a good shake-down by a style editor.

Otherwise I like this draft and think it has merit as a general
informational overview.

Nick


From elwynd@dial.pipex.com  Wed Dec 19 12:18:32 2012
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 962D221F84C2 for <gen-art@ietfa.amsl.com>; Wed, 19 Dec 2012 12:18:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 Kzi1Kp00bqrT for <gen-art@ietfa.amsl.com>; Wed, 19 Dec 2012 12:18:31 -0800 (PST)
Received: from auth.a.painless.aa.net.uk (a.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e33]) by ietfa.amsl.com (Postfix) with ESMTP id 941C521F857A for <gen-art@ietf.org>; Wed, 19 Dec 2012 12:18:31 -0800 (PST)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by a.painless.aa.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <elwynd@dial.pipex.com>) id 1TlQ5x-00083d-F6; Wed, 19 Dec 2012 20:18:27 +0000
From: Elwyn Davies <elwynd@dial.pipex.com>
To: General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain
Date: Wed, 19 Dec 2012 20:17:54 +0000
Message-Id: <1355948274.11916.15331.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
X-Spam-Score-a.painless.aa.net.uk: -4.0
Cc: draft-ietf-sidr-usecases.all@tools.ietf.org
Subject: [Gen-art] Gen-art LC/Telechat review of draft-ietf-sidr-usecases-05.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Dec 2012 20:18:32 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-sidr-usecases-05.txt
Reviewer: Elwyn Davies
Review Date: 19 December 2012
IETF LC End Date: 20 December 2012
IESG Telechat date: (if known) 20 December 2012

Summary:
This doucment is almost ready for publication.  There are a couple of
very minor issues (glorified nits really) and a number of real nits. 

Major issues:

Minor issues:
s1.4: The document doesn't appear to use any RFC 2119 upper-cased words.
If this is correct (and it probably is as the document isn't specifying
requirements) then this para and the RFC2119 ref SHOULd be removed.

s2.1, para 1: 
>    assumed to be intended (i.e., considered
>    unsuspicious) unless proven otherwise by the existence of a valid
>    RPKI object.
It is possible that I don't understand the problem, but this appears to
be trying to prove a negative by the existence of something.  What RPKI
object would have to exist to make the route suspicious?

s6.2: Can the make-before-break principle be applied to the resource
certificate for Org B?  Presumably this would mean overlapping existence
of resource certs for Org A and Org B so that the ROA add can occur
before the revoke.  Is this a problem?

Nits/editorial comments:

Abstract/a1:  The opening sentence is a bit obscure:

> This document provides use cases, directions, and interpretations for
>    organizations and relying parties when creating or encountering RPKI
>    object scenarios in the public RPKI.  All of the above are discussed
>    here in relation to the Internet routing system.
> 
Maybe better:
   This document describes a number of use cases together with directions and 
   interpretations for
   organizations and relying parties when creating or encountering RPKI
   object scenarios in the public RPKI.  All of the above are discussed
   here in relation to the Internet routing system.

Abstract/s1 et seq: Need to expand RPKI

ss1.1/1.3:  Although ROA is expanded in s1.1 as part of a document
title, it would be helpful to include a definition in s1.3 as it is used
a great deal in the other definitions.

s1.3, para 1: Technically, I don't think you need the author's
permission as it is an IETF draft, but it is polite.

s1.3, several places: s/in consideration/under consideration/

s1.3, last para: Possibly need to clarify *what* is originated?  s/that
is originated/for which a route is advertised/

s2.1, para 1: s/stance/operational policy/?

s3.3: the two ASNs used in the example are visually easily confused.
Might be better to use a more obviously different second ASN.

s3.5: Might be useful to refer to the currently in progress
draft-ietf-idr-as0 regarding AS0.

s4: The wording of the first sentence will have to be changed (or just
removed) for the published RFC.

s5.2 and s5.3, first table, fourth line of body: s/YES/Yes/

s6.x: Given the 'make-before-break' principle, would it be sensible to
describe the add before the revoke in each case?

s7.1: Could the terms Valid, Invalid and Not Found be usefully included
in the definitions section?

s7.1.6: see comment re s3.5 and RFC 6483.

s7.1.7, 'comment' para: s/exit/exist/ 






From ben@nostrum.com  Wed Dec 19 13:15:01 2012
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C04C21F85EE; Wed, 19 Dec 2012 13:15:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.543
X-Spam-Level: 
X-Spam-Status: No, score=-102.543 tagged_above=-999 required=5 tests=[AWL=0.057, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
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 cvP2--umsxYW; Wed, 19 Dec 2012 13:15:00 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 4885021F8578; Wed, 19 Dec 2012 13:15:00 -0800 (PST)
Received: from [172.20.10.2] (mobile-166-137-149-039.mycingular.net [166.137.149.39]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qBJLEwQO002499 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 19 Dec 2012 15:14:59 -0600 (CST) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Wed, 19 Dec 2012 15:14:58 -0600
Message-Id: <BE996F07-CFB7-47F5-8B17-FA651C294FA3@nostrum.com>
To: draft-ietf-dhc-relay-id-suboption.all@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
Received-SPF: pass (nostrum.com: 166.137.149.39 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
Subject: [Gen-art] Gen-ART LC Review of draft-ietf-dhc-relay-id-suboption-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Dec 2012 21:15:01 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-dhc-relay-id-suboption-11
Reviewer: Ben Campbell
Review Date: 2012-12-19
IETF LC End Date: 2013-01-07

Summary: This draft is basically ready for publication as a proposed =
standard. However, there is one comment from a prior review that I am =
not sure whether is resolved.

Major issues:

None

Minor issues:

-- In Sean Turner's 2009 review of version 07 of the document [ =
http://www.ietf.org/mail-archive/web/gen-art/current/msg04614.html ], he =
made the following comment:

> In the security considerations it says look to RFC 3046 and
> RFC 4030 for security considerations and then says SHOULD use the =
relay
> agent authentication option from RFC 4030.  RFC 3046 is targeted at
> network infrastructures that are "trusted and secure" and RFC 4030
> allows the relay agent to be part of this trusted and secure network.
> If an implementation doesn't use the relay agent authentication =
option,
> then the relay agent can't be part of the "trusted and secure" =
network.
>  This makes me think that the relay agent authentication option from
> RFC 4030 ought to be a MUST not a SHOULD?

I can't tell from the resulting conversation if that comment is =
addressed in the current text. Additional text has been added, but the =
SHOULD remains. I'm willing to accept it has been addressed if the =
author's say so--I only mention it to make sure it didn't fall through a =
crack.

Nits/editorial comments:

-- section 5, last paragraph:

I suggest removing the scare quotes around "stability". If there are =
concerns about whether such stability is real, it would be better to say =
that directly.

-- informative references:

draft-ietf-dhc-dhcpv4-bulk-leasequery-06 is now 07





From nick@inex.ie  Wed Dec 19 14:26:35 2012
Return-Path: <nick@inex.ie>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A09D21F8584; Wed, 19 Dec 2012 14:26:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.5
X-Spam-Level: 
X-Spam-Status: No, score=-2.5 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, NO_RELAYS=-0.001]
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 p3JeKCYuiK1A; Wed, 19 Dec 2012 14:26:34 -0800 (PST)
Received: from mail.acquirer.com (mail.netability.ie [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id 46BE521F8530; Wed, 19 Dec 2012 14:26:33 -0800 (PST)
X-Envelope-To: ietf@ietf.org
Received: from cupcake.foobar.org ([IPv6:2001:4d68:2002:100:41e8:aae1:8461:f339]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id qBJMOk7s039936 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 19 Dec 2012 22:24:51 GMT (envelope-from nick@inex.ie)
Message-ID: <50D23F11.8060901@inex.ie>
Date: Wed, 19 Dec 2012 22:26:25 +0000
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Ben Campbell <ben@nostrum.com>
References: <AEDD0F1A-EA31-4C3A-B1BF-BD16C9196740@nostrum.com> <50D0EA56.3050308@inex.ie> <566F175C-1DD4-414A-AB7D-27BF33156694@nostrum.com>
In-Reply-To: <566F175C-1DD4-414A-AB7D-27BF33156694@nostrum.com>
X-Enigmail-Version: 1.4.6
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org" <draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat Review of draft-ietf-karp-routing-tcp-analysis-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Dec 2012 22:26:35 -0000

On 18/12/2012 22:50, Ben Campbell wrote:
> I think Nick's email was a review of the document in general, 

yes, sorry, it was.  I hit reply when I saw the subject line.

> I don't think so. This draft does not establish a standard, or define a
> protocol. While I don't speak for the authors, I don't think it's
> intended to make normative statements about anything. The language is
> descriptive, not prescriptive.

ok, noted.

> (I agree "has to" is an awkward substitute for the non-normative "must".
> I agree that "must" should generally be avoided when there can be
> confusion about the normativeness of a statement. I'm not sure that's
> the case here, since the whole doc is non-normative. And I think we
> could find better language even when the confusion is possible.)

"needs to"?  "ought to"?  It's all massively context dependent though.
What's needed are some words / phrases which are defined to have local
imperative scope only or else nonlocal informative "must" - but yeah it's
messy and generally will involve nontrivial wordsmithing to work around
what is meant.

Nick


From terry.manderson@icann.org  Wed Dec 19 16:54:05 2012
Return-Path: <terry.manderson@icann.org>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69EFD21F84D0 for <gen-art@ietfa.amsl.com>; Wed, 19 Dec 2012 16:54:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.989
X-Spam-Level: 
X-Spam-Status: No, score=-105.989 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599, J_CHICKENPOX_43=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 NZQ7wfO1vuUo for <gen-art@ietfa.amsl.com>; Wed, 19 Dec 2012 16:54:02 -0800 (PST)
Received: from EXPFE100-1.exc.icann.org (expfe100-1.exc.icann.org [64.78.22.236]) by ietfa.amsl.com (Postfix) with ESMTP id E29F821F88A2 for <gen-art@ietf.org>; Wed, 19 Dec 2012 16:54:00 -0800 (PST)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-1.exc.icann.org ([64.78.22.236]) with mapi; Wed, 19 Dec 2012 16:53:57 -0800
From: Terry Manderson <terry.manderson@icann.org>
To: Elwyn Davies <elwynd@dial.pipex.com>, General Area Review Team <gen-art@ietf.org>
Date: Wed, 19 Dec 2012 16:53:54 -0800
Thread-Topic: Gen-art LC/Telechat review of  draft-ietf-sidr-usecases-05.txt
Thread-Index: Ac3eJibc675DLCCiTPq5UISdBO2JhwAJlT56
Message-ID: <CCF89EC2.2E370%terry.manderson@icann.org>
In-Reply-To: <1355948274.11916.15331.camel@mightyatom>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3438845634_5168437"
MIME-Version: 1.0
Cc: "draft-ietf-sidr-usecases.all@tools.ietf.org" <draft-ietf-sidr-usecases.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-art LC/Telechat review of draft-ietf-sidr-usecases-05.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Dec 2012 00:54:06 -0000

--B_3438845634_5168437
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

Hi Elwyn,

Thanks for your review. While Sriram holds the pen at this stage, I will
reply here.


On 20/12/12 6:17 AM, "Elwyn Davies" <elwynd@dial.pipex.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> 
> 
> Summary:
> This doucment is almost ready for publication.  There are a couple of
> very minor issues (glorified nits really) and a number of real nits.
> 
> Major issues:
> 
> Minor issues:
> s1.4: The document doesn't appear to use any RFC 2119 upper-cased words.
> If this is correct (and it probably is as the document isn't specifying
> requirements) then this para and the RFC2119 ref SHOULd be removed.

Great observation, yes RFC2119 can be removed.

> 
> s2.1, para 1:
>>    assumed to be intended (i.e., considered
>>    unsuspicious) unless proven otherwise by the existence of a valid
>>    RPKI object.
> It is possible that I don't understand the problem, but this appears to
> be trying to prove a negative by the existence of something.  What RPKI
> object would have to exist to make the route suspicious?

Essentially a valid RPKI ROA object would need to exist that proves a route
is suspicious. Because the RPKI+ROA is a "bolt on after the fact" security
effort, you can do no more. Simply routing exists now, the RPKI would be
deployed in the future. So any route that is seen must be considered
intended unless proven otherwise.

> 
> s6.2: Can the make-before-break principle be applied to the resource
> certificate for Org B?  Presumably this would mean overlapping existence
> of resource certs for Org A and Org B so that the ROA add can occur
> before the revoke.  Is this a problem?
> 

The preference, I believe (and my co-authors can correct me) is that two
different resource certificates (unless one in subordinate to the other)
should never exist.

This problem is an open issue in SIDR related to the grandfathering topic.
So for now the usecase should be that overlap cannot occur.

> Nits/editorial comments:
> 
> Abstract/a1:  The opening sentence is a bit obscure:
> 
>> This document provides use cases, directions, and interpretations for
>>    organizations and relying parties when creating or encountering RPKI
>>    object scenarios in the public RPKI.  All of the above are discussed
>>    here in relation to the Internet routing system.
>> 
> Maybe better:
>    This document describes a number of use cases together with directions and
>    interpretations for
>    organizations and relying parties when creating or encountering RPKI
>    object scenarios in the public RPKI.  All of the above are discussed
>    here in relation to the Internet routing system.

Nicer, Thanks.

> 
> Abstract/s1 et seq: Need to expand RPKI

Ack.

> 
> ss1.1/1.3:  Although ROA is expanded in s1.1 as part of a document
> title, it would be helpful to include a definition in s1.3 as it is used
> a great deal in the other definitions.

Ack.

> 
> s1.3, para 1: Technically, I don't think you need the author's
> permission as it is an IETF draft, but it is polite.
> 

I'd like to err on the side of politeness :)

> s1.3, several places: s/in consideration/under consideration/

Ack

> 
> s1.3, last para: Possibly need to clarify *what* is originated?  s/that
> is originated/for which a route is advertised/

Does

Multi-homed prefix or subnet: A prefix (i.e., subnet) for which a route is
   originated to two or more Autonomous Systems.

work for you?

> 
> s2.1, para 1: s/stance/operational policy/?


nice :-)

> 
> s3.3: the two ASNs used in the example are visually easily confused.
> Might be better to use a more obviously different second ASN.

Sriram, are you able to change the text and the table to have one of the
ASNs be AS64511 for both sec 3.2 and 3.3?


> 
> s3.5: Might be useful to refer to the currently in progress
> draft-ietf-idr-as0 regarding AS0.

I'm easy. Sriram, Russ?

> 
> s4: The wording of the first sentence will have to be changed (or just
> removed) for the published RFC.

Ack

> 
> s5.2 and s5.3, first table, fourth line of body: s/YES/Yes/

Ack.

> 
> s6.x: Given the 'make-before-break' principle, would it be sensible to
> describe the add before the revoke in each case?

ahh.. I think we have a disconnect. make before break is considered in the
routing sense that a route is considered o.k. (UNKNOWN) unless proven
otherwise, this means you can remove ALL RPKI object for a route, and it
will still exist happily until a new and conflicting RPKI ROA is created..
And we are working to that. Not necessarily making a new valid object before
breaking the old valid object. That would then imply ownership of a prefix
can then be in two places at the same time. And like the transfer of title
for a house, overlap tends to be considered a bad thing. (co-authors, chime
in here!)

> 
> s7.1: Could the terms Valid, Invalid and Not Found be usefully included
> in the definitions section?

Yes.

> 
> s7.1.6: see comment re s3.5 and RFC 6483.

Ack.

> 
> s7.1.7, 'comment' para: s/exit/exist/
> 

Ack.

Sriram, can you make the required changes as necessary to the holding
pattern copy assuming we all agree?

Cheers
Terry

--B_3438845634_5168437
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIIQAQYJKoZIhvcNAQcCoIIP8jCCD+4CAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
Dc0wggcDMIIF66ADAgECAhAPz2lJUZsAlD35l4oJxf0FMA0GCSqGSIb3DQEBBQUAMGIxCzAJ
BgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNVBAsTEHd3dy5kaWdpY2Vy
dC5jb20xITAfBgNVBAMTGERpZ2lDZXJ0IEFzc3VyZWQgSUQgQ0EtMTAeFw0xMjAzMjcwMDAw
MDBaFw0xNTAzMjcxMjAwMDBaMIGsMQswCQYDVQQGEwJVUzETMBEGA1UECBMKQ2FsaWZvcm5p
YTEXMBUGA1UEBxMOTWFyaW5hIGRlbCBSZXkxPDA6BgNVBAoTM0ludGVybmV0IENvcnBvcmF0
aW9uIGZvciBBc3NpZ25lZCBOYW1lcyBhbmQgTnVtYmVyczEXMBUGA1UECxMORE5TIE9wZXJh
dGlvbnMxGDAWBgNVBAMTD1RlcnJ5IE1hbmRlcnNvbjCCASIwDQYJKoZIhvcNAQEBBQADggEP
ADCCAQoCggEBAKRhZ4W3U6MnfS2woYEFCIyN+g1MNILokbUKk+PTl5mmK3QtWQxTSOu2sdzN
xHMy6p2RoT9BMGOamttFq2WswSru6/7JT1TflytGaPHfK5kMP/pI47hmcwUEm9Z169I5ar7z
BTiEAQA06cGKtgJ8XiiLFUIHLVuRq3WGxjnFTHlAHXY6mdgDT/ntAnoEvvPVm4XqUnjJiZTS
ojzyr1q2RqFvyXs2blOARumDqvLI33yLGcUuaEL+A+hgodzM/fL4kdoy964mXvmEerpm4d4f
Y/JfbRUWxc0Eomu9nwGFNk6ijO41qk+OIboct2qeA+5PPclXJNNHYVfzT2dyWfGgxaMCAwEA
AaOCA2gwggNkMB8GA1UdIwQYMBaAFBUAEisTmLKZB+0e36K+Vw0rZwLNMB0GA1UdDgQWBBSz
wvR2YXpP9XjS9cknMX5g3LM2jTAkBgNVHREEHTAbgRl0ZXJyeS5tYW5kZXJzb25AaWNhbm4u
b3JnMA4GA1UdDwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwfQYD
VR0fBHYwdDA4oDagNIYyaHR0cDovL2NybDMuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0QXNzdXJl
ZElEQ0EtMS5jcmwwOKA2oDSGMmh0dHA6Ly9jcmw0LmRpZ2ljZXJ0LmNvbS9EaWdpQ2VydEFz
c3VyZWRJRENBLTEuY3JsMIIBxQYDVR0gBIIBvDCCAbgwggG0BgpghkgBhv1sBAECMIIBpDA6
BggrBgEFBQcCARYuaHR0cDovL3d3dy5kaWdpY2VydC5jb20vc3NsLWNwcy1yZXBvc2l0b3J5
Lmh0bTCCAWQGCCsGAQUFBwICMIIBVh6CAVIAQQBuAHkAIAB1AHMAZQAgAG8AZgAgAHQAaABp
AHMAIABDAGUAcgB0AGkAZgBpAGMAYQB0AGUAIABjAG8AbgBzAHQAaQB0AHUAdABlAHMAIABh
AGMAYwBlAHAAdABhAG4AYwBlACAAbwBmACAAdABoAGUAIABEAGkAZwBpAEMAZQByAHQAIABD
AFAALwBDAFAAUwAgAGEAbgBkACAAdABoAGUAIABSAGUAbAB5AGkAbgBnACAAUABhAHIAdAB5
ACAAQQBnAHIAZQBlAG0AZQBuAHQAIAB3AGgAaQBjAGgAIABsAGkAbQBpAHQAIABsAGkAYQBi
AGkAbABpAHQAeQAgAGEAbgBkACAAYQByAGUAIABpAG4AYwBvAHIAcABvAHIAYQB0AGUAZAAg
AGgAZQByAGUAaQBuACAAYgB5ACAAcgBlAGYAZQByAGUAbgBjAGUALjB3BggrBgEFBQcBAQRr
MGkwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLmRpZ2ljZXJ0LmNvbTBBBggrBgEFBQcwAoY1
aHR0cDovL2NhY2VydHMuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0QXNzdXJlZElEQ0EtMS5jcnQw
DAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOCAQEAYpwxK/KvdhbyQqrKp2ylMQpNzqVH
ofo4hPILTnp/o+UyYVn6daWSilaV+XNBzE5Rm/f7ms2iA1zBzOvGv55pLH0n6lgIRTeuAGzf
KIsPCwPvYQkkMAPXHzh9A44m19hvigTgOPNyjzcOTiHqwwCJSDTEZx17CEkrzQPq1vfG1Lvk
+AWjEtxCsGmsuCHHaZjwQ8SsGI7W5cA1Y4RTcQf6S9eIpSsOwXIYdDgWq9Uhi/amW7ryW06Y
GH7BHaitqgmm32MZuid3UzJUU6+Ljx7uGA9Fe6k1uPEHhaXTAoobPSpPdOgGmnxUCRQu2OI7
+I8vHiSe7DC/LmxEDC5kB+lUTjCCBsIwggWqoAMCAQICEAoE3yF0XU0rjOozcgUAUOkwDQYJ
KoZIhvcNAQEFBQAwZTELMAkGA1UEBhMCVVMxFTATBgNVBAoTDERpZ2lDZXJ0IEluYzEZMBcG
A1UECxMQd3d3LmRpZ2ljZXJ0LmNvbTEkMCIGA1UEAxMbRGlnaUNlcnQgQXNzdXJlZCBJRCBS
b290IENBMB4XDTA2MTExMDAwMDAwMFoXDTIxMTExMDAwMDAwMFowYjELMAkGA1UEBhMCVVMx
FTATBgNVBAoTDERpZ2lDZXJ0IEluYzEZMBcGA1UECxMQd3d3LmRpZ2ljZXJ0LmNvbTEhMB8G
A1UEAxMYRGlnaUNlcnQgQXNzdXJlZCBJRCBDQS0xMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A
MIIBCgKCAQEA6IItmfnKwkKVpYBzQHDSnlZUXKnE0kEGj8kz/E1FkVyBn+0snPgWWd+etSQV
wpi5tHdJ3InECtqvy15r7a2wcTHrzzpADEZNk+yLejYIA6sMNP4YSYL+x8cxSIB8HqIPkg5Q
ycaH6zY/2DDD/6b3+6LNb3Mj/qxWBZDwMiEWicZwiPkFl32jx0PdAug7Pe2xQaPtP77blUjE
7h6z8rwMK5nQxl0SQoHhg26Ccz8mSxSQrllmCsSNvtLOBq6thG9IhJtPQLnxTPKvmPv2zkBd
XPao8S+v7Iki8msYZbHBc63X8djPHgp0XEK4aH631XcKJ1Z8D2KkPzIUYJX9BwSiCQIDAQAB
o4IDbzCCA2swDgYDVR0PAQH/BAQDAgGGMDsGA1UdJQQ0MDIGCCsGAQUFBwMBBggrBgEFBQcD
AgYIKwYBBQUHAwMGCCsGAQUFBwMEBggrBgEFBQcDCDCCAcYGA1UdIASCAb0wggG5MIIBtQYL
YIZIAYb9bAEDAAQwggGkMDoGCCsGAQUFBwIBFi5odHRwOi8vd3d3LmRpZ2ljZXJ0LmNvbS9z
c2wtY3BzLXJlcG9zaXRvcnkuaHRtMIIBZAYIKwYBBQUHAgIwggFWHoIBUgBBAG4AeQAgAHUA
cwBlACAAbwBmACAAdABoAGkAcwAgAEMAZQByAHQAaQBmAGkAYwBhAHQAZQAgAGMAbwBuAHMA
dABpAHQAdQB0AGUAcwAgAGEAYwBjAGUAcAB0AGEAbgBjAGUAIABvAGYAIAB0AGgAZQAgAEQA
aQBnAGkAQwBlAHIAdAAgAEMAUAAvAEMAUABTACAAYQBuAGQAIAB0AGgAZQAgAFIAZQBsAHkA
aQBuAGcAIABQAGEAcgB0AHkAIABBAGcAcgBlAGUAbQBlAG4AdAAgAHcAaABpAGMAaAAgAGwA
aQBtAGkAdAAgAGwAaQBhAGIAaQBsAGkAdAB5ACAAYQBuAGQAIABhAHIAZQAgAGkAbgBjAG8A
cgBwAG8AcgBhAHQAZQBkACAAaABlAHIAZQBpAG4AIABiAHkAIAByAGUAZgBlAHIAZQBuAGMA
ZQAuMA8GA1UdEwEB/wQFMAMBAf8wfQYIKwYBBQUHAQEEcTBvMCQGCCsGAQUFBzABhhhodHRw
Oi8vb2NzcC5kaWdpY2VydC5jb20wRwYIKwYBBQUHMAKGO2h0dHA6Ly93d3cuZGlnaWNlcnQu
Y29tL0NBQ2VydHMvRGlnaUNlcnRBc3N1cmVkSURSb290Q0EuY3J0MIGBBgNVHR8EejB4MDqg
OKA2hjRodHRwOi8vY3JsMy5kaWdpY2VydC5jb20vRGlnaUNlcnRBc3N1cmVkSURSb290Q0Eu
Y3JsMDqgOKA2hjRodHRwOi8vY3JsNC5kaWdpY2VydC5jb20vRGlnaUNlcnRBc3N1cmVkSURS
b290Q0EuY3JsMB0GA1UdDgQWBBQVABIrE5iymQftHt+ivlcNK2cCzTAfBgNVHSMEGDAWgBRF
66Kv9JLLgjEtUYunpyGd823IDzANBgkqhkiG9w0BAQUFAAOCAQEAhGFOQR64dgQqtbbvj/JV
hbldVv4KmObkvWWKfUAp0/yxXUX9OrgqWzNLJFzNubTkc61hXXatdDOKZtUjr0wfcm5F2XVA
u6I7z41JL8BBsOIpo1E4Q1CZFKwzBjViiX13qVIH5WwgV7aBum+8s8KU7XYCgNl8zoWoHOzH
Q0pLsVfPcs7f9SU8yyJP/Z9S0TfLCLs4PuDVPm95Ca1bfDGzdzXD5GP5aAqYB+dGOHeE0j6X
vAqgqKwlT0RukeHSWq9r7zAcjaNEQrMQiyP61+Y1dDesz+urWB/JiCP/NtQH6jRqR+qdlWye
KU9T7eMrlSBOKs+WYHr4LIDwlVLOKZaBYjGCAfwwggH4AgEBMHYwYjELMAkGA1UEBhMCVVMx
FTATBgNVBAoTDERpZ2lDZXJ0IEluYzEZMBcGA1UECxMQd3d3LmRpZ2ljZXJ0LmNvbTEhMB8G
A1UEAxMYRGlnaUNlcnQgQXNzdXJlZCBJRCBDQS0xAhAPz2lJUZsAlD35l4oJxf0FMAkGBSsO
AwIaBQCgXTAjBgkqhkiG9w0BCQQxFgQUBTrSN6MXL2CBVRN5iK9Q1rdpzt8wGAYJKoZIhvcN
AQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTIxMjIwMDA1MzU0WjANBgkqhkiG
9w0BAQEFAASCAQBczFeHqKeb7fMKjOBSv0Nw3DvBe5AxxAPn3Lpap8JY2Vw6uHNMF6jm1Ysp
+d5fR4cwPRfOUG+9aSswG+VjTrizAzeXZHmnuBRw4XqIiqHbKSZeM+ksGDlsI2fgeGHsXVOg
DFehBznDSM6EZ5cvtLIYMGBkJrxVGidScJm+/YS0A5vqh+yr261fuGR8SEQEg57eavU2Mox5
dd4Dz41VeHWODk/aRnzs6rHDyPWkzGZL34RNNsMsVsY8dJFs6Ty/zzEaolpH1xJGoMkynIMP
CgveiFgTA5gh5QIuHb30XdUUm18r16W4w6EA23MNjXJNibHuu6V7ILMw2UeW1Q1q9pCn

--B_3438845634_5168437--

From elwynd@dial.pipex.com  Wed Dec 19 17:23:40 2012
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 678EF21F87DE for <gen-art@ietfa.amsl.com>; Wed, 19 Dec 2012 17:23:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_43=0.6, USER_IN_WHITELIST=-100]
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 3k581K3io5uH for <gen-art@ietfa.amsl.com>; Wed, 19 Dec 2012 17:23:39 -0800 (PST)
Received: from auth.a.painless.aa.net.uk (a.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e33]) by ietfa.amsl.com (Postfix) with ESMTP id 763C421F843A for <gen-art@ietf.org>; Wed, 19 Dec 2012 17:23:39 -0800 (PST)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by a.painless.aa.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <elwynd@dial.pipex.com>) id 1TlUrF-00007K-UI; Thu, 20 Dec 2012 01:23:36 +0000
From: Elwyn Davies <elwynd@dial.pipex.com>
To: Terry Manderson <terry.manderson@icann.org>
In-Reply-To: <CCF89EC2.2E370%terry.manderson@icann.org>
References: <CCF89EC2.2E370%terry.manderson@icann.org>
Content-Type: text/plain
Date: Thu, 20 Dec 2012 01:23:04 +0000
Message-Id: <1355966584.11916.15363.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
X-Spam-Score-a.painless.aa.net.uk: -4.0
Cc: "draft-ietf-sidr-usecases.all@tools.ietf.org" <draft-ietf-sidr-usecases.all@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-art LC/Telechat review of draft-ietf-sidr-usecases-05.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Dec 2012 01:23:40 -0000

Hi, Terry.

Thanks for the swift reply.

Looks like all is well with most of he comments.

I guess the main consclusion would be that you maybe need to put in a
bit more explanation of the context to which make-before-break applies
as per your explanation to me below.

Excised the various 'acked' bits.. couple more comments in line.

Regards,
Elwyn

On Wed, 2012-12-19 at 16:53 -0800, Terry Manderson wrote:
> Hi Elwyn,
> 
> Thanks for your review. While Sriram holds the pen at this stage, I will
> reply here.
> 
> 
> On 20/12/12 6:17 AM, "Elwyn Davies" <elwynd@dial.pipex.com> wrote:
> 
> > I am the assigned Gen-ART reviewer for this draft. For background on
> > Gen-ART, please see the FAQ at
> > 
> > 
> > Summary:
> > This doucment is almost ready for publication.  There are a couple of
> > very minor issues (glorified nits really) and a number of real nits.
> > 
> > Major issues:
> > 
> > Minor issues:
> > 
> > s2.1, para 1:
> >>    assumed to be intended (i.e., considered
> >>    unsuspicious) unless proven otherwise by the existence of a valid
> >>    RPKI object.
> > It is possible that I don't understand the problem, but this appears to
> > be trying to prove a negative by the existence of something.  What RPKI
> > object would have to exist to make the route suspicious?
> 
> Essentially a valid RPKI ROA object would need to exist that proves a route
> is suspicious. Because the RPKI+ROA is a "bolt on after the fact" security
> effort, you can do no more. Simply routing exists now, the RPKI would be
> deployed in the future. So any route that is seen must be considered
> intended unless proven otherwise.
I see now.. perhaps you could add something like:
... valid RPKI object that explicitly invalidates the route (see Section
7 for examples).
> 
> > 
> > s6.2: Can the make-before-break principle be applied to the resource
> > certificate for Org B?  Presumably this would mean overlapping existence
> > of resource certs for Org A and Org B so that the ROA add can occur
> > before the revoke.  Is this a problem?
> > 
> 
> The preference, I believe (and my co-authors can correct me) is that two
> different resource certificates (unless one in subordinate to the other)
> should never exist.
> 
> This problem is an open issue in SIDR related to the grandfathering topic.
> So for now the usecase should be that overlap cannot occur.
Do you think this needs explicit  mention?
> 
> > Nits/editorial comments:
> > 
> > Abstract/a1:  The opening sentence is a bit obscure:
> > 
> >> This document provides use cases, directions, and interpretations for
> >>    organizations and relying parties when creating or encountering RPKI
> >>    object scenarios in the public RPKI.  All of the above are discussed
> >>    here in relation to the Internet routing system.
> >> 
> > Maybe better:
> >    This document describes a number of use cases together with directions and
> >    interpretations for
> >    organizations and relying parties when creating or encountering RPKI
> >    object scenarios in the public RPKI.  All of the above are discussed
> >    here in relation to the Internet routing system.
> 
> Nicer, Thanks.
:-)

> > 
> > s1.3, last para: Possibly need to clarify *what* is originated?  s/that
> > is originated/for which a route is advertised/
> 
> Does
> 
> Multi-homed prefix or subnet: A prefix (i.e., subnet) for which a route is
>    originated to two or more Autonomous Systems.
> 
> work for you?

Maybe 'through two or more' but basically 'yes, thanks'.
> 
> > 
> > s2.1, para 1: s/stance/operational policy/?
> 
> 
> nice

:-)


> > 
> > s3.5: Might be useful to refer to the currently in progress
> > draft-ietf-idr-as0 regarding AS0.
> 
> I'm easy. Sriram, Russ?
> 

> > 
> > s6.x: Given the 'make-before-break' principle, would it be sensible to
> > describe the add before the revoke in each case?
> 
> ahh.. I think we have a disconnect. make before break is considered in the
> routing sense that a route is considered o.k. (UNKNOWN) unless proven
> otherwise, this means you can remove ALL RPKI object for a route, and it
> will still exist happily until a new and conflicting RPKI ROA is created..
> And we are working to that. Not necessarily making a new valid object before
> breaking the old valid object. That would then imply ownership of a prefix
> can then be in two places at the same time. And like the transfer of title
> for a house, overlap tends to be considered a bad thing. (co-authors, chime
> in here!)
> 
See initial comment.. this is a useful explanation and some words to
this effect would avoid others with equally bad understanding of the
RPKI scenario making the same mistake.

Regards,
Elwyn

> Sriram, can you make the required changes as necessary to the holding
> pattern copy assuming we all agree?
> 
> Cheers
> Terry


From elwynd@folly.org.uk  Thu Dec 20 07:56:46 2012
Return-Path: <elwynd@folly.org.uk>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5B8421F8867 for <gen-art@ietfa.amsl.com>; Thu, 20 Dec 2012 07:56:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.979
X-Spam-Level: 
X-Spam-Status: No, score=-1.979 tagged_above=-999 required=5 tests=[AWL=0.621,  BAYES_00=-2.599]
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 jSWcxuzmq3l5 for <gen-art@ietfa.amsl.com>; Thu, 20 Dec 2012 07:56:44 -0800 (PST)
Received: from a.painless.aa.net.uk (a.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e33]) by ietfa.amsl.com (Postfix) with ESMTP id 55D6D21F88E8 for <gen-art@ietf.org>; Thu, 20 Dec 2012 07:56:43 -0800 (PST)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by a.painless.aa.net.uk with esmtp (Exim 4.77) (envelope-from <elwynd@folly.org.uk>) id 1TliUC-00011M-L1; Thu, 20 Dec 2012 15:56:40 +0000
From: Elwyn Davies <elwynd@folly.org.uk>
To: General Area Review Team <gen-art@ietf.org>
In-Reply-To: <1346249698.4622.5806.camel@mightyatom.folly.org.uk>
References: <1346249698.4622.5806.camel@mightyatom.folly.org.uk>
Content-Type: text/plain
Organization: Folly Consulting
Date: Thu, 20 Dec 2012 15:56:09 +0000
Message-Id: <1356018970.11916.15371.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-savi-dhcp.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art telechat review of draft-ietf-savi-dhcp-14
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Dec 2012 15:56:46 -0000

For the record:

Version 15 of draft-ietf-savi-dhcp from 2012-09-11 addressed to some
extent most of the issues listed here.  However the points in the
summary were not covered and the document is still difficult to
understand and I would be doubtful that interoperable implementations
could be generated from the specification as it stands.

I understand that this is hopefully being addressed at present and I
will carry out a fuller re-review when this work is published.

I would be grateful if the authors or document shepherd could ping me
when this is done as gen-art reviewers are not on the usual automatic
notification list.

Regards,
Elwyn

On Wed, 2012-08-29 at 15:15 +0100, Elwyn Davies wrote:
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> < http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> 
> Please wait for direction from your document shepherd
> or AD before posting a new version of the draft.
> 
> Document: draft-ietf-savi-dhcp-14.txt
> Reviewer: Elwyn Davies
> Review Date: 28 August 2012
> IETF LC End Date: - 
> IESG Telechat date: 30 August 2012
> 
> Summary:
> Not ready.
> The explanation of SAVI Protection Perimeters and other matters in s2 of
> RFC 6620 is very significantly better than the work in this draft, and
> appears in many ways to be equally applicable.  Either duplicating and
> adapting the RFC 6620 work in this draft or, better still, referencing
> it so far as is possible and providing some differences would be a
> significant improvement for this draft.
> 
> There are still a significant number of language issues including a
> large number of missing indefinite articles, not all of which I have
> noted below.
> 
> Major issues:
> 
> Minor issues:
> s1, para 3: Suggestions for other SAVI mechanisms would be a good idea.
> I think FCFS is mentioned later.
> 
> s5.1, para 2: 
> >    Considering the trivial of configuration, it is expected SAVI-DHCP
> >    function will not cause a break of the network even though an
> >    attribute is not configured.  Thus, data packet filtering will not be
> >    performed on binding anchor with no attribute.
> I cannot parse the first sentence of this para. It strikes me that
> having a default of 'let everything through' is not very robust.  This
> is discussed in RFC 6620 where ports (which are actually what get
> attributes in most cases) are either Trusted or not. 
> 
> s6.1: I failed to note during LC that recording the Lifetime of a
> binding is not very useful.  If recording the Lifetime is needed then
> one really wants to record the expiry time of the binding (i.e. the DHCP
> lease) - logically recording the Lifetime is useless without the start
> time or the implementation has to be specified to count down the
> lifetimes of all bindings.
> 
> s6.2: Why should this draft seek to constrain the implementation of the 
> proposal by mandating that a SAVI device 'MUST only use' a binding 
> table that is not necessarily associated with the SAVI code?  Leave it
> to the implementor to decide.
> 
> s7.3.2, s7.4.1.2 and s13.2 (and other places): The concept of 'binding
> entry limit' is not defined.  It is unclear in s7 whether this is
> supposed to be a per anchor or per device limit.  It is also unclear
> what the purpose of having such a limit is until s13.2.  The text in
> s7.3.2: 
> > For any message that may
> >    trigger a new binding, the binding entry limit (cf. Section 13.2) on
> >    the corresponding binding anchor MUST NOT have not been reached.
> implies a per-anchor limit but apparently conflicts with the text in
> s7.4.1.2 which might imply a per device limit: 
> > The binding entry limit can be exceeded when setting up bindings for
> >    all addresses in a REPLY message.  If there is enough binding entry
> >    resources, corresponding new entries MUST be generated even when the
> >    binding number limit is exceeded.  In case that there is not enough
> >    resources left, the message MUST be discarded.
> The MUST NOT in the s7.3.2 is not a protocol specification issue - the
> SAVI node has no control over how many addresses are given to an
> interface by DHCP so that the count can exceed the specified max - SAVI
> just has to cope with this.
> 
> S7.3.2 should refer to s13.2 to explain that excessive bindings is a
> potential security risk.
> Altogether this sections need to be made consistent.
> 
> In s13.2 a mitigation for binding entry limit overload is suggested to
> be limiting the DHCP Request rate.  It is unclear that SAVI has any
> control over this - or is it intended that SAVI should monitor the
> request rate and discard excess messages?
> 
> s7.4.2.2: (DHCP)LEASEQUERY requests SHOULD be authenticated (probably
> with IPSEC - not surprisingly) - is this envisioned?  The answer to this
> question when asked in the previous review misinterpreted the question.
> A discussion of how LEASEQUERY messages will be authenticated is
> required.
> 
> Nits/editorial comments:
> Abstract: s/on SAVI/on a SAVI/
> Abstract; s1 para 1; and more generally: 'filter' - to what end? filter
> just means distinguish the packets - 'identify', 'reject' or 'discard'
> is what you mean maybe. More generally in this document the use of
> 'filter' with the implicit (I take it) meaning of discard is confusing.
> There is a particular case in the second para of s5.1 where this is
> problematic. 
> Abstract: Links do not generate packets.
> Abstract: s/complement of/complement to/
> 
> s1, para 2:  The term 'binding recovery procedure' is not defined.  It
> would be useful to have some idea of why we want to define one before
> saying it isn't discussed in [BA2007].
> s1, para 3: 'only DHCP addresses': Presumably you mean again 'IP
> addresses assigned to an interface via DHCP' . It would probably be
> helpful to define a term for this rather than assuming 'DHCP address'.
> 
> s3: 'SAVI-DHCP': I am unclear what is being named here.  Is this the
> whole set of devices or a mechanism?  What is a 'SAVI instance'? Do you
> mean 'SAVI capability'? - also applies to definition of '(Non-)SAVI
> device' definitions.
> 
> s4, para 1: s/DHCP relay/A DHCP relay/
> 
> s4, para 2: 
> > Protection perimeter (refer to Section 4 in [savi-framework]) is
> >    formed by SAVI Device A and SAVI Device B for scalability.
> What has scalability to do with this?
> 
> s6.2, para 1: The two sentences need to be interchanged so that the
> description of the table content comes first.
> 
> 
> s5.1, para 1:
> > thus, server type DHCP messages
> >    from the binding anchor with no attribute will be discarded.
> For consistency this should be about 'DHCP server/relay' messages.
> 
> s5.1, para 2:
> > For example, in Figure 1, on the binding anchor of SAVI Device A
> >    connected to Router B, it is unreasonable to set up bindings for the
> >    host behind Router B, or filter out traffic from Router B, or allow
> >    forged DHCP message from Router B. Thus, no attribute should be
> >    configured on this binding anchor.
> Some explanation of why it is unreasonable to do these things would be
> desirable.  After reading this several times, I think that is trying to
> say that we have to let all the data packets through but discard (bogus)
> DHCP messages, but I am not sure about this.  As I mentioned in the
> previous review it is unclear how bogus DHCP messages would be
> distinguished in a case where the binding anchors are not configured.
> 
> s5.2:
> > SAVI-Validation attribute is used on a binding anchor on which the
> >    source address of data packet and DHCP message is to be validated.
> >    The filtering process on the binding anchor with such attribute is
> >    described in section 9.
> Section 9 talks about 'data packets and control packets'.  The latter
> are more than just DHCP messages. 
> 
> s5.4, para 3:
> > However only when a
> >    binding anchor is on the protection perimeter and connected to
> >    another link, then it can have no attribute after configuration.
> I don't understand the phrase' connected to another link. A binding
> anchor is associated with a link/interface... what is connected to
> another link?  
> 
> s7: It would be worth stating that the procedure uses a state machine.
> 
> s7.3.2: As noted in the previous review, the term 'control messages'
> from s9.2 covers NDP messages as well as DHCP messages.  It would be
> clearer to use server/relay DHCP message term as only DHCP mesages cause
> events. 
> 
> s7.3.2/s7.5: What happens if a control message arrives but does not 
> generate a valid event?  The authors made a statement about this in
> response to a previous review but have not specified what happens in the
> document (apparently discarding the event with no action).
> 
> s7.4.1.2:
> > If the binding anchor is not a link layer address and there is not a
> >    mapping table from the link layer address to the binding anchor, the
> >    message SHOULD be discarded.
> What else might happen here if the message is NOT discarded?  It strikes
> me that this is a node misconfiguration rather than a protocol error.
> 
> s7.4.2.2:
> > If there is no such an entry, the SAVI device
> >    MUST send a LEASEQUERY [RFC5007] message querying by IP address to
> >    All_DHCP_Relay_Agents_and_Servers multicast address [RFC3315] or a
> >    configured server address. 
> RFC 5007 is IPv6 specific.  If the EVE_DHCP_REPLY_NOLEASE event is
> generated as a result of a DHCPv4 event then the relevant RFC is 4388
> and it sends DHCPLEASEQUERY messages.
> 
> s8.1: What is the rationale for doing the queries twice in stage 1? -
> needs explaining still.
> 
> s13: Discussion of TID spoofing?
> 


From dromasca@avaya.com  Thu Dec 20 09:41:32 2012
Return-Path: <dromasca@avaya.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1CE821F8A53 for <gen-art@ietfa.amsl.com>; Thu, 20 Dec 2012 09:41:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.42
X-Spam-Level: 
X-Spam-Status: No, score=-103.42 tagged_above=-999 required=5 tests=[AWL=0.179, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 G6oSc5fc0rMJ for <gen-art@ietfa.amsl.com>; Thu, 20 Dec 2012 09:41:32 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 14F2E21F8A42 for <gen-art@ietf.org>; Thu, 20 Dec 2012 09:41:31 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0JAKUvoFCHCzI1/2dsb2JhbABEgmzAaYEBB4IgAQEDEigtEhIBFQcOFEImAQQODRMHh2gBCp4mnACRfmEDlxiEcYo2gm+CGQ
X-IronPort-AV: E=Sophos;i="4.80,759,1344225600"; d="scan'208";a="337200159"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 20 Dec 2012 12:34:41 -0500
Received: from unknown (HELO AZ-FFEXHC04.global.avaya.com) ([135.64.58.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 20 Dec 2012 12:16:59 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC04.global.avaya.com ([135.64.58.14]) with mapi id 14.02.0318.004; Thu, 20 Dec 2012 12:41:30 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART review of draft-bonica-special-purpose-03
Thread-Index: Ac3e2T3mhC4vJXtpR9OoC8AK8RH1tQ==
Date: Thu, 20 Dec 2012 17:41:30 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA04525A@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.45]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Ron Bonica <rbonica@juniper.net>, "Ralph Droms \(rdroms\)" <rdroms@cisco.com>
Subject: [Gen-art] Gen-ART review of draft-bonica-special-purpose-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Dec 2012 17:41:33 -0000

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments you m=
ay receive.

Document: draft-bonica-special-purpose-03
Reviewer: Dan Romascanu
Review Date: 12/20/12
IETF LC End Date: 01/02/13
IESG Telechat date: 01/10/13

Summary:

This is a well written, clear, and aparently simple document. It instructs =
IANA to restructure its IPv4 and IPv6 Special-Purpose Address Registries, u=
pdates the RFCs that define the current structure of the IPv4 and IPv6 Spec=
ial-Purpose Address Registries, and obsoletes the RFCs that currently docum=
ent the Special-Use IPv4 and IPv6 addresses. During the IETF Last Call one =
major issue was raised, and this issue needs to be clarified before the IES=
G decides how to proceed with this document. A small number of minor issues=
 and editorial comments can be easily resolved.=20


Major issues:

Geoff Hunt pointed during the IETF Last Call that this document actually de=
als with two different categories of addresses:=20
- address reservations for which the functionality should be included in th=
e IP stacks
- special purpose assignments for which special treatment should be configu=
rable by the IP stacks

(see https://www.ietf.org/ibin/c5i?mid=3D6&rid=3D49&gid=3D0&k1=3D933&k2=3D6=
6219&tid=3D1356023982)=20

In its current form the content of the new registry documented by the I-D d=
oes not make a distinction between the two categories. There are two soluti=
ons to overcome this, one would be to define separate registries, the other=
 to add a field to the current tables that makes the distinction between th=
e two.=20

Minor issues:

1. The Security Considerations section in RFC 5156 which is obsoleted by th=
is document included:=20

   Filtering the invalid routing prefixes listed in this document should
   improve the security of networks.

This has not been taken upon by the new I-D, although it looked like a usef=
ul recommendation.=20

Similarly RFC 5735 included warning text about the unexpected usage of spec=
ial purposes addresses which was not carried over in this document.=20

2. RFC 5735 included in the IANA consideration section the following recomm=
endation:=20

   As required by [RFC2860], the IANA will also make necessary
   experimental assignments of IPv4 addresses, also in consultation with
   the Regional Internet Registries.

There is no such recommendation in the new proposal, actually there is noth=
ing about experimental assignments.=20

Nits/editorial comments:

In Table 11 Allocation Date is stated as February 196 - needs to be correct=
ed (probably February 1996)



From peter@akayla.com  Thu Dec 20 09:55:25 2012
Return-Path: <peter@akayla.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D76921F8A58; Thu, 20 Dec 2012 09:55:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 wuEeQt5NniV7; Thu, 20 Dec 2012 09:55:24 -0800 (PST)
Received: from m1plsmtpa01-08.prod.mesa1.secureserver.net (m1plsmtpa01-08.prod.mesa1.secureserver.net [64.202.165.187]) by ietfa.amsl.com (Postfix) with ESMTP id 373A521F8A56; Thu, 20 Dec 2012 09:55:24 -0800 (PST)
Received: from spectre ([173.8.184.78]) by m1plsmtpa01-08.prod.mesa1.secureserver.net with  id dtvJ1k0061huGat01tvNsd; Thu, 20 Dec 2012 10:55:23 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-avt-rtp-evrc-nw.all@tools.ietf.org>
Date: Thu, 20 Dec 2012 09:55:34 -0800
Message-ID: <049f01cddedb$38f6e0c0$aae4a240$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac3e2rXiaYaUgbG0Sl+xMZvnSdc1cw==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART review of draft-ietf-avt-rtp-evrc-nw-0
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Dec 2012 17:55:25 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at <
http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please wait for direction from your document shepherd or AD before posting a
new version of the draft.

Document: draft-ietf-avt-rtp-evrc-nw-09
Reviewer: Peter Yee
Review Date: Dec-19-2012
IETF LC End Date: Dec-11-2012
IESG Telechat date: Dec-20-2012

Summary: This draft is ready for publication as a Standards Track RFC.



From rbonica@juniper.net  Thu Dec 20 13:47:59 2012
Return-Path: <rbonica@juniper.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F44421F8994 for <gen-art@ietfa.amsl.com>; Thu, 20 Dec 2012 13:47:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.349
X-Spam-Level: 
X-Spam-Status: No, score=-103.349 tagged_above=-999 required=5 tests=[AWL=0.118, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNRESOLVED_TEMPLATE=3.132, USER_IN_WHITELIST=-100]
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 vxEdGhXVEiLI for <gen-art@ietfa.amsl.com>; Thu, 20 Dec 2012 13:47:58 -0800 (PST)
Received: from exprod7og106.obsmtp.com (exprod7og106.obsmtp.com [64.18.2.165]) by ietfa.amsl.com (Postfix) with ESMTP id 8543D21F8AA4 for <gen-art@ietf.org>; Thu, 20 Dec 2012 13:47:58 -0800 (PST)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob106.postini.com ([64.18.6.12]) with SMTP ID DSNKUNOHjqKnZe4C3zheMcMwzUHM5585msOo@postini.com; Thu, 20 Dec 2012 13:47:58 PST
Received: from P-CLDFE01-HQ.jnpr.net (172.24.192.59) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 20 Dec 2012 13:45:58 -0800
Received: from o365mail.juniper.net (207.17.137.149) by o365mail.juniper.net (172.24.192.59) with Microsoft SMTP Server id 14.1.355.2; Thu, 20 Dec 2012 13:45:58 -0800
Received: from va3outboundpool.messaging.microsoft.com (216.32.180.11) by o365mail.juniper.net (207.17.137.149) with Microsoft SMTP Server (TLS) id 14.1.355.2; Thu, 20 Dec 2012 13:48:50 -0800
Received: from mail32-va3-R.bigfish.com (10.7.14.246) by VA3EHSOBE001.bigfish.com (10.7.40.21) with Microsoft SMTP Server id 14.1.225.23; Thu, 20 Dec 2012 21:45:57 +0000
Received: from mail32-va3 (localhost [127.0.0.1])	by mail32-va3-R.bigfish.com (Postfix) with ESMTP id D6C9612021D	for <gen-art@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Thu, 20 Dec 2012 21:45:56 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.238.5; KIP:(null); UIP:(null); (null); H:BY2PRD0512HT001.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -27
X-BigFish: PS-27(zzbb2dI9371I103dK542I1432Izz1de0h1202h1e76h1d1ah1d2ahzz1033IL17326ah8275dhz2dh2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h1155h)
Received: from mail32-va3 (localhost.localdomain [127.0.0.1]) by mail32-va3 (MessageSwitch) id 1356039951313798_30985; Thu, 20 Dec 2012 21:45:51 +0000 (UTC)
Received: from VA3EHSMHS023.bigfish.com (unknown [10.7.14.253])	by mail32-va3.bigfish.com (Postfix) with ESMTP id 257BAE00CE; Thu, 20 Dec 2012 21:45:51 +0000 (UTC)
Received: from BY2PRD0512HT001.namprd05.prod.outlook.com (157.56.238.5) by VA3EHSMHS023.bigfish.com (10.7.99.33) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 20 Dec 2012 21:45:47 +0000
Received: from BY2PRD0512MB653.namprd05.prod.outlook.com ([169.254.5.183]) by BY2PRD0512HT001.namprd05.prod.outlook.com ([10.255.243.34]) with mapi id 14.16.0245.002; Thu, 20 Dec 2012 21:45:39 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART review of draft-bonica-special-purpose-03
Thread-Index: Ac3e2T3mhC4vJXtpR9OoC8AK8RH1tQAH+RzA
Date: Thu, 20 Dec 2012 21:45:38 +0000
Message-ID: <2CF4CB03E2AA464BA0982EC92A02CE2501DF3A3F@BY2PRD0512MB653.namprd05.prod.outlook.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA04525A@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA04525A@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.232.2]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%AVAYA.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%CISCO.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
Cc: "Ralph Droms \(rdroms\)" <rdroms@cisco.com>
Subject: Re: [Gen-art] Gen-ART review of draft-bonica-special-purpose-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Dec 2012 21:47:59 -0000

Hi Dan,

Response inline.....

> -----Original Message-----
> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
> Sent: Thursday, December 20, 2012 12:41 PM
> To: gen-art@ietf.org
> Cc: Ronald Bonica; Ralph Droms (rdroms)
> Subject: Gen-ART review of draft-bonica-special-purpose-03
>=20
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-bonica-special-purpose-03
> Reviewer: Dan Romascanu
> Review Date: 12/20/12
> IETF LC End Date: 01/02/13
> IESG Telechat date: 01/10/13
>=20
> Summary:
>=20
> This is a well written, clear, and aparently simple document. It
> instructs IANA to restructure its IPv4 and IPv6 Special-Purpose Address
> Registries, updates the RFCs that define the current structure of the
> IPv4 and IPv6 Special-Purpose Address Registries, and obsoletes the
> RFCs that currently document the Special-Use IPv4 and IPv6 addresses.
> During the IETF Last Call one major issue was raised, and this issue
> needs to be clarified before the IESG decides how to proceed with this
> document. A small number of minor issues and editorial comments can be
> easily resolved.

Thanks!

>=20
>=20
> Major issues:
>=20
> Geoff Hunt pointed during the IETF Last Call that this document
> actually deals with two different categories of addresses:
> - address reservations for which the functionality should be included
> in the IP stacks
> - special purpose assignments for which special treatment should be
> configurable by the IP stacks
>=20
> (see
> https://www.ietf.org/ibin/c5i?mid=3D6&rid=3D49&gid=3D0&k1=3D933&k2=3D6621=
9&tid=3D13
> 56023982)
>=20
> In its current form the content of the new registry documented by the
> I-D does not make a distinction between the two categories. There are
> two solutions to overcome this, one would be to define separate
> registries, the other to add a field to the current tables that makes
> the distinction between the two.

The later approach is taken in version-04

>=20
> Minor issues:
>=20
> 1. The Security Considerations section in RFC 5156 which is obsoleted
> by this document included:
>=20
>    Filtering the invalid routing prefixes listed in this document
> should
>    improve the security of networks.
>=20
> This has not been taken upon by the new I-D, although it looked like a
> useful recommendation.
>=20
> Similarly RFC 5735 included warning text about the unexpected usage of
> special purposes addresses which was not carried over in this document.

These are both useful recommendations, but beyond the scope of the current =
document, which is an instruction to IANA. This kind of advice should be in=
 an OPSEC document.

>=20
> 2. RFC 5735 included in the IANA consideration section the following
> recommendation:
>=20
>    As required by [RFC2860], the IANA will also make necessary
>    experimental assignments of IPv4 addresses, also in consultation
> with
>    the Regional Internet Registries.
>=20
> There is no such recommendation in the new proposal, actually there is
> nothing about experimental assignments.

RFC 5735 doesn't make any recommendation. It reiterates a requirement state=
d in RFC 2860. Since the current document does not obsolete, update or in a=
ny way affect RFC 2860, there is no need to reiterate that long-standing re=
quirement.

>=20
> Nits/editorial comments:
>=20
> In Table 11 Allocation Date is stated as February 196 - needs to be
> corrected (probably February 1996)
>=20

Good Catch.

>=20



From terry.manderson@icann.org  Thu Dec 20 17:02:40 2012
Return-Path: <terry.manderson@icann.org>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3E2D21E803C for <gen-art@ietfa.amsl.com>; Thu, 20 Dec 2012 17:02:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.992
X-Spam-Level: 
X-Spam-Status: No, score=-105.992 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599, J_CHICKENPOX_43=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 Fw8x1ODXFs58 for <gen-art@ietfa.amsl.com>; Thu, 20 Dec 2012 17:02:39 -0800 (PST)
Received: from EXPFE100-2.exc.icann.org (expfe100-2.exc.icann.org [64.78.22.237]) by ietfa.amsl.com (Postfix) with ESMTP id 5B49C21E8034 for <gen-art@ietf.org>; Thu, 20 Dec 2012 17:02:39 -0800 (PST)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-2.exc.icann.org ([64.78.22.237]) with mapi; Thu, 20 Dec 2012 17:02:38 -0800
From: Terry Manderson <terry.manderson@icann.org>
To: Elwyn Davies <elwynd@dial.pipex.com>
Date: Thu, 20 Dec 2012 17:02:39 -0800
Thread-Topic: Gen-art LC/Telechat review of  draft-ietf-sidr-usecases-05.txt
Thread-Index: Ac3eULh+hOL9I/RCSlaG9FVaISUs3QAxiavp
Message-ID: <CCF9F24F.2E422%terry.manderson@icann.org>
In-Reply-To: <1355966584.11916.15363.camel@mightyatom>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3438932559_6349051"
MIME-Version: 1.0
Cc: "draft-ietf-sidr-usecases.all@tools.ietf.org" <draft-ietf-sidr-usecases.all@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-art LC/Telechat review of draft-ietf-sidr-usecases-05.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Dec 2012 01:02:40 -0000

--B_3438932559_6349051
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit


On 20/12/12 11:23 AM, "Elwyn Davies" <elwynd@dial.pipex.com> wrote:

> Hi, Terry.
> 
> Thanks for the swift reply.
> 
> Looks like all is well with most of he comments.
> 
> I guess the main consclusion would be that you maybe need to put in a
> bit more explanation of the context to which make-before-break applies
> as per your explanation to me below.

I hear you, I will come back to you after Xmas with some expanded draft text
for s2.1.

> 

>>> It is possible that I don't understand the problem, but this appears to
>>> be trying to prove a negative by the existence of something.  What RPKI
>>> object would have to exist to make the route suspicious?
>> 
>> Essentially a valid RPKI ROA object would need to exist that proves a route
>> is suspicious. Because the RPKI+ROA is a "bolt on after the fact" security
>> effort, you can do no more. Simply routing exists now, the RPKI would be
>> deployed in the future. So any route that is seen must be considered
>> intended unless proven otherwise.
> I see now.. perhaps you could add something like:
> ... valid RPKI object that explicitly invalidates the route (see Section
> 7 for examples).

That works for me.

>> 
>>> 
>>> s6.2: Can the make-before-break principle be applied to the resource
>>> certificate for Org B?  Presumably this would mean overlapping existence
>>> of resource certs for Org A and Org B so that the ROA add can occur
>>> before the revoke.  Is this a problem?
>>> 
>> 
>> The preference, I believe (and my co-authors can correct me) is that two
>> different resource certificates (unless one in subordinate to the other)
>> should never exist.
>> 
>> This problem is an open issue in SIDR related to the grandfathering topic.
>> So for now the usecase should be that overlap cannot occur.
> Do you think this needs explicit  mention?

No. I feel it is better to remain silent in the usecases. A requirements
document (should one ever be set as a charter deliverable) would define that
behaviour, which would then be reinforced by the RPKI architecture.

I personally feel it is better to bis this document should change be needed.


>> work for you?
> 
> Maybe 'through two or more' but basically 'yes, thanks'.

Works for me.

>> 

>>> describe the add before the revoke in each case?
>> 
>> ahh.. I think we have a disconnect. make before break is considered in the
>> routing sense that a route is considered o.k. (UNKNOWN) unless proven
>> otherwise, this means you can remove ALL RPKI object for a route, and it
>> will still exist happily until a new and conflicting RPKI ROA is created..
>> And we are working to that. Not necessarily making a new valid object before
>> breaking the old valid object. That would then imply ownership of a prefix
>> can then be in two places at the same time. And like the transfer of title
>> for a house, overlap tends to be considered a bad thing. (co-authors, chime
>> in here!)
>> 
> See initial comment.. this is a useful explanation and some words to
> this effect would avoid others with equally bad understanding of the
> RPKI scenario making the same mistake.
> 

Ack. Will run draft text past co-authors and bring back post xmas.

Terry

--B_3438932559_6349051
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIIQAQYJKoZIhvcNAQcCoIIP8jCCD+4CAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
Dc0wggcDMIIF66ADAgECAhAPz2lJUZsAlD35l4oJxf0FMA0GCSqGSIb3DQEBBQUAMGIxCzAJ
BgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNVBAsTEHd3dy5kaWdpY2Vy
dC5jb20xITAfBgNVBAMTGERpZ2lDZXJ0IEFzc3VyZWQgSUQgQ0EtMTAeFw0xMjAzMjcwMDAw
MDBaFw0xNTAzMjcxMjAwMDBaMIGsMQswCQYDVQQGEwJVUzETMBEGA1UECBMKQ2FsaWZvcm5p
YTEXMBUGA1UEBxMOTWFyaW5hIGRlbCBSZXkxPDA6BgNVBAoTM0ludGVybmV0IENvcnBvcmF0
aW9uIGZvciBBc3NpZ25lZCBOYW1lcyBhbmQgTnVtYmVyczEXMBUGA1UECxMORE5TIE9wZXJh
dGlvbnMxGDAWBgNVBAMTD1RlcnJ5IE1hbmRlcnNvbjCCASIwDQYJKoZIhvcNAQEBBQADggEP
ADCCAQoCggEBAKRhZ4W3U6MnfS2woYEFCIyN+g1MNILokbUKk+PTl5mmK3QtWQxTSOu2sdzN
xHMy6p2RoT9BMGOamttFq2WswSru6/7JT1TflytGaPHfK5kMP/pI47hmcwUEm9Z169I5ar7z
BTiEAQA06cGKtgJ8XiiLFUIHLVuRq3WGxjnFTHlAHXY6mdgDT/ntAnoEvvPVm4XqUnjJiZTS
ojzyr1q2RqFvyXs2blOARumDqvLI33yLGcUuaEL+A+hgodzM/fL4kdoy964mXvmEerpm4d4f
Y/JfbRUWxc0Eomu9nwGFNk6ijO41qk+OIboct2qeA+5PPclXJNNHYVfzT2dyWfGgxaMCAwEA
AaOCA2gwggNkMB8GA1UdIwQYMBaAFBUAEisTmLKZB+0e36K+Vw0rZwLNMB0GA1UdDgQWBBSz
wvR2YXpP9XjS9cknMX5g3LM2jTAkBgNVHREEHTAbgRl0ZXJyeS5tYW5kZXJzb25AaWNhbm4u
b3JnMA4GA1UdDwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwfQYD
VR0fBHYwdDA4oDagNIYyaHR0cDovL2NybDMuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0QXNzdXJl
ZElEQ0EtMS5jcmwwOKA2oDSGMmh0dHA6Ly9jcmw0LmRpZ2ljZXJ0LmNvbS9EaWdpQ2VydEFz
c3VyZWRJRENBLTEuY3JsMIIBxQYDVR0gBIIBvDCCAbgwggG0BgpghkgBhv1sBAECMIIBpDA6
BggrBgEFBQcCARYuaHR0cDovL3d3dy5kaWdpY2VydC5jb20vc3NsLWNwcy1yZXBvc2l0b3J5
Lmh0bTCCAWQGCCsGAQUFBwICMIIBVh6CAVIAQQBuAHkAIAB1AHMAZQAgAG8AZgAgAHQAaABp
AHMAIABDAGUAcgB0AGkAZgBpAGMAYQB0AGUAIABjAG8AbgBzAHQAaQB0AHUAdABlAHMAIABh
AGMAYwBlAHAAdABhAG4AYwBlACAAbwBmACAAdABoAGUAIABEAGkAZwBpAEMAZQByAHQAIABD
AFAALwBDAFAAUwAgAGEAbgBkACAAdABoAGUAIABSAGUAbAB5AGkAbgBnACAAUABhAHIAdAB5
ACAAQQBnAHIAZQBlAG0AZQBuAHQAIAB3AGgAaQBjAGgAIABsAGkAbQBpAHQAIABsAGkAYQBi
AGkAbABpAHQAeQAgAGEAbgBkACAAYQByAGUAIABpAG4AYwBvAHIAcABvAHIAYQB0AGUAZAAg
AGgAZQByAGUAaQBuACAAYgB5ACAAcgBlAGYAZQByAGUAbgBjAGUALjB3BggrBgEFBQcBAQRr
MGkwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLmRpZ2ljZXJ0LmNvbTBBBggrBgEFBQcwAoY1
aHR0cDovL2NhY2VydHMuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0QXNzdXJlZElEQ0EtMS5jcnQw
DAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUFAAOCAQEAYpwxK/KvdhbyQqrKp2ylMQpNzqVH
ofo4hPILTnp/o+UyYVn6daWSilaV+XNBzE5Rm/f7ms2iA1zBzOvGv55pLH0n6lgIRTeuAGzf
KIsPCwPvYQkkMAPXHzh9A44m19hvigTgOPNyjzcOTiHqwwCJSDTEZx17CEkrzQPq1vfG1Lvk
+AWjEtxCsGmsuCHHaZjwQ8SsGI7W5cA1Y4RTcQf6S9eIpSsOwXIYdDgWq9Uhi/amW7ryW06Y
GH7BHaitqgmm32MZuid3UzJUU6+Ljx7uGA9Fe6k1uPEHhaXTAoobPSpPdOgGmnxUCRQu2OI7
+I8vHiSe7DC/LmxEDC5kB+lUTjCCBsIwggWqoAMCAQICEAoE3yF0XU0rjOozcgUAUOkwDQYJ
KoZIhvcNAQEFBQAwZTELMAkGA1UEBhMCVVMxFTATBgNVBAoTDERpZ2lDZXJ0IEluYzEZMBcG
A1UECxMQd3d3LmRpZ2ljZXJ0LmNvbTEkMCIGA1UEAxMbRGlnaUNlcnQgQXNzdXJlZCBJRCBS
b290IENBMB4XDTA2MTExMDAwMDAwMFoXDTIxMTExMDAwMDAwMFowYjELMAkGA1UEBhMCVVMx
FTATBgNVBAoTDERpZ2lDZXJ0IEluYzEZMBcGA1UECxMQd3d3LmRpZ2ljZXJ0LmNvbTEhMB8G
A1UEAxMYRGlnaUNlcnQgQXNzdXJlZCBJRCBDQS0xMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A
MIIBCgKCAQEA6IItmfnKwkKVpYBzQHDSnlZUXKnE0kEGj8kz/E1FkVyBn+0snPgWWd+etSQV
wpi5tHdJ3InECtqvy15r7a2wcTHrzzpADEZNk+yLejYIA6sMNP4YSYL+x8cxSIB8HqIPkg5Q
ycaH6zY/2DDD/6b3+6LNb3Mj/qxWBZDwMiEWicZwiPkFl32jx0PdAug7Pe2xQaPtP77blUjE
7h6z8rwMK5nQxl0SQoHhg26Ccz8mSxSQrllmCsSNvtLOBq6thG9IhJtPQLnxTPKvmPv2zkBd
XPao8S+v7Iki8msYZbHBc63X8djPHgp0XEK4aH631XcKJ1Z8D2KkPzIUYJX9BwSiCQIDAQAB
o4IDbzCCA2swDgYDVR0PAQH/BAQDAgGGMDsGA1UdJQQ0MDIGCCsGAQUFBwMBBggrBgEFBQcD
AgYIKwYBBQUHAwMGCCsGAQUFBwMEBggrBgEFBQcDCDCCAcYGA1UdIASCAb0wggG5MIIBtQYL
YIZIAYb9bAEDAAQwggGkMDoGCCsGAQUFBwIBFi5odHRwOi8vd3d3LmRpZ2ljZXJ0LmNvbS9z
c2wtY3BzLXJlcG9zaXRvcnkuaHRtMIIBZAYIKwYBBQUHAgIwggFWHoIBUgBBAG4AeQAgAHUA
cwBlACAAbwBmACAAdABoAGkAcwAgAEMAZQByAHQAaQBmAGkAYwBhAHQAZQAgAGMAbwBuAHMA
dABpAHQAdQB0AGUAcwAgAGEAYwBjAGUAcAB0AGEAbgBjAGUAIABvAGYAIAB0AGgAZQAgAEQA
aQBnAGkAQwBlAHIAdAAgAEMAUAAvAEMAUABTACAAYQBuAGQAIAB0AGgAZQAgAFIAZQBsAHkA
aQBuAGcAIABQAGEAcgB0AHkAIABBAGcAcgBlAGUAbQBlAG4AdAAgAHcAaABpAGMAaAAgAGwA
aQBtAGkAdAAgAGwAaQBhAGIAaQBsAGkAdAB5ACAAYQBuAGQAIABhAHIAZQAgAGkAbgBjAG8A
cgBwAG8AcgBhAHQAZQBkACAAaABlAHIAZQBpAG4AIABiAHkAIAByAGUAZgBlAHIAZQBuAGMA
ZQAuMA8GA1UdEwEB/wQFMAMBAf8wfQYIKwYBBQUHAQEEcTBvMCQGCCsGAQUFBzABhhhodHRw
Oi8vb2NzcC5kaWdpY2VydC5jb20wRwYIKwYBBQUHMAKGO2h0dHA6Ly93d3cuZGlnaWNlcnQu
Y29tL0NBQ2VydHMvRGlnaUNlcnRBc3N1cmVkSURSb290Q0EuY3J0MIGBBgNVHR8EejB4MDqg
OKA2hjRodHRwOi8vY3JsMy5kaWdpY2VydC5jb20vRGlnaUNlcnRBc3N1cmVkSURSb290Q0Eu
Y3JsMDqgOKA2hjRodHRwOi8vY3JsNC5kaWdpY2VydC5jb20vRGlnaUNlcnRBc3N1cmVkSURS
b290Q0EuY3JsMB0GA1UdDgQWBBQVABIrE5iymQftHt+ivlcNK2cCzTAfBgNVHSMEGDAWgBRF
66Kv9JLLgjEtUYunpyGd823IDzANBgkqhkiG9w0BAQUFAAOCAQEAhGFOQR64dgQqtbbvj/JV
hbldVv4KmObkvWWKfUAp0/yxXUX9OrgqWzNLJFzNubTkc61hXXatdDOKZtUjr0wfcm5F2XVA
u6I7z41JL8BBsOIpo1E4Q1CZFKwzBjViiX13qVIH5WwgV7aBum+8s8KU7XYCgNl8zoWoHOzH
Q0pLsVfPcs7f9SU8yyJP/Z9S0TfLCLs4PuDVPm95Ca1bfDGzdzXD5GP5aAqYB+dGOHeE0j6X
vAqgqKwlT0RukeHSWq9r7zAcjaNEQrMQiyP61+Y1dDesz+urWB/JiCP/NtQH6jRqR+qdlWye
KU9T7eMrlSBOKs+WYHr4LIDwlVLOKZaBYjGCAfwwggH4AgEBMHYwYjELMAkGA1UEBhMCVVMx
FTATBgNVBAoTDERpZ2lDZXJ0IEluYzEZMBcGA1UECxMQd3d3LmRpZ2ljZXJ0LmNvbTEhMB8G
A1UEAxMYRGlnaUNlcnQgQXNzdXJlZCBJRCBDQS0xAhAPz2lJUZsAlD35l4oJxf0FMAkGBSsO
AwIaBQCgXTAjBgkqhkiG9w0BCQQxFgQUDDAW83VbeZFOukDJmvhHM41yueIwGAYJKoZIhvcN
AQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTIxMjIxMDEwMjM5WjANBgkqhkiG
9w0BAQEFAASCAQCCZSXnZSBPwP7YMGzh1BOkVDsiHn2M1pEZ81OrqoLtLwV/6PfQXW16OZH5
QqgkKBbcPec/HMnQWyY4gGbgPdJt/Eq+GEYYVskiR7hRyTxsNLAKQqP0E+wJfpvAbWgTrCdO
5yv3oMaXhQMnqoIoZQJZGXIvJB5b1dJw87PSFSVMvl0nmvybcrWV/TXtb+6S+TSfnqxKZRhu
xorouQnheIKio/7IqRfOcTbMdkWPC4WwuJTY5egPhVNLxYqew+rAlCIyfkENc23omUkTzgdO
ILcwqYgrBFRGe9X2w8NoblUz0UB+Y5hcpP8SmOGs9Qeui1kPWytjPCOMo9FQcs0+rlc6

--B_3438932559_6349051--

From elwynd@dial.pipex.com  Fri Dec 21 04:07:24 2012
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2BCE21F8953 for <gen-art@ietfa.amsl.com>; Fri, 21 Dec 2012 04:07:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.249
X-Spam-Level: 
X-Spam-Status: No, score=-102.249 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, J_CHICKENPOX_43=0.6, USER_IN_WHITELIST=-100]
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 Kjc7SMHgZXN2 for <gen-art@ietfa.amsl.com>; Fri, 21 Dec 2012 04:07:24 -0800 (PST)
Received: from auth.a.painless.aa.net.uk (a.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e33]) by ietfa.amsl.com (Postfix) with ESMTP id E506321F885C for <gen-art@ietf.org>; Fri, 21 Dec 2012 04:07:23 -0800 (PST)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by a.painless.aa.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <elwynd@dial.pipex.com>) id 1Tm1Ni-0005Ox-Eg; Fri, 21 Dec 2012 12:07:17 +0000
From: Elwyn Davies <elwynd@dial.pipex.com>
To: Terry Manderson <terry.manderson@icann.org>
In-Reply-To: <CCF9F24F.2E422%terry.manderson@icann.org>
References: <CCF9F24F.2E422%terry.manderson@icann.org>
Content-Type: text/plain
Date: Fri, 21 Dec 2012 12:06:42 +0000
Message-Id: <1356091602.11916.15388.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
X-Spam-Score-a.painless.aa.net.uk: -4.0
Cc: "draft-ietf-sidr-usecases.all@tools.ietf.org" <draft-ietf-sidr-usecases.all@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-art LC/Telechat review of draft-ietf-sidr-usecases-05.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Dec 2012 12:07:24 -0000

Hi, Terry.

That's all fine by me.

Have a great Christmas!

Elwyn 

On Thu, 2012-12-20 at 17:02 -0800, Terry Manderson wrote:
> On 20/12/12 11:23 AM, "Elwyn Davies" <elwynd@dial.pipex.com> wrote:
> 
> > Hi, Terry.
> > 
> > Thanks for the swift reply.
> > 
> > Looks like all is well with most of he comments.
> > 
> > I guess the main consclusion would be that you maybe need to put in a
> > bit more explanation of the context to which make-before-break applies
> > as per your explanation to me below.
> 
> I hear you, I will come back to you after Xmas with some expanded draft text
> for s2.1.
> 
> > 
> 
> >>> It is possible that I don't understand the problem, but this appears to
> >>> be trying to prove a negative by the existence of something.  What RPKI
> >>> object would have to exist to make the route suspicious?
> >> 
> >> Essentially a valid RPKI ROA object would need to exist that proves a route
> >> is suspicious. Because the RPKI+ROA is a "bolt on after the fact" security
> >> effort, you can do no more. Simply routing exists now, the RPKI would be
> >> deployed in the future. So any route that is seen must be considered
> >> intended unless proven otherwise.
> > I see now.. perhaps you could add something like:
> > ... valid RPKI object that explicitly invalidates the route (see Section
> > 7 for examples).
> 
> That works for me.
> 
> >> 
> >>> 
> >>> s6.2: Can the make-before-break principle be applied to the resource
> >>> certificate for Org B?  Presumably this would mean overlapping existence
> >>> of resource certs for Org A and Org B so that the ROA add can occur
> >>> before the revoke.  Is this a problem?
> >>> 
> >> 
> >> The preference, I believe (and my co-authors can correct me) is that two
> >> different resource certificates (unless one in subordinate to the other)
> >> should never exist.
> >> 
> >> This problem is an open issue in SIDR related to the grandfathering topic.
> >> So for now the usecase should be that overlap cannot occur.
> > Do you think this needs explicit  mention?
> 
> No. I feel it is better to remain silent in the usecases. A requirements
> document (should one ever be set as a charter deliverable) would define that
> behaviour, which would then be reinforced by the RPKI architecture.
> 
> I personally feel it is better to bis this document should change be needed.
> 
> 
> >> work for you?
> > 
> > Maybe 'through two or more' but basically 'yes, thanks'.
> 
> Works for me.
> 
> >> 
> 
> >>> describe the add before the revoke in each case?
> >> 
> >> ahh.. I think we have a disconnect. make before break is considered in the
> >> routing sense that a route is considered o.k. (UNKNOWN) unless proven
> >> otherwise, this means you can remove ALL RPKI object for a route, and it
> >> will still exist happily until a new and conflicting RPKI ROA is created..
> >> And we are working to that. Not necessarily making a new valid object before
> >> breaking the old valid object. That would then imply ownership of a prefix
> >> can then be in two places at the same time. And like the transfer of title
> >> for a house, overlap tends to be considered a bad thing. (co-authors, chime
> >> in here!)
> >> 
> > See initial comment.. this is a useful explanation and some words to
> > this effect would avoid others with equally bad understanding of the
> > RPKI scenario making the same mistake.
> > 
> 
> Ack. Will run draft text past co-authors and bring back post xmas.
> 
> Terry


From RAMAKRISHNADTV@infosys.com  Fri Dec 21 04:48:38 2012
Return-Path: <RAMAKRISHNADTV@infosys.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C19BA21F84FB; Fri, 21 Dec 2012 04:48:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 TwqIW5rQDMAu; Fri, 21 Dec 2012 04:48:37 -0800 (PST)
Received: from KECGATE08.infosys.com (kecgate08.infosysconsulting.com [122.98.10.33]) by ietfa.amsl.com (Postfix) with ESMTP id EA2D421F84F5; Fri, 21 Dec 2012 04:48:36 -0800 (PST)
X-TM-IMSS-Message-ID: <5051633600276dbe@infosys.com>
Received: from blrkechub01.ad.infosys.com ([10.66.236.41]) by infosys.com ([122.98.10.33]) with ESMTP (TREND IMSS SMTP Service 7.1) id 5051633600276dbe ; Fri, 21 Dec 2012 18:23:03 +0530
Received: from BLRKECHUB07.ad.infosys.com (10.66.236.117) by blrkechub01.ad.infosys.com (10.66.236.41) with Microsoft SMTP Server (TLS) id 8.2.176.0; Fri, 21 Dec 2012 18:18:12 +0530
Received: from BLRKECMBX23.ad.infosys.com ([fe80::d9f9:2028:fd8:1e35]) by BLRKECHUB07.ad.infosys.com ([::1]) with mapi id 14.02.0318.004; Fri, 21 Dec 2012 18:18:12 +0530
From: RAMAKRISHNADTV <RAMAKRISHNADTV@infosys.com>
To: Ben Campbell <ben@nostrum.com>, "draft-ietf-dhc-relay-id-suboption.all@tools.ietf.org" <draft-ietf-dhc-relay-id-suboption.all@tools.ietf.org>
Thread-Topic: Gen-ART LC Review of draft-ietf-dhc-relay-id-suboption-11
Thread-Index: AQHN3i35q1rCmEQ/mUyYBxRcqJiFtpgi7Klw
Date: Fri, 21 Dec 2012 12:48:13 +0000
Message-ID: <F2B120E98374B2448745C1117BDA1854238F281F@BLRKECMBX23.ad.infosys.com>
References: <BE996F07-CFB7-47F5-8B17-FA651C294FA3@nostrum.com>
In-Reply-To: <BE996F07-CFB7-47F5-8B17-FA651C294FA3@nostrum.com>
Accept-Language: en-US, en-IN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.66.236.147]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 21 Dec 2012 05:20:15 -0800
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>, Bharat Joshi <bharat_joshi@infosys.com>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-dhc-relay-id-suboption-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Dec 2012 12:48:38 -0000

Hi Ben,

Thank you for your review comments. 
Please find my responses inline below.

Regards,
Ramakrishna DTV.

>-----Original Message-----
>From: Ben Campbell [mailto:ben@nostrum.com]
>Sent: Thursday, December 20, 2012 2:45 AM
>To: draft-ietf-dhc-relay-id-suboption.all@tools.ietf.org
>Cc: gen-art@ietf.org Review Team; ietf@ietf.org List
>Subject: Gen-ART LC Review of draft-ietf-dhc-relay-id-suboption-11
>
>I am the assigned Gen-ART reviewer for this draft. For background on
>Gen-ART, please see the FAQ at
>
><http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
>Please resolve these comments along with any other Last Call comments
>you may receive.
>
>Document: draft-ietf-dhc-relay-id-suboption-11
>Reviewer: Ben Campbell
>Review Date: 2012-12-19
>IETF LC End Date: 2013-01-07
>
>Summary: This draft is basically ready for publication as a proposed
>standard. However, there is one comment from a prior review that I am
>not sure whether is resolved.
>
>Major issues:
>
>None
>
>Minor issues:
>
>-- In Sean Turner's 2009 review of version 07 of the document [
>http://www.ietf.org/mail-archive/web/gen-art/current/msg04614.html ], he
>made the following comment:
>
>> In the security considerations it says look to RFC 3046 and
>> RFC 4030 for security considerations and then says SHOULD use the
>relay
>> agent authentication option from RFC 4030.  RFC 3046 is targeted at
>> network infrastructures that are "trusted and secure" and RFC 4030
>> allows the relay agent to be part of this trusted and secure network.
>> If an implementation doesn't use the relay agent authentication
>option,
>> then the relay agent can't be part of the "trusted and secure"
>network.

RFC3046 created the relay agent information option.
Relay agent information option exists only in the messages between
relay agents and DHCP servers. RFC3046 is targeted at network infrastruct=
ures
that are "trusted and secure" as far as the paths among relay agents and =
DHCP
servers is concerned. In many deployments, relay agents and DHCP servers 
are under a single administrative control. By careful design and engineer=
ing 
of the network, it is possible to ensure that the network infrastructure 
comprising relay agents and DHCP server is trusted and secure. To achieve=
 that,
RFC4030 may be used but is not a MUST. If not, RFC4030 would already be a=
 MUST 
for RFC3046 deployment. But that is not currently the case.

>>  This makes me think that the relay agent authentication option from
>> RFC 4030 ought to be a MUST not a SHOULD?
>
>I can't tell from the resulting conversation if that comment is
>addressed in the current text. Additional text has been added, but the
>SHOULD remains. I'm willing to accept it has been addressed if the
>author's say so--I only mention it to make sure it didn't fall through a
>crack.
>

We have indeed discussed about this comment and addressed it.

The following was a related comment from DHC WG Chair (Ted Lemon) 
(http://www.ietf.org/mail-archive/web/gen-art/current/msg04615.html):

=09"This document makes no changes to practice that require more or less =
security 
=09than is provided by existing relay agent options in RFC3046. Thus, the=
 
=09security considerations in RFC3046 should be adequate."

As Ted mentioned, our draft only proposes a new sub-option for relay-agen=
t 
option which was originally created as part of RFC3046. So, the security 
considerations for RFC3046 apply to our draft as well. RFC3046 deployment=
s may
use RFC4030 as explained above. So, we indicated in our draft to refer to=
 
both RFC3046 and RFC4030. But there are no specific security issues in th=
e 
new relay-id sub-option itself to make RFC4030 a MUST.


>Nits/editorial comments:
>
>-- section 5, last paragraph:
>
>I suggest removing the scare quotes around "stability". If there are
>concerns about whether such stability is real, it would be better to say
>that directly.
>

There is no need for these scare quotes. We will remove them.

>-- informative references:
>
>draft-ietf-dhc-dhcpv4-bulk-leasequery-06 is now 07

We will update this.

>

**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended sol=
ely 
for the use of the addressee(s). If you are not the intended recipient, p=
lease 
notify the sender by e-mail and delete the original message. Further, you=
 are not 
to copy, disclose, or distribute this e-mail or its contents to any other=
 person and 
any such actions are unlawful. This e-mail may contain viruses. Infosys h=
as taken 
every reasonable precaution to minimize this risk, but is not liable for =
any damage 
you may sustain as a result of any virus in this e-mail. You should carry=
 out your 
own virus checks before opening the e-mail or attachment. Infosys reserve=
s the 
right to monitor and review the content of all messages sent to or from t=
his e-mail 
address. Messages sent to or from this e-mail address may be stored on th=
e 
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***

From Ted.Lemon@nominum.com  Fri Dec 21 06:27:25 2012
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4085221F8CEC; Fri, 21 Dec 2012 06:27:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.576
X-Spam-Level: 
X-Spam-Status: No, score=-106.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 W5-M1IimCRLw; Fri, 21 Dec 2012 06:27:24 -0800 (PST)
Received: from exprod7og115.obsmtp.com (exprod7og115.obsmtp.com [64.18.2.217]) by ietfa.amsl.com (Postfix) with ESMTP id 2CDE421F8C93; Fri, 21 Dec 2012 06:27:24 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob115.postini.com ([64.18.6.12]) with SMTP ID DSNKUNRxyxyV6ezR4sIheTm/JB5fY/f81T6O@postini.com; Fri, 21 Dec 2012 06:27:24 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id A8FDB1B812D; Fri, 21 Dec 2012 06:27:23 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 9F1D1190052; Fri, 21 Dec 2012 06:27:23 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Fri, 21 Dec 2012 06:27:17 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: RAMAKRISHNADTV <RAMAKRISHNADTV@infosys.com>
Thread-Topic: Gen-ART LC Review of draft-ietf-dhc-relay-id-suboption-11
Thread-Index: AQHN3i33Q3+/pWXDrEC14WiRxtRL+pgjvKCAgAAbrIA=
Date: Fri, 21 Dec 2012 14:27:17 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307474418FF@mbx-01.win.nominum.com>
References: <BE996F07-CFB7-47F5-8B17-FA651C294FA3@nostrum.com> <F2B120E98374B2448745C1117BDA1854238F281F@BLRKECMBX23.ad.infosys.com>
In-Reply-To: <F2B120E98374B2448745C1117BDA1854238F281F@BLRKECMBX23.ad.infosys.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <59F9D6FCA56827488D2004B1DB7EA177@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, Bharat Joshi <bharat_joshi@infosys.com>, "ietf@ietf.org List" <ietf@ietf.org>, "draft-ietf-dhc-relay-id-suboption.all@tools.ietf.org" <draft-ietf-dhc-relay-id-suboption.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-dhc-relay-id-suboption-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Dec 2012 14:27:25 -0000

On Dec 21, 2012, at 7:48 AM, RAMAKRISHNADTV <RAMAKRISHNADTV@infosys.com> wr=
ote:
> As Ted mentioned, our draft only proposes a new sub-option for relay-agen=
t=20
> option which was originally created as part of RFC3046. So, the security=
=20
> considerations for RFC3046 apply to our draft as well. RFC3046 deployment=
s may
> use RFC4030 as explained above. So, we indicated in our draft to refer to=
=20
> both RFC3046 and RFC4030. But there are no specific security issues in th=
e=20
> new relay-id sub-option itself to make RFC4030 a MUST.

To put it a bit differently, changing the security considerations for RFC30=
46 is out of scope for this document.   It could certainly be argued that t=
he security considerations for RFC3046 are too weak, but if that is an argu=
ment that someone wants to make, the argument should be made in the context=
 of updating RFC3046, not in the context of adding a new DHCP relay option.


From ben@nostrum.com  Fri Dec 21 07:40:24 2012
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C6E021F85D7; Fri, 21 Dec 2012 07:40:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.474
X-Spam-Level: 
X-Spam-Status: No, score=-102.474 tagged_above=-999 required=5 tests=[AWL=0.126, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
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 yNp20WY0A2vh; Fri, 21 Dec 2012 07:40:23 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id AD78321F8ADA; Fri, 21 Dec 2012 07:40:17 -0800 (PST)
Received: from [10.0.1.14] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qBLFeGCi096183 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 21 Dec 2012 09:40:16 -0600 (CST) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <F2B120E98374B2448745C1117BDA1854238F281F@BLRKECMBX23.ad.infosys.com>
Date: Fri, 21 Dec 2012 09:40:18 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <8C2DB2B9-B9DD-444B-B760-DED177907291@nostrum.com>
References: <BE996F07-CFB7-47F5-8B17-FA651C294FA3@nostrum.com> <F2B120E98374B2448745C1117BDA1854238F281F@BLRKECMBX23.ad.infosys.com>
To: RAMAKRISHNADTV <RAMAKRISHNADTV@infosys.com>
X-Mailer: Apple Mail (2.1499)
Received-SPF: pass (nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, Bharat Joshi <bharat_joshi@infosys.com>, "ietf@ietf.org List" <ietf@ietf.org>, "draft-ietf-dhc-relay-id-suboption.all@tools.ietf.org" <draft-ietf-dhc-relay-id-suboption.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-dhc-relay-id-suboption-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Dec 2012 15:40:24 -0000

Thanks for the timely response, and the background for the security =
language.=20

This brings up one question, however. See inline:=20

Thanks!

Ben.

On Dec 21, 2012, at 6:48 AM, RAMAKRISHNADTV <RAMAKRISHNADTV@infosys.com> =
wrote:

> Hi Ben,
>=20
> Thank you for your review comments.
> Please find my responses inline below.
>=20
> Regards,
> Ramakrishna DTV.
>=20
>> -----Original Message-----
>> From: Ben Campbell [mailto:ben@nostrum.com]
>> Sent: Thursday, December 20, 2012 2:45 AM
>> To: draft-ietf-dhc-relay-id-suboption.all@tools.ietf.org
>> Cc: gen-art@ietf.org Review Team; ietf@ietf.org List
>> Subject: Gen-ART LC Review of draft-ietf-dhc-relay-id-suboption-11
>>=20
>> I am the assigned Gen-ART reviewer for this draft. For background on
>> Gen-ART, please see the FAQ at
>>=20
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>=20
>> Please resolve these comments along with any other Last Call comments
>> you may receive.
>>=20
>> Document: draft-ietf-dhc-relay-id-suboption-11
>> Reviewer: Ben Campbell
>> Review Date: 2012-12-19
>> IETF LC End Date: 2013-01-07
>>=20
>> Summary: This draft is basically ready for publication as a proposed
>> standard. However, there is one comment from a prior review that I am
>> not sure whether is resolved.
>>=20
>> Major issues:
>>=20
>> None
>>=20
>> Minor issues:
>>=20
>> -- In Sean Turner's 2009 review of version 07 of the document [
>> http://www.ietf.org/mail-archive/web/gen-art/current/msg04614.html ], =
he
>> made the following comment:
>>=20
>>> In the security considerations it says look to RFC 3046 and
>>> RFC 4030 for security considerations and then says SHOULD use the
>> relay
>>> agent authentication option from RFC 4030.  RFC 3046 is targeted at
>>> network infrastructures that are "trusted and secure" and RFC 4030
>>> allows the relay agent to be part of this trusted and secure =
network.
>>> If an implementation doesn't use the relay agent authentication
>> option,
>>> then the relay agent can't be part of the "trusted and secure"
>> network.
>=20
> RFC3046 created the relay agent information option.
> Relay agent information option exists only in the messages between
> relay agents and DHCP servers. RFC3046 is targeted at network =
infrastructures
> that are "trusted and secure" as far as the paths among relay agents =
and DHCP
> servers is concerned. In many deployments, relay agents and DHCP =
servers
> are under a single administrative control. By careful design and =
engineering
> of the network, it is possible to ensure that the network =
infrastructure
> comprising relay agents and DHCP server is trusted and secure. To =
achieve that,
> RFC4030 may be used but is not a MUST. If not, RFC4030 would already =
be a MUST
> for RFC3046 deployment. But that is not currently the case.

Is the SHOULD use 4030 language a new normative requirement, or is it =
simply describing existing requirements from 3046 or elsewhere?  If it's =
a new normative requirement, then I am fine with your answer and =
withdraw the concern. If not, then it would be better to use descriptive =
rather than normative language in this draft.


>=20
>>> This makes me think that the relay agent authentication option from
>>> RFC 4030 ought to be a MUST not a SHOULD?
>>=20
>> I can't tell from the resulting conversation if that comment is
>> addressed in the current text. Additional text has been added, but =
the
>> SHOULD remains. I'm willing to accept it has been addressed if the
>> author's say so--I only mention it to make sure it didn't fall =
through a
>> crack.
>>=20
>=20
> We have indeed discussed about this comment and addressed it.
>=20
> The following was a related comment from DHC WG Chair (Ted Lemon)
> (http://www.ietf.org/mail-archive/web/gen-art/current/msg04615.html):
>=20
> 	"This document makes no changes to practice that require more or =
less security
> 	than is provided by existing relay agent options in RFC3046. =
Thus, the
> 	security considerations in RFC3046 should be adequate."
>=20
> As Ted mentioned, our draft only proposes a new sub-option for =
relay-agent
> option which was originally created as part of RFC3046. So, the =
security
> considerations for RFC3046 apply to our draft as well. RFC3046 =
deployments may
> use RFC4030 as explained above. So, we indicated in our draft to refer =
to
> both RFC3046 and RFC4030. But there are no specific security issues in =
the
> new relay-id sub-option itself to make RFC4030 a MUST.
>=20
>=20
>> Nits/editorial comments:
>>=20
>> -- section 5, last paragraph:
>>=20
>> I suggest removing the scare quotes around "stability". If there are
>> concerns about whether such stability is real, it would be better to =
say
>> that directly.
>>=20
>=20
> There is no need for these scare quotes. We will remove them.
>=20
>> -- informative references:
>>=20
>> draft-ietf-dhc-dhcpv4-bulk-leasequery-06 is now 07
>=20
> We will update this.
>=20
>>=20
>=20
> **************** CAUTION - Disclaimer *****************
> This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended =
solely
> for the use of the addressee(s). If you are not the intended =
recipient, please
> notify the sender by e-mail and delete the original message. Further, =
you are not
> to copy, disclose, or distribute this e-mail or its contents to any =
other person and
> any such actions are unlawful. This e-mail may contain viruses. =
Infosys has taken
> every reasonable precaution to minimize this risk, but is not liable =
for any damage
> you may sustain as a result of any virus in this e-mail. You should =
carry out your
> own virus checks before opening the e-mail or attachment. Infosys =
reserves the
> right to monitor and review the content of all messages sent to or =
from this e-mail
> address. Messages sent to or from this e-mail address may be stored on =
the
> Infosys e-mail system.
> ***INFOSYS******** End of Disclaimer ********INFOSYS***


From ben@nostrum.com  Fri Dec 21 07:45:15 2012
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98B1F21F8CEC; Fri, 21 Dec 2012 07:45:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.484
X-Spam-Level: 
X-Spam-Status: No, score=-102.484 tagged_above=-999 required=5 tests=[AWL=0.116, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
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 wfaa02TCtIAY; Fri, 21 Dec 2012 07:45:15 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id ADB0621F8C31; Fri, 21 Dec 2012 07:45:14 -0800 (PST)
Received: from [10.0.1.14] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qBLFjDUE096742 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 21 Dec 2012 09:45:13 -0600 (CST) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307474418FF@mbx-01.win.nominum.com>
Date: Fri, 21 Dec 2012 09:45:15 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <E1A0312B-2E9A-4FD6-AAAA-8AE03AE4B965@nostrum.com>
References: <BE996F07-CFB7-47F5-8B17-FA651C294FA3@nostrum.com> <F2B120E98374B2448745C1117BDA1854238F281F@BLRKECMBX23.ad.infosys.com> <8D23D4052ABE7A4490E77B1A012B6307474418FF@mbx-01.win.nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1499)
Received-SPF: pass (nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, Bharat Joshi <bharat_joshi@infosys.com>, RAMAKRISHNADTV <RAMAKRISHNADTV@infosys.com>, "draft-ietf-dhc-relay-id-suboption.all@tools.ietf.org" <draft-ietf-dhc-relay-id-suboption.all@tools.ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-dhc-relay-id-suboption-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Dec 2012 15:45:15 -0000

On Dec 21, 2012, at 8:27 AM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> On Dec 21, 2012, at 7:48 AM, RAMAKRISHNADTV =
<RAMAKRISHNADTV@infosys.com> wrote:
>> As Ted mentioned, our draft only proposes a new sub-option for =
relay-agent=20
>> option which was originally created as part of RFC3046. So, the =
security=20
>> considerations for RFC3046 apply to our draft as well. RFC3046 =
deployments may
>> use RFC4030 as explained above. So, we indicated in our draft to =
refer to=20
>> both RFC3046 and RFC4030. But there are no specific security issues =
in the=20
>> new relay-id sub-op
>> tion itself to make RFC4030 a MUST.
>=20
> To put it a bit differently, changing the security considerations for =
RFC3046 is out of scope for this document.   It could certainly be =
argued that the security considerations for RFC3046 are too weak, but if =
that is an argument that someone wants to make, the argument should be =
made in the context of updating RFC3046, not in the context of adding a =
new DHCP relay option.
>=20

Thanks Ted, that makes perfect sense.=20

As I responded separately to Ramakrishna, is the SHOULD use 4030 =
language a new requirement specific to this draft? Or is it just =
describing requirements in 3046 or elsewhere?

Thanks!

Ben.=

From Ted.Lemon@nominum.com  Fri Dec 21 08:06:35 2012
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F6E521F8802; Fri, 21 Dec 2012 08:06:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.576
X-Spam-Level: 
X-Spam-Status: No, score=-106.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 RjQfGZwdBglx; Fri, 21 Dec 2012 08:06:34 -0800 (PST)
Received: from exprod7og124.obsmtp.com (exprod7og124.obsmtp.com [64.18.2.26]) by ietfa.amsl.com (Postfix) with ESMTP id 7B49321F86A4; Fri, 21 Dec 2012 08:06:34 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob124.postini.com ([64.18.6.12]) with SMTP ID DSNKUNSJBq9xiSuHISy1FgkVyq8g2p1bv2hs@postini.com; Fri, 21 Dec 2012 08:06:34 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 4C0511B81E8; Fri, 21 Dec 2012 08:06:30 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 43759190052; Fri, 21 Dec 2012 08:06:30 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Fri, 21 Dec 2012 08:06:30 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Ben Campbell <ben@nostrum.com>
Thread-Topic: Gen-ART LC Review of draft-ietf-dhc-relay-id-suboption-11
Thread-Index: AQHN3i33Q3+/pWXDrEC14WiRxtRL+pgjvKCAgAAbrICAABXLgIAABe6A
Date: Fri, 21 Dec 2012 16:06:30 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630747441AF5@mbx-01.win.nominum.com>
References: <BE996F07-CFB7-47F5-8B17-FA651C294FA3@nostrum.com> <F2B120E98374B2448745C1117BDA1854238F281F@BLRKECMBX23.ad.infosys.com> <8D23D4052ABE7A4490E77B1A012B6307474418FF@mbx-01.win.nominum.com> <E1A0312B-2E9A-4FD6-AAAA-8AE03AE4B965@nostrum.com>
In-Reply-To: <E1A0312B-2E9A-4FD6-AAAA-8AE03AE4B965@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <051271295785B447A3D42540E88098E3@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, Bharat Joshi <bharat_joshi@infosys.com>, RAMAKRISHNADTV <RAMAKRISHNADTV@infosys.com>, "draft-ietf-dhc-relay-id-suboption.all@tools.ietf.org" <draft-ietf-dhc-relay-id-suboption.all@tools.ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-dhc-relay-id-suboption-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Dec 2012 16:06:36 -0000

On Dec 21, 2012, at 10:45 AM, Ben Campbell <ben@nostrum.com> wrote:
> As I responded separately to Ramakrishna, is the SHOULD use 4030 language=
 a new requirement specific to this draft? Or is it just describing require=
ments in 3046 or elsewhere?

I suppose the authors should really answer this, but I was curious as well,=
 and went looking.   I think RFC4030 should have updated RFC3046 to add thi=
s as a security consideration, but it did not.   However, e.g. RFC4243, RFC=
5010 and RFC5107 do add a similar requirement to their security considerati=
ons section, so it's probably fair to say that this has been informally ado=
pted as appropriate practice for security considerations sections.  =20

Perhaps we should adopt the practice more formally... :)


From ben@nostrum.com  Fri Dec 21 08:37:16 2012
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07F1221F874E; Fri, 21 Dec 2012 08:37:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.492
X-Spam-Level: 
X-Spam-Status: No, score=-102.492 tagged_above=-999 required=5 tests=[AWL=0.108, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
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 UN6QhA2-z0og; Fri, 21 Dec 2012 08:37:15 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 3BE4B21F872C; Fri, 21 Dec 2012 08:37:15 -0800 (PST)
Received: from [10.0.1.14] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qBLGb8tK002567 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 21 Dec 2012 10:37:09 -0600 (CST) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630747441AF5@mbx-01.win.nominum.com>
Date: Fri, 21 Dec 2012 10:37:10 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <1D859D9D-D1F5-4AD4-855E-9D193A7084B2@nostrum.com>
References: <BE996F07-CFB7-47F5-8B17-FA651C294FA3@nostrum.com> <F2B120E98374B2448745C1117BDA1854238F281F@BLRKECMBX23.ad.infosys.com> <8D23D4052ABE7A4490E77B1A012B6307474418FF@mbx-01.win.nominum.com> <E1A0312B-2E9A-4FD6-AAAA-8AE03AE4B965@nostrum.com> <8D23D4052ABE7A4490E77B1A012B630747441AF5@mbx-01.win.nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1499)
Received-SPF: pass (nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, Bharat Joshi <bharat_joshi@infosys.com>, RAMAKRISHNADTV <RAMAKRISHNADTV@infosys.com>, "draft-ietf-dhc-relay-id-suboption.all@tools.ietf.org" <draft-ietf-dhc-relay-id-suboption.all@tools.ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-dhc-relay-id-suboption-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Dec 2012 16:37:16 -0000

On Dec 21, 2012, at 10:06 AM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> On Dec 21, 2012, at 10:45 AM, Ben Campbell <ben@nostrum.com> wrote:
>> As I responded separately to Ramakrishna, is the SHOULD use 4030 =
language a new requirement specific to this draft? Or is it just =
describing requirements in 3046 or elsewhere?
>=20
> I suppose the authors should really answer this, but I was curious as =
well, and went looking.   I think RFC4030 should have updated RFC3046 to =
add this as a security consideration, but it did not.   However, e.g. =
RFC4243, RFC5010 and RFC5107 do add a similar requirement to their =
security considerations section, so it's probably fair to say that this =
has been informally adopted as appropriate practice for security =
considerations sections.  =20
>=20
> Perhaps we should adopt the practice more formally... :)

Pending the authors' comments, it sounds like it's good as is. (Assuming =
that "adopt[ing] the practice more formally" isn't _this_ draft's =
problem :-)  )

>=20


From bharat_joshi@infosys.com  Sun Dec 23 19:34:56 2012
Return-Path: <bharat_joshi@infosys.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46F4021F8BC4; Sun, 23 Dec 2012 19:34:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 RhUvuo3-H08E; Sun, 23 Dec 2012 19:34:55 -0800 (PST)
Received: from kecgate06.infosys.com (kecgate06.infosys.com [122.98.14.33]) by ietfa.amsl.com (Postfix) with ESMTP id E625E21F8BB3; Sun, 23 Dec 2012 19:34:53 -0800 (PST)
X-TM-IMSS-Message-ID: <0426e0510027d947@infosys.com>
Received: from blrkechub04.ad.infosys.com ([10.66.236.44]) by infosys.com ([122.98.14.33]) with ESMTP (TREND IMSS SMTP Service 7.1) id 0426e0510027d947 ; Mon, 24 Dec 2012 09:08:06 +0530
Received: from BLRKECHUB10.ad.infosys.com (10.66.236.120) by blrkechub04.ad.infosys.com (10.66.236.44) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 24 Dec 2012 09:04:24 +0530
Received: from BLRKECMBX13.ad.infosys.com ([fe80::c43d:ba67:abc0:11c3]) by blrkechub10.ad.infosys.com ([::1]) with mapi id 14.02.0318.004; Mon, 24 Dec 2012 09:04:23 +0530
From: Bharat Joshi <bharat_joshi@infosys.com>
To: Ben Campbell <ben@nostrum.com>, RAMAKRISHNADTV <RAMAKRISHNADTV@infosys.com>
Thread-Topic: Gen-ART LC Review of draft-ietf-dhc-relay-id-suboption-11
Thread-Index: AQHN3i35+JDgXE0aqUaOeE64IeAUXJgi2lGAgAAwFACABEXLYw==
Date: Mon, 24 Dec 2012 03:34:23 +0000
Message-ID: <35347FBF2796F94E936EE76C0E6047ED2B643600@BLRKECMBX13.ad.infosys.com>
References: <BE996F07-CFB7-47F5-8B17-FA651C294FA3@nostrum.com> <F2B120E98374B2448745C1117BDA1854238F281F@BLRKECMBX23.ad.infosys.com>, <8C2DB2B9-B9DD-444B-B760-DED177907291@nostrum.com>
In-Reply-To: <8C2DB2B9-B9DD-444B-B760-DED177907291@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.37.13]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>, "draft-ietf-dhc-relay-id-suboption.all@tools.ietf.org" <draft-ietf-dhc-relay-id-suboption.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-dhc-relay-id-suboption-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Dec 2012 03:34:56 -0000

Hi Ben,

        One reply in line.

        We will bring out another revision after taking care of your sugg=
estions once we have some more review comments.

Regards,
Bharat

> Thanks for the timely response, and the background for the security
> language. 
> 
> This brings up one question, however. See inline: 
> 
> Thanks!
> 
> Ben.
> 
> On Dec 21, 2012, at 6:48 AM, RAMAKRISHNADTV <RAMAKRISHNADTV@infosys.com=
>
> wrote:
> 
> > Hi Ben,
> > 
> > Thank you for your review comments.
> > Please find my responses inline below.
> > 
> > Regards,
> > Ramakrishna DTV.
> > 
> >> -----Original Message-----
> >> From: Ben Campbell [mailto:ben@nostrum.com]
> >> Sent: Thursday, December 20, 2012 2:45 AM
> >> To: draft-ietf-dhc-relay-id-suboption.all@tools.ietf.org
> >> Cc: gen-art@ietf.org Review Team; ietf@ietf.org List
> >> Subject: Gen-ART LC Review of draft-ietf-dhc-relay-id-suboption-11
> >> 
> >> I am the assigned Gen-ART reviewer for this draft. For background on
> >> Gen-ART, please see the FAQ at
> >> 
> >> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >> 
> >> Please resolve these comments along with any other Last Call comment=
s
> >> you may receive.
> >> 
> >> Document: draft-ietf-dhc-relay-id-suboption-11
> >> Reviewer: Ben Campbell
> >> Review Date: 2012-12-19
> >> IETF LC End Date: 2013-01-07
> >> 
> >> Summary: This draft is basically ready for publication as a proposed
> >> standard. However, there is one comment from a prior review that I a=
m
> >> not sure whether is resolved.
> >> 
> >> Major issues:
> >> 
> >> None
> >> 
> >> Minor issues:
> >> 
> >> -- In Sean Turner's 2009 review of version 07 of the document [
> >> http://www.ietf.org/mail-archive/web/gen-art/current/msg04614.html ]=
,
> he
> >> made the following comment:
> >> 
> >>> In the security considerations it says look to RFC 3046 and
> >>> RFC 4030 for security considerations and then says SHOULD use the
> >> relay
> >>> agent authentication option from RFC 4030.  RFC 3046 is targeted at
> >>> network infrastructures that are "trusted and secure" and RFC 4030
> >>> allows the relay agent to be part of this trusted and secure
> network.
> >>> If an implementation doesn't use the relay agent authentication
> >> option,
> >>> then the relay agent can't be part of the "trusted and secure"
> >> network.
> > 
> > RFC3046 created the relay agent information option.
> > Relay agent information option exists only in the messages between
> > relay agents and DHCP servers. RFC3046 is targeted at network
> infrastructures
> > that are "trusted and secure" as far as the paths among relay agents
> and DHCP
> > servers is concerned. In many deployments, relay agents and DHCP
> servers
> > are under a single administrative control. By careful design and
> engineering
> > of the network, it is possible to ensure that the network
> infrastructure
> > comprising relay agents and DHCP server is trusted and secure. To
> achieve that,
> > RFC4030 may be used but is not a MUST. If not, RFC4030 would already
> be a MUST
> > for RFC3046 deployment. But that is not currently the case.
> 
> Is the SHOULD use 4030 language a new normative requirement, or is it
> simply describing existing requirements from 3046 or elsewhere?  If it'=
s
> a new normative requirement, then I am fine with your answer and
> withdraw the concern. If not, then it would be better to use descriptiv=
e
> rather than normative language in this draft.
> 

Yes.

Also as mentioned by Ted, this draft is using a language similar to some =
existing RFCs.
**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended sol=
ely 
for the use of the addressee(s). If you are not the intended recipient, p=
lease 
notify the sender by e-mail and delete the original message. Further, you=
 are not 
to copy, disclose, or distribute this e-mail or its contents to any other=
 person and 
any such actions are unlawful. This e-mail may contain viruses. Infosys h=
as taken 
every reasonable precaution to minimize this risk, but is not liable for =
any damage 
you may sustain as a result of any virus in this e-mail. You should carry=
 out your 
own virus checks before opening the e-mail or attachment. Infosys reserve=
s the 
right to monitor and review the content of all messages sent to or from t=
his e-mail 
address. Messages sent to or from this e-mail address may be stored on th=
e 
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***

From kotikalapudi.sriram@nist.gov  Tue Dec 25 21:17:39 2012
Return-Path: <kotikalapudi.sriram@nist.gov>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA00F21F8C56 for <gen-art@ietfa.amsl.com>; Tue, 25 Dec 2012 21:17:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.219
X-Spam-Level: 
X-Spam-Status: No, score=-6.219 tagged_above=-999 required=5 tests=[AWL=-0.220, BAYES_00=-2.599, J_CHICKENPOX_43=0.6, 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 ijBsDBo5rAIy for <gen-art@ietfa.amsl.com>; Tue, 25 Dec 2012 21:17:39 -0800 (PST)
Received: from wsget2.nist.gov (wsget2.nist.gov [129.6.13.151]) by ietfa.amsl.com (Postfix) with ESMTP id C2D3F21F8C55 for <gen-art@ietf.org>; Tue, 25 Dec 2012 21:17:38 -0800 (PST)
Received: from WSXGHUB2.xchange.nist.gov (129.6.18.19) by wsget2.nist.gov (129.6.13.151) with Microsoft SMTP Server (TLS) id 14.2.328.9; Wed, 26 Dec 2012 00:17:21 -0500
Received: from MBCLUSTER.xchange.nist.gov ([fe80::d479:3188:aec0:cb66]) by WSXGHUB2.xchange.nist.gov ([129.6.18.19]) with mapi; Wed, 26 Dec 2012 00:17:36 -0500
From: "Sriram, Kotikalapudi" <kotikalapudi.sriram@nist.gov>
To: Elwyn Davies <elwynd@dial.pipex.com>, Terry Manderson <terry.manderson@icann.org>
Date: Wed, 26 Dec 2012 00:17:36 -0500
Thread-Topic: Gen-art LC/Telechat review of  draft-ietf-sidr-usecases-05.txt
Thread-Index: Ac3fc8x1YYe+e8wQQ1Wn35I8JNvHogDsy39x
Message-ID: <D7A0423E5E193F40BE6E94126930C4930BB91F89E7@MBCLUSTER.xchange.nist.gov>
References: <CCF9F24F.2E422%terry.manderson@icann.org>, <1356091602.11916.15388.camel@mightyatom>
In-Reply-To: <1356091602.11916.15388.camel@mightyatom>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 25 Dec 2012 23:59:01 -0800
Cc: "draft-ietf-sidr-usecases.all@tools.ietf.org" <draft-ietf-sidr-usecases.all@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-art LC/Telechat review of draft-ietf-sidr-usecases-05.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Dec 2012 05:17:39 -0000

Hi Elwyn,

I have carefully read all the comments in this thread.
Thank you for your review and comments -- very helpful.
I have a good understanding of all the changes I need to make.
I will spin a new version by Wednesday (12/26) evening or Thursday a.m. 
Will run it by Terry and Russ first and then post it here in this thread as an attachment.

Happy Holidays.

Sriram
________________________________________
From: Elwyn Davies [elwynd@dial.pipex.com]
Sent: Friday, December 21, 2012 7:06 AM
To: Terry Manderson
Cc: General Area Review Team; draft-ietf-sidr-usecases.all@tools.ietf.org
Subject: Re: Gen-art LC/Telechat review of  draft-ietf-sidr-usecases-05.txt

Hi, Terry.

That's all fine by me.

Have a great Christmas!

Elwyn

On Thu, 2012-12-20 at 17:02 -0800, Terry Manderson wrote:
> On 20/12/12 11:23 AM, "Elwyn Davies" <elwynd@dial.pipex.com> wrote:
>
> > Hi, Terry.
> >
> > Thanks for the swift reply.
> >
> > Looks like all is well with most of he comments.
> >
> > I guess the main consclusion would be that you maybe need to put in a
> > bit more explanation of the context to which make-before-break applies
> > as per your explanation to me below.
>
> I hear you, I will come back to you after Xmas with some expanded draft text
> for s2.1.
>
> >
>
> >>> It is possible that I don't understand the problem, but this appears to
> >>> be trying to prove a negative by the existence of something.  What RPKI
> >>> object would have to exist to make the route suspicious?
> >>
> >> Essentially a valid RPKI ROA object would need to exist that proves a route
> >> is suspicious. Because the RPKI+ROA is a "bolt on after the fact" security
> >> effort, you can do no more. Simply routing exists now, the RPKI would be
> >> deployed in the future. So any route that is seen must be considered
> >> intended unless proven otherwise.
> > I see now.. perhaps you could add something like:
> > ... valid RPKI object that explicitly invalidates the route (see Section
> > 7 for examples).
>
> That works for me.
>
> >>
> >>>
> >>> s6.2: Can the make-before-break principle be applied to the resource
> >>> certificate for Org B?  Presumably this would mean overlapping existence
> >>> of resource certs for Org A and Org B so that the ROA add can occur
> >>> before the revoke.  Is this a problem?
> >>>
> >>
> >> The preference, I believe (and my co-authors can correct me) is that two
> >> different resource certificates (unless one in subordinate to the other)
> >> should never exist.
> >>
> >> This problem is an open issue in SIDR related to the grandfathering topic.
> >> So for now the usecase should be that overlap cannot occur.
> > Do you think this needs explicit  mention?
>
> No. I feel it is better to remain silent in the usecases. A requirements
> document (should one ever be set as a charter deliverable) would define that
> behaviour, which would then be reinforced by the RPKI architecture.
>
> I personally feel it is better to bis this document should change be needed.
>
>
> >> work for you?
> >
> > Maybe 'through two or more' but basically 'yes, thanks'.
>
> Works for me.
>
> >>
>
> >>> describe the add before the revoke in each case?
> >>
> >> ahh.. I think we have a disconnect. make before break is considered in the
> >> routing sense that a route is considered o.k. (UNKNOWN) unless proven
> >> otherwise, this means you can remove ALL RPKI object for a route, and it
> >> will still exist happily until a new and conflicting RPKI ROA is created..
> >> And we are working to that. Not necessarily making a new valid object before
> >> breaking the old valid object. That would then imply ownership of a prefix
> >> can then be in two places at the same time. And like the transfer of title
> >> for a house, overlap tends to be considered a bad thing. (co-authors, chime
> >> in here!)
> >>
> > See initial comment.. this is a useful explanation and some words to
> > this effect would avoid others with equally bad understanding of the
> > RPKI scenario making the same mistake.
> >
>
> Ack. Will run draft text past co-authors and bring back post xmas.
>
> Terry


From peter@akayla.com  Wed Dec 26 03:04:37 2012
Return-Path: <peter@akayla.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97C6B21F8AE7 for <gen-art@ietfa.amsl.com>; Wed, 26 Dec 2012 03:04:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 BfcHqm0COXzL for <gen-art@ietfa.amsl.com>; Wed, 26 Dec 2012 03:04:37 -0800 (PST)
Received: from smtpauth23.prod.mesa1.secureserver.net (smtpauth23.prod.mesa1.secureserver.net [64.202.165.47]) by ietfa.amsl.com (Postfix) with SMTP id C349621F89E9 for <gen-art@ietf.org>; Wed, 26 Dec 2012 03:04:36 -0800 (PST)
Received: (qmail 28466 invoked from network); 26 Dec 2012 11:04:36 -0000
Received: from unknown (173.8.184.78) by smtpauth23.prod.mesa1.secureserver.net (64.202.165.47) with ESMTP; 26 Dec 2012 11:04:34 -0000
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-6man-udpchecksums.all@tools.ietf.org>
Date: Wed, 26 Dec 2012 03:05:01 -0800
Message-ID: <000701cde358$da44c6a0$8ece53e0$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac3jUy70UdbyWm97QlKDE0mhNpITcQ==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART review of draft-ietf-6man-udpchecksums-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Dec 2012 11:04:37 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>

Please wait for direction from your document shepherd or AD before posting a
new version of the draft.

Document: draft-ietf-6man-udpchecksums-06
Reviewer: Peter Yee
Review Date: Dec-25-2012
IETF LC End Date: Dec-25-2012
IESG Telechat date: Unknown

Summary: This draft is basically ready for publication, but has nits that
should be fixed before publication. [Ready with nits.]

This document provides an update to 2460 to allow the use of zero checksum
UDP packets over IPv6 in certain
cases involving protocols tunneled inside of UDP packets.

Nits:

General: a comma after "i.e." is preferred in American English.

General: it is not necessary to hyphenate "misdelivered" or "misdelivery".

General: put quotes around "Applicability Statement for the use of IPv6 UDP
Datagrams with Zero  Checksums"

Abstract, first sentence: "when" -> "where"

Abstract, second sentence: "protocol" -> "protocols"

Section 1, second paragraph, first sentence: delete the comma after
"packet".

Section 1, fourth paragraph, first sentence: move the comma in "AMT," to
after the reference.

Section 1, fourth paragraph, last sentence: insert "the" after "applicable
in".

Section 3, second sentence: delete the first occurrence of "where".
Consider revising the sentence for clarity.

Section 4, second sentence: "Section" -> "Sections"

Section 4.1, it would be nice, but not necessary to have an enumeration of
the corruption modes.  

Section 4.1, third bullet item, first sentence: a verb is missing here
making the sentence difficult to parse.

Section 4.1, third bullet item, first sentence: "packets" -> "packet"

Section 4.1, third bullet item, third sub-bullet: put commas around "for
example".

Section 4.2, first bullet item, last sentence: this sentence is hard to
understand; consider revising.  (See next comment)

Section 4.2, first bullet item, last sentence: "an" -> "a" and "are" ->
"is"; also not general comment about "misdelivered".

Section 4.2, third bullet item, third sentence: "effect" -> "affect"

Section 4.2, first paragraph after bullet items, first sentence: delete
"this".

Section 4.2, first paragraph after bullet items, third sentence:
"mis-delievery" -> "misdelivery".

Section 4.2, first paragraph after bullet items, third sentence: delete
"that".

Section 4.3, first sentence: "middlebox devices" -> "middleboxes" unless
this a specific usage from I-D.ietf-6man-udpzero.

Section 4.3, second sentence: "needs" -> "need"

Section 5, first paragraph, second sentence: insert "in" after "node
requirements".

Section 5, first paragraph of replacement text, second sentence: delete
"usage for", replace "some" with "certain", and replace second "protocols"
with "those".

Section 5, last paragraph: delete first instance of "the".

Section 6, first bullet item, first sentence: "corruptions" -> "corruption"

Section 6, second bullet item, last sentence: change "This" to "UDP-Lite".

Section 8, first sentence: delete redundant "required".


From brian.e.carpenter@gmail.com  Wed Dec 26 03:50:22 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4890B21F8C9C for <gen-art@ietfa.amsl.com>; Wed, 26 Dec 2012 03:50:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.603
X-Spam-Level: 
X-Spam-Status: No, score=-101.603 tagged_above=-999 required=5 tests=[AWL=0.088, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 nKeSHERkDB8U for <gen-art@ietfa.amsl.com>; Wed, 26 Dec 2012 03:50:17 -0800 (PST)
Received: from mail-wi0-f179.google.com (mail-wi0-f179.google.com [209.85.212.179]) by ietfa.amsl.com (Postfix) with ESMTP id 5DF2821F8C9B for <gen-art@ietf.org>; Wed, 26 Dec 2012 03:50:17 -0800 (PST)
Received: by mail-wi0-f179.google.com with SMTP id o1so4765623wic.6 for <gen-art@ietf.org>; Wed, 26 Dec 2012 03:50:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:subject:content-type; bh=Nr++PqyWBLzUC7WOx/rMpZ6pnIfTV7ViwkcybjUNHEQ=; b=oksyyBEQT3WK/6H+idIhfkljj0gqMZo7+PA50NB87x1nKoGb7sEUm4zXfdcn1chETF zfcOCFs7RePjY0Pv2YyTZFJn0UXryR1nZ/RYA37UoP6det4jIki/1e3viDvFCe2Sytdm EBu10ydQXXTfb3nK1K5Ii4Hw2BHHZKSz2J4DqCliMmmBcUwLreNePvKgsMiU9D8jeQ5q 2ARufS3DbwvfjWj1gthT7+Y4oyxvx2Feb3EQEIf1l34HynC4yD4Ye0X8FR8QXbjUVgWs AVUS/1k9jrT01MoBpf6ZY3iQJjd2YToQiDeli/L6aaYXrb+OtMaOU8YtBGSsGFNk1TsE 3W0g==
X-Received: by 10.180.85.165 with SMTP id i5mr42030199wiz.11.1356522616320; Wed, 26 Dec 2012 03:50:16 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-219-117.as13285.net. [2.102.219.117]) by mx.google.com with ESMTPS id hg17sm52233375wib.1.2012.12.26.03.50.14 (version=SSLv3 cipher=OTHER); Wed, 26 Dec 2012 03:50:15 -0800 (PST)
Message-ID: <50DAE47F.4030704@gmail.com>
Date: Wed, 26 Dec 2012 11:50:23 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: draft-ietf-sidr-rpki-rtr-protocol-mib.all@tools.ietf.org,  General Area Review Team <gen-art@ietf.org>
Content-Type: multipart/mixed; boundary="------------070500010502040504050707"
Subject: [Gen-art] Gen-ART LC review of draft-ietf-sidr-rpki-rtr-protocol-mib-04.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Dec 2012 11:50:22 -0000

This is a multi-part message in MIME format.
--------------070500010502040504050707
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Please see attached review.

     Brian




--------------070500010502040504050707
Content-Type: text/plain;
 name="draft-ietf-sidr-rpki-rtr-protocol-mib-04-carpenter.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="draft-ietf-sidr-rpki-rtr-protocol-mib-04-carpenter.txt"

SSBhbSB0aGUgYXNzaWduZWQgR2VuLUFSVCByZXZpZXdlciBmb3IgdGhpcyBkcmFmdC4gRm9y
IGJhY2tncm91bmQgb24NCkdlbi1BUlQsIHBsZWFzZSBzZWUgdGhlIEZBUSBhdA0KPGh0dHA6
Ly93aWtpLnRvb2xzLmlldGYub3JnL2FyZWEvZ2VuL3RyYWMvd2lraS9HZW5BcnRmYXE+Lg0K
DQpQbGVhc2UgcmVzb2x2ZSB0aGVzZSBjb21tZW50cyBhbG9uZyB3aXRoIGFueSBvdGhlciBM
YXN0IENhbGwgY29tbWVudHMNCnlvdSBtYXkgcmVjZWl2ZS4NCg0KRG9jdW1lbnQ6IGRyYWZ0
LWlldGYtc2lkci1ycGtpLXJ0ci1wcm90b2NvbC1taWItMDQudHh0DQpSZXZpZXdlcjogQnJp
YW4gQ2FycGVudGVyDQpSZXZpZXcgRGF0ZTogMjAxMi0xMi0yNg0KSUVURiBMQyBFbmQgRGF0
ZTogMjAxMy0wMS0xNA0KSUVTRyBUZWxlY2hhdCBkYXRlOiANCg0KU3VtbWFyeTogIEluIGdv
b2Qgc2hhcGUsIHR3byBvcGVuIGlzc3Vlcw0KLS0tLS0tLS0NCg0KQ29tbWVudDogIA0KLS0t
LS0tLS0NCg0KSSBzZWUgYSBub3RlIGluIHRoZSB0cmFja2VyIHRoYXQgdGhlIE1JQiBEb2N0
b3IgcmV2aWV3ICJzdGlsbCBuZWVkcyB0byBoYXBwZW4iLg0KU2luY2UgSSdtIG5vdCBjb21w
ZXRlbnQgYXMgYSBNSUIgZG9jdG9yLCBJIGhvcGUgdGhpcyBoYXMgYmVlbiBkb25lLg0KDQpN
YWpvciBpc3N1ZToNCi0tLS0tLS0tLS0tLQ0KDQpJbiBkcmFmdC1pZXRmLXNpZHItcnBraS1y
dHItMjYgdGhlIGxpc3Qgb2YgY2FjaGVzIGlzIHN0YXRlZCB0byBpbmNsdWRlDQoNCiAgTmFt
ZTogIFRoZSBJUCBBZGRyZXNzIG9yIGZ1bGx5IHF1YWxpZmllZCBkb21haW4gbmFtZSBvZiB0
aGUgY2FjaGUuDQoNCkkgZmluZCBubyB3YXkgdG8gcmVwcmVzZW50IHRoZSBGUUROIG9wdGlv
biBpbiB0aGUgTUlCIG1vZHVsZS4gV2Ugc3RhdGUNCmV4cGxpY2l0bHkgaW4gdGhlIDZyZW51
bSBkb2N1bWVudHMgdGhhdCBpdCBzaG91bGQgYmUgcG9zc2libGUgdG8gY29uZmlndXJlDQpu
ZXR3b3JrIGVsZW1lbnRzIHVzaW5nIG5hbWVzIGluIHByZWZlcmVuY2UgdG8gYWRkcmVzc2Vz
LCBzbyBJIHRoaW5rIHRoaXMgaXMNCmEgcHJvYmxlbS4gT2YgY291cnNlLCBhdCBydW4gdGlt
ZSwgdGhlIEZRRE4gd2lsbCBoYXZlIGJlZW4gcmVzb2x2ZWQgaW50bw0KYW4gYWRkcmVzcywg
YnV0IHdoeSBpc24ndCB0aGVyZSBhbHNvIGFuIEZRRE4gb2JqZWN0IGluIHRoZSBNSUIgbW9k
dWxlPw0KSXQgc2VlbSBsaWtlIHRoZXJlIHNob3VsZCBiZSBycGtpUnRyQ2FjaGVTZXJ2ZXJG
UUROLg0KDQpNaW5vciBpc3N1ZToNCi0tLS0tLS0tLS0tLQ0KDQpJbiBkcmFmdC1pZXRmLXNp
ZHItcnBraS1ydHItMjYgdGhlIHByZWZlcmVuY2UgaXMgZGVmaW5lZCBhcw0KDQogUHJlZmVy
ZW5jZTogIEFuIHVuc2lnbmVkIGludGVnZXIgZGVub3RpbmcgdGhlIHJvdXRlcidzIHByZWZl
cmVuY2UgdG8NCiAgICAgIGNvbm5lY3QgdG8gdGhhdCBjYWNoZSwgdGhlIGxvd2VyIHRoZSB2
YWx1ZSB0aGUgbW9yZSBwcmVmZXJyZWQuDQoNClRoYXQgZG9lc24ndCBzcGVjaWZ5IGEgcmFu
Z2UuIFRoZSBNSUIgc3BlY2lmaWVzIHRoZSByYW5nZSBhcyAwLi4yNTU6DQoNCiAgIHJwa2lS
dHJDYWNoZVNlcnZlclByZWZlcmVuY2UgT0JKRUNULVRZUEUNCiAgICAgICBTWU5UQVggICAg
ICAgVW5zaWduZWQzMiAoMC4uMjU1KQ0KDQpJcyB0aGlzIGFuIG92ZXJzaWdodCBpbiBkcmFm
dC1pZXRmLXNpZHItcnBraS1ydHI/IElmIG5vdCwgaXQgc2VlbXMNCm5lY2Vzc2FyeSB0byBz
dGF0ZSB3aGF0IHNob3VsZCBiZSBpbiB0aGUgTUlCIG9iamVjdCBpZiBwcmVmZXJlbmNlPjI1
NS4NCg0KTml0Og0KLS0tLQ0KDQoiVHdvIE5vdGlmaWNhdGlvbiBoYXZlIGJlZW4gZGVmaW5l
ZC4uLiINCnMvTm90aWZpY2F0aW9uL05vdGlmaWNhdGlvbnMvDQo=
--------------070500010502040504050707--

From brian.e.carpenter@gmail.com  Thu Dec 27 03:50:03 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8452321F8855 for <gen-art@ietfa.amsl.com>; Thu, 27 Dec 2012 03:50:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.219
X-Spam-Level: 
X-Spam-Status: No, score=-100.219 tagged_above=-999 required=5 tests=[AWL=-1.298, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_ILLEGAL_IP=1.908, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
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 BKy0iQBkb9qI for <gen-art@ietfa.amsl.com>; Thu, 27 Dec 2012 03:50:02 -0800 (PST)
Received: from mail-wg0-x229.google.com (wg-in-x0229.1e100.net [IPv6:2a00:1450:400c:c00::229]) by ietfa.amsl.com (Postfix) with ESMTP id 6CFE721F8610 for <gen-art@ietf.org>; Thu, 27 Dec 2012 03:50:02 -0800 (PST)
Received: by mail-wg0-f41.google.com with SMTP id ds1so3712251wgb.2 for <gen-art@ietf.org>; Thu, 27 Dec 2012 03:50:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Eta5awe4JDXSD4CVdzOa2dfOwAkzuKXZPDqMDI91DVQ=; b=QAi9PC0TItuASIc+RSe+g6gmPp+rOyo+dAGhQft84xdAC4OL4SSBAOA4WhCGAmV+hD JVsUphRPmBFQhFpvc1xeinkSZJalVdvUdye41NyH5kOdI6nbF3RuVOwDyl66OQCBqYRw gkX7z0Np4GCD3s8sn5/sWLVdSVwCNloQnc9IMdMOoDXCah81eqaRFCBjbCnQMOR10FUI taSHMZTDaFoxV6MD/yjpkW0BkhBAxngKTHHndXvDwbhJ5NVTHoWEcUogO6yuj0U0Txzg SvAU0kfnnohzpuDIegaTqEUHlTj+Wq/XhMl366ETSpQqUWrKrUGVa3cZ6MOXCP1ypBdL pK3g==
X-Received: by 10.180.8.130 with SMTP id r2mr40337099wia.28.1356609001168; Thu, 27 Dec 2012 03:50:01 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-217-137.as13285.net. [2.102.217.137]) by mx.google.com with ESMTPS id hg17sm56972842wib.1.2012.12.27.03.49.59 (version=SSLv3 cipher=OTHER); Thu, 27 Dec 2012 03:49:59 -0800 (PST)
Message-ID: <50DC35F1.5060809@gmail.com>
Date: Thu, 27 Dec 2012 11:50:09 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
References: <50DAE47F.4030704@gmail.com> <50DC18C5.5040600@bwijnen.net>
In-Reply-To: <50DC18C5.5040600@bwijnen.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-sidr-rpki-rtr-protocol-mib.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>, "sidr-chairs >> SIDR Chairs" <sidr-chairs@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-sidr-rpki-rtr-protocol-mib-04.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Dec 2012 11:50:03 -0000

Hi Bert, inline again...

On 27/12/2012 09:45, Bert Wijnen (IETF) wrote:
> Thanks for your review Brian,
> inline
> 
> On 12/26/12 12:50 PM, Brian E Carpenter wrote:
>> Please see attached review.
>>
>>       Brian
>>
>>
>>
>>
>> draft-ietf-sidr-rpki-rtr-protocol-mib-04-carpenter.txt
>>
>>
>> I am the assigned Gen-ART reviewer for this draft. For background on
>> Gen-ART, please see the FAQ at
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>
>> Please resolve these comments along with any other Last Call comments
>> you may receive.
>>
>> Document: draft-ietf-sidr-rpki-rtr-protocol-mib-04.txt
>> Reviewer: Brian Carpenter
>> Review Date: 2012-12-26
>> IETF LC End Date: 2013-01-14
>> IESG Telechat date:
>>
>> Summary:  In good shape, two open issues
>> --------
>>
>> Comment:
>> --------
>>
>> I see a note in the tracker that the MIB Doctor review "still needs to
>> happen".
>> Since I'm not competent as a MIB doctor, I hope this has been done.
>>
>> Major issue:
>> ------------
>>
>> In draft-ietf-sidr-rpki-rtr-26 the list of caches is stated to include
>>
>>    Name:  The IP Address or fully qualified domain name of the cache.
>>
>> I find no way to represent the FQDN option in the MIB module. We state
>> explicitly in the 6renum documents that it should be possible to
>> configure
>> network elements using names in preference to addresses, so I think
>> this is
>> a problem. Of course, at run time, the FQDN will have been resolved into
>> an address, but why isn't there also an FQDN object in the MIB module?
>> It seem like there should be rpkiRtrCacheServerFQDN.
>>
> 
> It would not be an extra object I think.

I wondered about that. Is there a case where the operator might want
to know both the FQDN (as configured) and the IP address (as found
in DNS)? In that case it would need to be an extra object. However,
your proposal is completely logical.

One more comment below.

> It states IP address OR FQDN, so in order to catch that, the current
> 
>    rpkiRtrCacheServerAddressType OBJECT-TYPE
>        SYNTAX       InetAddressType { ipv4(1), ipv6 (2) }
>        MAX-ACCESS   not-accessible
>        STATUS       current
>        DESCRIPTION "The network address type of the connection
>                     to this RPKI cache server.
> 
>                     Only IPv4 and IPv6 are supported."
>        ::= { rpkiRtrCacheServerTableEntry 1 }
> 
>    rpkiRtrCacheServerRemoteAddress OBJECT-TYPE
>        SYNTAX       InetAddress (SIZE(4|16))
>        MAX-ACCESS   not-accessible
>        STATUS       current
>        DESCRIPTION "The remote network address for this connection
>                     to this RPKI cache server.
> 
>                     The format of the address is defined by the
>                     value of the corresponding instance of
>                     rpkiRtrCacheServerAddressType."
>        ::= { rpkiRtrCacheServerTableEntry 2 }
> 
> 
> 
> Could be changed to include dns:
> 
>    rpkiRtrCacheServerAddressType OBJECT-TYPE
>        SYNTAX       InetAddressType { ipv4(1), ipv6 (2), dns(16) }
>        MAX-ACCESS   not-accessible
>        STATUS       current
>        DESCRIPTION "The network address type of the connection
>                     to this RPKI cache server.
> 
>                     Only IPv4 and IPv6 are supported."
>        ::= { rpkiRtrCacheServerTableEntry 1 }
> 
>    rpkiRtrCacheServerRemoteAddress OBJECT-TYPE
>        SYNTAX       InetAddress
>        MAX-ACCESS   not-accessible
>        STATUS       current
>        DESCRIPTION "The remote network address for this connection
>                     to this RPKI cache server.
> 
>                     The format of the address is defined by the
>                     value of the corresponding instance of
>                     rpkiRtrCacheServerAddressType."
>        ::= { rpkiRtrCacheServerTableEntry 2 }
> 
> Note that the Remote address can now have a size of up to 255 octets.
> And we need to specify WHEN the dns name will be resolved.
> I'd have to rely on the RPKI-RTR protocol gurus to tell me when
> that would happen. This is the TC definition for a DNS name in
> this field:
> InetAddressDNS ::= TEXTUAL-CONVENTION
>     DISPLAY-HINT "255a"
>     STATUS       current
>     DESCRIPTION
>         "Represents a DNS domain name.  The name SHOULD be fully
>          qualified whenever possible.
> 
>          The corresponding InetAddressType is dns(16).
> 
>          The DESCRIPTION clause of InetAddress objects that may have
>          InetAddressDNS values MUST fully describe how (and when)
>          these names are to be resolved to IP addresses.
> 
>          The resolution of an InetAddressDNS value may require to
>          query multiple DNS records (e.g., A for IPv4 and AAAA for
>          IPv6).  The order of the resolution process and which DNS
>          record takes precedence depends on the configuration of the
>          resolver.
> 
> So that is what we need to describe. I guess we'd have to
> bring this to teh SIDR WG if we want to add that functionality.
> 
>> Minor issue:
>> ------------
>>
>> In draft-ietf-sidr-rpki-rtr-26 the preference is defined as
>>
>>   Preference:  An unsigned integer denoting the router's preference to
>>        connect to that cache, the lower the value the more preferred.
>>
>> That doesn't specify a range. The MIB specifies the range as 0..255:
>>
>>     rpkiRtrCacheServerPreference OBJECT-TYPE
>>         SYNTAX       Unsigned32 (0..255)
>>
>> Is this an oversight in draft-ietf-sidr-rpki-rtr? If not, it seems
>> necessary to state what should be in the MIB object if preference>255.
>>
> 
> Since the MIB module specifies the range, a value >255 would be return
> a "wrongValue" error. I.e. a value that according to the MIB Syntax
> can never be set.
> 
> Now.. it might be good if the protocol document would specify this too.
> But I do not think it is a fatal flaw.

Agreed. It might be a bit frustrating for the operator though. Maybe
you should add a comment in the MIB module that this might happen.

    Brian
> 
>> Nit:
>> ----
>>
>> "Two Notification have been defined..."
>> s/Notification/Notifications/
> 
> OK, we can easily fix that, otherwise I am sure RFC-Editor will fix it.
> 
> Bert
> 

From Francis.Dupont@fdupont.fr  Thu Dec 27 07:10:06 2012
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BCF721F88C7 for <gen-art@ietfa.amsl.com>; Thu, 27 Dec 2012 07:10:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599]
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 UFaLxuHonrl3 for <gen-art@ietfa.amsl.com>; Thu, 27 Dec 2012 07:10:06 -0800 (PST)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfa.amsl.com (Postfix) with ESMTP id B4F9721F841B for <gen-art@ietf.org>; Thu, 27 Dec 2012 07:10:05 -0800 (PST)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id qBRFA2Ek060734; Thu, 27 Dec 2012 16:10:02 +0100 (CET) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201212271510.qBRFA2Ek060734@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: gen-art@ietf.org
Date: Thu, 27 Dec 2012 16:10:02 +0100
Sender: Francis.Dupont@fdupont.fr
Cc: draft-ietf-sipclf-format.all@tools.ietf.org
Subject: [Gen-art] review of draft-ietf-sipclf-format-09.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Dec 2012 15:10:06 -0000

It seems I forgot to send this before Christmas... I apologize.

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-sipclf-format-09.txt (applies to -11.txt too)
Reviewer: Francis Dupont
Review Date: 20121220
IETF LC End Date: 20121217
IESG Telechat date: 20121220

Summary: Almost Ready

Major issues: None

Minor issues: the encoding of the BEB is inconsistent: one part of the text
specifies 0x00 or 0x01 values, another the hexadecimal of these, i.e.,
the two characters 00 or 01. IMHO they are many good reasons to take the
second but it requires to fix the text, for instance to put the BEB field
in figure 5 section 4.4 page 16 on 2 octets (vs only one) with the mention
"(Hex)".

Nits/editorial comments: (with version 11 page numbers)
 - ToC page 2 and 10 page 28: Acknowledgements -> Acknowledgments

 - 2 page 4: inconsistent use of article in:

   This document uses the term "SIP Server" that is defined to include
   the following SIP entities: user agent server, registrar, redirect
   server, a SIP proxy in the role of user agent server, and a B2BUA in
   the role of a user agent server.

 (IMHO the best is to removed it in the second "the role of a user")

 - 4 page 7: it should be reader friendly to decode the separators
  (i.e., to say 0x2C == ',', etc)

 - 4.2 page 11: i.e. -> i.e.,

 - 4.2 page 12: Encrytped -> Encrypted

 - 4.2 page 13: I have a small concern about the two "(if present)" for
  "To Tag" and "From Tag" because the way it has to be encoded if not
  present is explained after in 4.3. IMHO a reference with a short
  indication ("-") should be wellcome.

 - 4.4 pages 15 and 16: place where BEB is specified.

 - 4.4 page 18: e.g. -> e.g.,

 - 4.4 (1) page 18: first example where the BEB is clearly encoded in
  hexadecimal into 2 octets/characters.

 - Authors' Addresses page 30: (3 times) US -> USA

Regards (and as it is a bit late for Christmas, Happy New Year!)

Francis.Dupont@fdupont.fr

From mahoney@nostrum.com  Thu Dec 27 16:21:44 2012
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 309DF21F8DDD for <gen-art@ietfa.amsl.com>; Thu, 27 Dec 2012 16:21:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
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 3DPKvSX28DPG for <gen-art@ietfa.amsl.com>; Thu, 27 Dec 2012 16:21:43 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 39F0721F8DDC for <gen-art@ietf.org>; Thu, 27 Dec 2012 16:21:43 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-57-99-236.dllstx.fios.verizon.net [173.57.99.236]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qBS0Lgp0074526 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 27 Dec 2012 18:21:42 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <50DCE616.70401@nostrum.com>
Date: Thu, 27 Dec 2012 18:21:42 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 173.57.99.236 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2012-12-27
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Dec 2012 00:21:44 -0000

Hi all,

The following reviewers have assignments:

Reviewer           LC end      Draft

Dan Romascanu     2013-01-07   draft-ietf-sipcore-priority-00

Francis Dupont    2013-01-24   draft-laurie-pki-sunlight-05

Joel Halpern      2013-01-17   draft-higgs-oipf-urn-00


I have made the assignments in the review tool:
http://art.tools.ietf.org/tools/art/genart/

And the assignments are captured in the spreadsheets:
http://wiki.tools.ietf.org/dav/genart/gen-art.html
http://wiki.tools.ietf.org/dav/genart/gen-art-by-reviewer.html


The standard template is included below.

Thanks,

Jean

-------------------------------------------------------------------

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

From jmh@joelhalpern.com  Thu Dec 27 17:06:24 2012
Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9450221F8DE0 for <gen-art@ietfa.amsl.com>; Thu, 27 Dec 2012 17:06:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.14
X-Spam-Level: 
X-Spam-Status: No, score=-102.14 tagged_above=-999 required=5 tests=[AWL=0.125, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
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 XqCNGMkSYp3x for <gen-art@ietfa.amsl.com>; Thu, 27 Dec 2012 17:06:24 -0800 (PST)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 1222F21F8DC5 for <gen-art@ietf.org>; Thu, 27 Dec 2012 17:06:24 -0800 (PST)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by morbo.tigertech.net (Postfix) with ESMTP id D657FA38E8 for <gen-art@ietf.org>; Thu, 27 Dec 2012 17:06:23 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 862A91C06CA4; Thu, 27 Dec 2012 17:06:22 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [10.10.10.104] (pool-70-106-135-81.clppva.east.verizon.net [70.106.135.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 04DBD1C06CA3; Thu, 27 Dec 2012 17:06:21 -0800 (PST)
Message-ID: <50DCF087.6090609@joelhalpern.com>
Date: Thu, 27 Dec 2012 20:06:15 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>
References: <50DCE616.70401@nostrum.com>
In-Reply-To: <50DCE616.70401@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org
Subject: [Gen-art]  Review: draft-higgs-oipf-urn-00.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Dec 2012 01:06:24 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-higgs-oipf-urn-00.txt
     A Uniform Resource Name (URN) Namespace for the Open IPTV Forum
                                   (OIPF)
Reviewer: Joel M. Halpern
Review Date: 27-December-2012
IETF LC End Date: 17-January-2013
IESG Telechat date: 24-January-2013

Summary: As far as this reviewer can tell, this document is ready for 
publication as an informational RFC.  It seems to be properly formed 
according to the rules of RFC 3406.

The justification of need seems very light.  I have no idea how this 
compares with the standards the IEtF has applied to such justifications 
in the past, and therefore can not make any judgment as to its 
appropriateness.

Major issues:

Minor issues:

Nits/editorial comments:

From david.black@emc.com  Fri Dec 28 12:26:28 2012
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C73BF21F8E15; Fri, 28 Dec 2012 12:26:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.539
X-Spam-Level: 
X-Spam-Status: No, score=-103.539 tagged_above=-999 required=5 tests=[AWL=1.060, BAYES_00=-2.599, GB_I_LETTER=-2, USER_IN_WHITELIST=-100]
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 7TwTLXQ4+d-t; Fri, 28 Dec 2012 12:26:28 -0800 (PST)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id D653521F8E14; Fri, 28 Dec 2012 12:26:27 -0800 (PST)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id qBSKQKWv000647 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 28 Dec 2012 15:26:20 -0500
Received: from mailhub.lss.emc.com (mailhubhoprd05.lss.emc.com [10.254.222.129]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Fri, 28 Dec 2012 15:26:00 -0500
Received: from mxhub22.corp.emc.com (mxhub22.corp.emc.com [128.222.70.134]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id qBSKPxgX012649; Fri, 28 Dec 2012 15:26:00 -0500
Received: from mx15a.corp.emc.com ([169.254.1.210]) by mxhub22.corp.emc.com ([128.222.70.134]) with mapi; Fri, 28 Dec 2012 15:25:59 -0500
From: "Black, David" <david.black@emc.com>
To: "rogaglia@cisco.com" <rogaglia@cisco.com>, Stephen Kent <kent@bbn.com>, Sean Turner <turners@ieca.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Date: Fri, 28 Dec 2012 15:25:47 -0500
Thread-Topic: Gen-ART review of draft-ietf-sidr-algorithm-agility-09
Thread-Index: Ac3lOYUa+SMuJHJqQnWqMAKs4+qaRg==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71287CBF04D@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-cr-puzzleid: {2EE00D5C-0E52-4397-B700-FAB3D89CF142}
x-cr-hashedpuzzle: EDy+ HCD/ PqAl WOGp ayJy b2ru hjd7 lJ1f rcct s40t vlnj w84h zYJu 3D3+ AAfVJA== AAoJ2g==; 6; ZwBlAG4ALQBhAHIAdABAAGkAZQB0AGYALgBvAHIAZwA7AGsAZQBuAHQAQABiAGIAbgAuAGMAbwBtADsAcgBvAGcAYQBnAGwAaQBhAEAAYwBpAHMAYwBvAC4AYwBvAG0AOwBzAGkAZAByAEAAaQBlAHQAZgAuAG8AcgBnADsAcwB0AGIAcgB5AGEAbgB0AEAAYwBpAHMAYwBvAC4AYwBvAG0AOwB0AHUAcgBuAGUAcgBzAEAAaQBlAGMAYQAuAGMAbwBtAA==; Sosha1_v1; 7; {2EE00D5C-0E52-4397-B700-FAB3D89CF142}; ZABhAHYAaQBkAC4AYgBsAGEAYwBrAEAAZQBtAGMALgBjAG8AbQA=; Fri, 28 Dec 2012 20:25:47 GMT; RwBlAG4ALQBBAFIAVAAgAHIAZQB2AGkAZQB3ACAAbwBmACAAZAByAGEAZgB0AC0AaQBlAHQAZgAtAHMAaQBkAHIALQBhAGwAZwBvAHIAaQB0AGgAbQAtAGEAZwBpAGwAaQB0AHkALQAwADkA
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: Stewart Bryant <stbryant@cisco.com>, "sidr@ietf.org" <sidr@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-sidr-algorithm-agility-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Dec 2012 20:26:28 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-sidr-algorithm-agility-09
Reviewer: David L. Black
Review Date: December 28, 2012
IETF LC End Date: December 14, 2012

Summary:

This draft is on the right track but has open issues, described in the revi=
ew.

I apologize for the tardy arrival of this review after the end of IETF Last
Call for this draft - the last few months have been a rather busy time for =
me.

This draft specifies the algorithm transition process for RPKI, which
entails coordinated issuance of new certificates and other signed products
across the collection of RPKI CAs in a fashion that ensures that at least
one set of signed products is usable at all times.

The draft is generally well-written and clear, but has an unfortunate
nomenclature change problem that is the primary open issue[*].

Major issues:

[*] Section 4.7 changes the meaning of the algorithm suite names (A, B
and C) from prior sections.  This also affects Sections 6 and 7.
I have classified this as a major issue as I believe it introduces
severe lack of clarity (and potential ambiguity) into the following
two paragraphs in Section 7:=20

   During Phase 1, a CA that revokes a certificate under Suite A SHOULD
   revoke the corresponding certificate under Suite B, if that
   certificate exists.  During Phase 4, a CA that revokes a certificate
   under Suite A SHOULD revoke the corresponding certificate under Suite
   C, if that certificate exists.

   During Phase 1, a CA may revoke certificates under Suite B without
   revoking them under Suite A, since the Suite B products are for test
   purposes.  During Phase 4 a CA may revoke certificates issued under
   Suite C without revoking them under Suite A, since Suite C products
   are being deprecated.

Despite the use of three letters (A, B and C), there are only two
algorithm suites involved, and different instances of Suite A refer to
different algorithm suites.  In each paragraph, the first instance of
"Suite A" refers to the same algorithm suite as "Suite C", and the
second instance of "Suite A" refers to the same algorithm suite
as "Suite B".

It would be much better and clearer to not change the meaning of the=20
algorithm suite names until the EOL date. In addition, this change
should enable removal of the Suite C concept from this draft.  I
strongly recommend removing the Suite C concept, as the C-A-B
chronological order of suite introduction dates seems counter-intuitive.

Minor issues:

Starting in Section 4.3.1, there are a number of uses of "will be"
(future tense) in the milestone and phase descriptions.  All of
these uses of "will be" should be reviewed to determine whether
"MUST be" is appropriate, e.g., as appears to be the case for
this sentence in 4.3.1:

   Additionally, the new algorithm transition timeline document will be
   published with the following information:

When "MUST be" is not appropriate, present tense (i.e., "is") is
preferable.

Nits/editorial:

Abstract: The following two sentences don't quite line up:

   The process
   is expected to be completed in a time scale of months or years.
   Consequently, no emergency transition is specified. =20

Also, section 4.2 indicates that a multi-year transition timeframe
is expected, which suggests that "months" is not appropriate in
the abstract.  Suggested rephrasing:

   The time available to complete the transition process
   is expected to be several years.
   Consequently, no emergency transition process is specified.

Section 2. Introduction: The first sentence in the last paragraph
mentions a forthcoming BCP on transition timetable.  The rest of
that paragraph implies that the BCP is for a single transition, as
opposed to being a BCP for transitions in general.  It would be
helpful to clarify that at the start of the paragraph, e.g.,
by adding "For each algorithm transition," to the start of the
paragraph.

Section 3 Definitions: Is there any concern about possible
confusion of the use of "Suite B" in this draft with NSA Suite B?
The draft is clear on what Suite B means for RPKI, but I suspect
that RPKI Suite B and NSA Suite B are unlikely to match, if ever.

Describing Phase 0 as both the steady state of the RPKI and the first
phase of transition is confusing (e.g., in 4.3).  It would be clearer
if Phase 0 began with publication of the updated RPKI algorithm
document (Milestone 1) and that the activities that are unchanged
from steady state were described as not changing in phase 0.

Starting near the end of section 4.3, the three characters
|-> are used in figures to represent an RPKI hierarchy relationship;
that relationship should be defined and/or explained before it is used.
For clarity, I'd suggest swapping the order of the two paragraphs
above that figure in 4.3 and making the following change at the end
of the paragraph that is moved down (addition of the word
"certificate" is the important change):

OLD
   and shows the relationship between three CAs (X, Y, and Z) that form
   a chain.
NEW
   and shows the relationships among the three CAs (X, Y, and Z)
   that participate in a certificate chain.

Subsequent uses of |-> seemed clear to me.

Section 4.5 Phase 2 says that Suite B product SHOULD be stored at
independent publication points, but does not make it clear that this
recommendation applies beyond phase 2.  I suggest adding text to
make that clear - a reference to Section 9 (which is clear about
this) may be useful as part of that text.

In Section 6, please expand the ROA acronym on first use and consider
whether it should be defined in Section 3.  I'm also assuming that the
ASN acronym is intended to refer to ASN.1 content; if not, that
acronym also needs attention.

idnits 2.12.13 found a couple of minor nits:

  ** There is 1 instance of too long lines in the document, the longest one
     being 23 characters in excess of 72.

  =3D=3D The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword=
, but
     does not include the phrase in its RFC 2119 key words list.

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
+1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-778=
6
david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
----------------------------------------------------


From elwynd@dial.pipex.com  Sun Dec 30 07:26:47 2012
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7A6721F8812 for <gen-art@ietfa.amsl.com>; Sun, 30 Dec 2012 07:26:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.487
X-Spam-Level: 
X-Spam-Status: No, score=-102.487 tagged_above=-999 required=5 tests=[AWL=0.113, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 wlKh394LHdgF for <gen-art@ietfa.amsl.com>; Sun, 30 Dec 2012 07:26:47 -0800 (PST)
Received: from auth.a.painless.aa.net.uk (a.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e33]) by ietfa.amsl.com (Postfix) with ESMTP id 9B3D121F872C for <gen-art@ietf.org>; Sun, 30 Dec 2012 07:26:43 -0800 (PST)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by a.painless.aa.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <elwynd@dial.pipex.com>) id 1TpKmX-0003nW-F8; Sun, 30 Dec 2012 15:26:35 +0000
From: Elwyn Davies <elwynd@dial.pipex.com>
To: "Sriram, Kotikalapudi" <kotikalapudi.sriram@nist.gov>
In-Reply-To: <D7A0423E5E193F40BE6E94126930C4930BB91F89F3@MBCLUSTER.xchange.nist.gov>
References: <CCF9F24F.2E422%terry.manderson@icann.org> ,<1356091602.11916.15388.camel@mightyatom> , <D7A0423E5E193F40BE6E94126930C4930BB91F89E7@MBCLUSTER.xchange.nist.gov> <D7A0423E5E193F40BE6E94126930C4930BB91F89F3@MBCLUSTER.xchange.nist.gov>
Content-Type: text/plain
Date: Sun, 30 Dec 2012 15:25:40 +0000
Message-Id: <1356881140.11916.16732.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
X-Spam-Score-a.painless.aa.net.uk: -4.0
Cc: Russ White <russw@riw.us>, General Area Review Team <gen-art@ietf.org>, Terry Manderson <terry.manderson@icann.org>
Subject: Re: [Gen-art] Gen-art LC/Telechat review of draft-ietf-sidr-usecases-05.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Dec 2012 15:26:47 -0000

Hi Sriram, Terry.

The new draft covers almost everything in the review and is fine with
one exception.

On ree-reading the draft and Terry's reponse to my original comment
about 'make-before-break', I have come to the conclusion that this
phrase is possibly confusing.  Arguably you actually have a
'break-before-make' policy! 

So if I (now) understand correctly the following explanation:

> > s6.x: Given the 'make-before-break' principle, would it be sensible
> to
> > describe the add before the revoke in each case?
> 
> ahh.. I think we have a disconnect. make before break is considered in
> the
> routing sense that a route is considered o.k. (UNKNOWN) unless proven
> otherwise, this means you can remove ALL RPKI object for a route, and
> it
> will still exist happily until a new and conflicting RPKI ROA is
> created..
> And we are working to that. Not necessarily making a new valid object
> before
> breaking the old valid object. That would then imply ownership of a
> prefix
> can then be in two places at the same time. And like the transfer of
> title
> for a house, overlap tends to be considered a bad thing. (co-authors,
> chime
> in here!)
> 
the timeline for the transition between one ROA and a new one would be

Time BGP FIB Event       ROA Event              Route Validation status
T0   Route R1 recvd                             (initially?) NotFound
T0+  Route R1 installed                         NotFound
T1                       ROA1 covering R1 recvd Valid
T2                       ROA1 revoked           NotFound
T3                       ROA2 recvd             Invalid (or Valid)
T3+  Route R1 removed    (for the Invalid case)

So to my mind the treatment of the toutes might be described as
'optimistic acceptance' or 'negative vetting' (as routes are only thrown
out if explicit negative evidence is received) but the ROA
mechanism/policy is definitely break the old ROA before issuing a new
one to avoid having conflicting ones in existence.

It may be that:
- not using the term 'make-before-break' but rather using Terry's words
would avoid 'interpretation'.
- explaining that seeing contradictory ROAs in a router is bad news and
one should check for revocations - presumably the RPKI infrastructure
would prevent a DoS attack here.

Best wishes for the New Year,
Elwyn
On Thu, 2012-12-27 at 16:20 -0500, Sriram, Kotikalapudi wrote:
> Hi Elwyn, Terry:
> 
> Please find attached the revised -06 version .txt file and also the rfc-diff file (-05 vs. -06).
> I think I have captured all the comments you two have gone over,
> and also included are minor comments from Barry, Stewart, others.
> Please let me know if I missed anything.
> 
> Elwyn: Please let me know if need to upload a -06 version to the the IETF submissions page
> at some pioint. Thanks again for all your commnets and help.
> 
> Sriram
> 
> ________________________________________
> From: Sriram, Kotikalapudi [kotikalapudi.sriram@nist.gov]
> Sent: Wednesday, December 26, 2012 12:17 AM
> To: Elwyn Davies; Terry Manderson
> Cc: General Area Review Team; draft-ietf-sidr-usecases.all@tools.ietf.org
> Subject: RE: Gen-art LC/Telechat review of  draft-ietf-sidr-usecases-05.txt
> 
> Hi Elwyn,
> 
> I have carefully read all the comments in this thread.
> Thank you for your review and comments -- very helpful.
> I have a good understanding of all the changes I need to make.
> I will spin a new version by Wednesday (12/26) evening or Thursday a.m.
> Will run it by Terry and Russ first and then post it here in this thread as an attachment.
> 
> Happy Holidays.
> 
> Sriram
> ________________________________________
> From: Elwyn Davies [elwynd@dial.pipex.com]
> Sent: Friday, December 21, 2012 7:06 AM
> To: Terry Manderson
> Cc: General Area Review Team; draft-ietf-sidr-usecases.all@tools.ietf.org
> Subject: Re: Gen-art LC/Telechat review of  draft-ietf-sidr-usecases-05.txt
> 
> Hi, Terry.
> 
> That's all fine by me.
> 
> Have a great Christmas!
> 
> Elwyn


From kent@bbn.com  Mon Dec 31 11:34:45 2012
Return-Path: <kent@bbn.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1ABE921F878A; Mon, 31 Dec 2012 11:34:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.599
X-Spam-Level: 
X-Spam-Status: No, score=-107.599 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 XK5DhhqNgzfp; Mon, 31 Dec 2012 11:34:44 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfa.amsl.com (Postfix) with ESMTP id 1203921F8738; Mon, 31 Dec 2012 11:34:44 -0800 (PST)
Received: from dhcp89-089-242.bbn.com ([128.89.89.242]:50892) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1Tpl8C-000BIp-TZ; Mon, 31 Dec 2012 14:34:40 -0500
Message-ID: <50E1E8D0.5010204@bbn.com>
Date: Mon, 31 Dec 2012 14:34:40 -0500
From: Stephen Kent <kent@bbn.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: "Black, David" <david.black@emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71287CBF04D@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71287CBF04D@MX15A.corp.emc.com>
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Stewart Bryant <stbryant@cisco.com>, "rogaglia@cisco.com" <rogaglia@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "sidr@ietf.org" <sidr@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-sidr-algorithm-agility-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Dec 2012 19:34:45 -0000

David,

> The draft is generally well-written and clear, but has an unfortunate
> nomenclature change problem that is the primary open issue[*].
>
> Major issues:
>
> [*] Section 4.7 changes the meaning of the algorithm suite names (A, B
> and C) from prior sections.

I have deleted all references to Alg Suite C throughout the doc, and
revised the text accordingly.

> This also affects Sections 6 and 7.
> I have classified this as a major issue as I believe it introduces
> severe lack of clarity (and potential ambiguity) into the following
> two paragraphs in Section 7:
>
>     During Phase 1, a CA that revokes a certificate under Suite A SHOULD
>     revoke the corresponding certificate under Suite B, if that
>     certificate exists.  During Phase 4, a CA that revokes a certificate
>     under Suite A SHOULD revoke the corresponding certificate under Suite
>     C, if that certificate exists.
>
>     During Phase 1, a CA may revoke certificates under Suite B without
>     revoking them under Suite A, since the Suite B products are for test
>     purposes.  During Phase 4 a CA may revoke certificates issued under
>     Suite C without revoking them under Suite A, since Suite C products
>     are being deprecated.
fixed.
> Despite the use of three letters (A, B and C), there are only two
> algorithm suites involved, and different instances of Suite A refer to
> different algorithm suites. In each paragraph, the first instance of
> "Suite A" refers to the same algorithm suite as "Suite C", and the
> second instance of "Suite A" refers to the same algorithm suite
> as "Suite B".
>
> It would be much better and clearer to not change the meaning of the
> algorithm suite names until the EOL date. In addition, this change
> should enable removal of the Suite C concept from this draft.
fixed
>    I
> strongly recommend removing the Suite C concept, as the C-A-B
> chronological order of suite introduction dates seems counter-intuitive.
Done.
>
> Minor issues:
>
> Starting in Section 4.3.1, there are a number of uses of "will be"
> (future tense) in the milestone and phase descriptions.  All of
> these uses of "will be" should be reviewed to determine whether
> "MUST be" is appropriate, e.g., as appears to be the case for
> this sentence in 4.3.1:
>
>     Additionally, the new algorithm transition timeline document will be
>     published with the following information:
I agree that "will be" needs to be changed to "MUST be" in a few places,
starting on page 5 (Section 2) where the need to update the CP and to 
publish an
alg transition timetable are first mentioned. An examination of the rest 
of the
doc shows that this change need be applied only when the alg transition 
doc is
mentioned.
> When "MUST be" is not appropriate, present tense (i.e., "is") is
> preferable.
fixed.
>
> Nits/editorial:
>
> Abstract: The following two sentences don't quite line up:
>
>     The process
>     is expected to be completed in a time scale of months or years.
>     Consequently, no emergency transition is specified.
>
> Also, section 4.2 indicates that a multi-year transition timeframe
> is expected, which suggests that "months" is not appropriate in
> the abstract.  Suggested rephrasing:
>
>     The time available to complete the transition process
>     is expected to be several years.
>     Consequently, no emergency transition process is specified.
fixed.
> Section 2. Introduction: The first sentence in the last paragraph
> mentions a forthcoming BCP on transition timetable.  The rest of
> that paragraph implies that the BCP is for a single transition, as
> opposed to being a BCP for transitions in general.  It would be
> helpful to clarify that at the start of the paragraph, e.g.,
> by adding "For each algorithm transition," to the start of the
> paragraph.
fixed.
> Section 3 Definitions: Is there any concern about possible
> confusion of the use of "Suite B" in this draft with NSA Suite B?
> The draft is clear on what Suite B means for RPKI, but I suspect
> that RPKI Suite B and NSA Suite B are unlikely to match, if ever.
We defined what "Suite B" is in the terminology section, so I
think no further clarification is required here.
> Describing Phase 0 as both the steady state of the RPKI and the first
> phase of transition is confusing (e.g., in 4.3).  It would be clearer
> if Phase 0 began with publication of the updated RPKI algorithm
> document (Milestone 1) and that the activities that are unchanged
> from steady state were described as not changing in phase 0.
we need to be able to refer to steady state, separate from the
first milestone in the transition process, but I agree that referring to
it as the first phase of the transition process is confusing. I have
changed the text accordingly.
> Starting near the end of section 4.3, the three characters
> |-> are used in figures to represent an RPKI hierarchy relationship;
> that relationship should be defined and/or explained before it is used.
> For clarity, I'd suggest swapping the order of the two paragraphs
> above that figure in 4.3 and making the following change at the end
> of the paragraph that is moved down (addition of the word
> "certificate" is the important change):
>
> OLD
>     and shows the relationship between three CAs (X, Y, and Z) that form
>     a chain.
> NEW
>     and shows the relationships among the three CAs (X, Y, and Z)
>     that participate in a certificate chain.
>
> Subsequent uses of |-> seemed clear to me.
I'll defer to Roque here, as the repository representation is his design.
> Section 4.5 Phase 2 says that Suite B product SHOULD be stored at
> independent publication points, but does not make it clear that this
> recommendation applies beyond phase 2.  I suggest adding text to
> make that clear - a reference to Section 9 (which is clear about
> this) may be useful as part of that text.
I have added a forward pointer to Section 9 here.
> In Section 6, please expand the ROA acronym on first use and consider
> whether it should be defined in Section 3.  I'm also assuming that the
> ASN acronym is intended to refer to ASN.1 content; if not, that
> acronym also needs attention.
ASN = Autonomous System Number. I expended the acronym as it appears
only here. I added a ROA definition to Section 3.
> idnits 2.12.13 found a couple of minor nits:
>
>    ** There is 1 instance of too long lines in the document, the longest one
>       being 23 characters in excess of 72.
I'll let Roque address this issue.
>
>    == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but
>       does not include the phrase in its RFC 2119 key words list.
fixed.


From david.black@emc.com  Mon Dec 31 11:58:22 2012
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0532421F8798; Mon, 31 Dec 2012 11:58:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.686
X-Spam-Level: 
X-Spam-Status: No, score=-103.686 tagged_above=-999 required=5 tests=[AWL=0.913, BAYES_00=-2.599, GB_I_LETTER=-2, USER_IN_WHITELIST=-100]
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 YEkM6i6jwr30; Mon, 31 Dec 2012 11:58:21 -0800 (PST)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id ECCA021F8781; Mon, 31 Dec 2012 11:58:20 -0800 (PST)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id qBVJwDtx018582 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 31 Dec 2012 14:58:13 -0500
Received: from mailhub.lss.emc.com (mailhubhoprd01.lss.emc.com [10.254.221.251]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Mon, 31 Dec 2012 14:58:00 -0500
Received: from mxhub13.corp.emc.com (mxhub13.corp.emc.com [128.222.70.234]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id qBVJvvne002947; Mon, 31 Dec 2012 14:57:59 -0500
Received: from mx15a.corp.emc.com ([169.254.1.210]) by mxhub13.corp.emc.com ([128.222.70.234]) with mapi; Mon, 31 Dec 2012 14:57:58 -0500
From: "Black, David" <david.black@emc.com>
To: Stephen Kent <kent@bbn.com>
Date: Mon, 31 Dec 2012 14:57:57 -0500
Thread-Topic: Gen-ART review of draft-ietf-sidr-algorithm-agility-09
Thread-Index: Ac3njf3a/Rf0YVKgRU+J2U5oHDjWLQAANeIA
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71287DB217C@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71287CBF04D@MX15A.corp.emc.com> <50E1E8D0.5010204@bbn.com>
In-Reply-To: <50E1E8D0.5010204@bbn.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "rogaglia@cisco.com" <rogaglia@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "sidr@ietf.org" <sidr@ietf.org>, Stewart Bryant <stbryant@cisco.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-sidr-algorithm-agility-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Dec 2012 19:58:22 -0000

Steve,

This all looks good; thanks for the quick response.

> > [*] Section 4.7 changes the meaning of the algorithm suite names (A, B
> > and C) from prior sections.

> I have deleted all references to Alg Suite C throughout the doc, and
> revised the text accordingly.

Magnificent - that'll be a significant improvement.

> > Starting in Section 4.3.1, there are a number of uses of "will be"
> > (future tense) in the milestone and phase descriptions.  All of
> > these uses of "will be" should be reviewed to determine whether
> > "MUST be" is appropriate, e.g., as appears to be the case for
> > this sentence in 4.3.1:
> >
> >     Additionally, the new algorithm transition timeline document will b=
e
> >     published with the following information:

> I agree that "will be" needs to be changed to "MUST be" in a few places,
> starting on page 5 (Section 2) where the need to update the CP and to pub=
lish an
> alg transition timetable are first mentioned. An examination of the rest =
of the
> doc shows that this change need be applied only when the alg transition d=
oc is
> mentioned.

That sounds reasonable.

> > Section 3 Definitions: Is there any concern about possible
> > confusion of the use of "Suite B" in this draft with NSA Suite B?
> > The draft is clear on what Suite B means for RPKI, but I suspect
> > that RPKI Suite B and NSA Suite B are unlikely to match, if ever.
>
> We defined what "Suite B" is in the terminology section, so I
> think no further clarification is required here.

That's ok with me, but I thought it was worth asking.

Thanks,
--David

> -----Original Message-----
> From: Stephen Kent [mailto:kent@bbn.com]
> Sent: Monday, December 31, 2012 2:35 PM
> To: Black, David
> Cc: rogaglia@cisco.com; Sean Turner; gen-art@ietf.org; sidr@ietf.org; Ste=
wart
> Bryant
> Subject: Re: Gen-ART review of draft-ietf-sidr-algorithm-agility-09
>=20
> David,
>=20
> > The draft is generally well-written and clear, but has an unfortunate
> > nomenclature change problem that is the primary open issue[*].
> >
> > Major issues:
> >
> > [*] Section 4.7 changes the meaning of the algorithm suite names (A, B
> > and C) from prior sections.
>=20
> I have deleted all references to Alg Suite C throughout the doc, and
> revised the text accordingly.
>=20
> > This also affects Sections 6 and 7.
> > I have classified this as a major issue as I believe it introduces
> > severe lack of clarity (and potential ambiguity) into the following
> > two paragraphs in Section 7:
> >
> >     During Phase 1, a CA that revokes a certificate under Suite A SHOUL=
D
> >     revoke the corresponding certificate under Suite B, if that
> >     certificate exists.  During Phase 4, a CA that revokes a certificat=
e
> >     under Suite A SHOULD revoke the corresponding certificate under Sui=
te
> >     C, if that certificate exists.
> >
> >     During Phase 1, a CA may revoke certificates under Suite B without
> >     revoking them under Suite A, since the Suite B products are for tes=
t
> >     purposes.  During Phase 4 a CA may revoke certificates issued under
> >     Suite C without revoking them under Suite A, since Suite C products
> >     are being deprecated.
> fixed.
> > Despite the use of three letters (A, B and C), there are only two
> > algorithm suites involved, and different instances of Suite A refer to
> > different algorithm suites. In each paragraph, the first instance of
> > "Suite A" refers to the same algorithm suite as "Suite C", and the
> > second instance of "Suite A" refers to the same algorithm suite
> > as "Suite B".
> >
> > It would be much better and clearer to not change the meaning of the
> > algorithm suite names until the EOL date. In addition, this change
> > should enable removal of the Suite C concept from this draft.
> fixed
> >    I
> > strongly recommend removing the Suite C concept, as the C-A-B
> > chronological order of suite introduction dates seems counter-intuitive=
.
> Done.
> >
> > Minor issues:
> >
> > Starting in Section 4.3.1, there are a number of uses of "will be"
> > (future tense) in the milestone and phase descriptions.  All of
> > these uses of "will be" should be reviewed to determine whether
> > "MUST be" is appropriate, e.g., as appears to be the case for
> > this sentence in 4.3.1:
> >
> >     Additionally, the new algorithm transition timeline document will b=
e
> >     published with the following information:
> I agree that "will be" needs to be changed to "MUST be" in a few places,
> starting on page 5 (Section 2) where the need to update the CP and to
> publish an
> alg transition timetable are first mentioned. An examination of the rest
> of the
> doc shows that this change need be applied only when the alg transition
> doc is
> mentioned.
> > When "MUST be" is not appropriate, present tense (i.e., "is") is
> > preferable.
> fixed.
> >
> > Nits/editorial:
> >
> > Abstract: The following two sentences don't quite line up:
> >
> >     The process
> >     is expected to be completed in a time scale of months or years.
> >     Consequently, no emergency transition is specified.
> >
> > Also, section 4.2 indicates that a multi-year transition timeframe
> > is expected, which suggests that "months" is not appropriate in
> > the abstract.  Suggested rephrasing:
> >
> >     The time available to complete the transition process
> >     is expected to be several years.
> >     Consequently, no emergency transition process is specified.
> fixed.
> > Section 2. Introduction: The first sentence in the last paragraph
> > mentions a forthcoming BCP on transition timetable.  The rest of
> > that paragraph implies that the BCP is for a single transition, as
> > opposed to being a BCP for transitions in general.  It would be
> > helpful to clarify that at the start of the paragraph, e.g.,
> > by adding "For each algorithm transition," to the start of the
> > paragraph.
> fixed.
> > Section 3 Definitions: Is there any concern about possible
> > confusion of the use of "Suite B" in this draft with NSA Suite B?
> > The draft is clear on what Suite B means for RPKI, but I suspect
> > that RPKI Suite B and NSA Suite B are unlikely to match, if ever.
> We defined what "Suite B" is in the terminology section, so I
> think no further clarification is required here.
> > Describing Phase 0 as both the steady state of the RPKI and the first
> > phase of transition is confusing (e.g., in 4.3).  It would be clearer
> > if Phase 0 began with publication of the updated RPKI algorithm
> > document (Milestone 1) and that the activities that are unchanged
> > from steady state were described as not changing in phase 0.
> we need to be able to refer to steady state, separate from the
> first milestone in the transition process, but I agree that referring to
> it as the first phase of the transition process is confusing. I have
> changed the text accordingly.
> > Starting near the end of section 4.3, the three characters
> > |-> are used in figures to represent an RPKI hierarchy relationship;
> > that relationship should be defined and/or explained before it is used.
> > For clarity, I'd suggest swapping the order of the two paragraphs
> > above that figure in 4.3 and making the following change at the end
> > of the paragraph that is moved down (addition of the word
> > "certificate" is the important change):
> >
> > OLD
> >     and shows the relationship between three CAs (X, Y, and Z) that for=
m
> >     a chain.
> > NEW
> >     and shows the relationships among the three CAs (X, Y, and Z)
> >     that participate in a certificate chain.
> >
> > Subsequent uses of |-> seemed clear to me.
> I'll defer to Roque here, as the repository representation is his design.
> > Section 4.5 Phase 2 says that Suite B product SHOULD be stored at
> > independent publication points, but does not make it clear that this
> > recommendation applies beyond phase 2.  I suggest adding text to
> > make that clear - a reference to Section 9 (which is clear about
> > this) may be useful as part of that text.
> I have added a forward pointer to Section 9 here.
> > In Section 6, please expand the ROA acronym on first use and consider
> > whether it should be defined in Section 3.  I'm also assuming that the
> > ASN acronym is intended to refer to ASN.1 content; if not, that
> > acronym also needs attention.
> ASN =3D Autonomous System Number. I expended the acronym as it appears
> only here. I added a ROA definition to Section 3.
> > idnits 2.12.13 found a couple of minor nits:
> >
> >    ** There is 1 instance of too long lines in the document, the longes=
t one
> >       being 23 characters in excess of 72.
> I'll let Roque address this issue.
> >
> >    =3D=3D The document seems to use 'NOT RECOMMENDED' as an RFC 2119 ke=
yword,
> but
> >       does not include the phrase in its RFC 2119 key words list.
> fixed.
>=20


From kotikalapudi.sriram@nist.gov  Mon Dec 31 18:04:09 2012
Return-Path: <kotikalapudi.sriram@nist.gov>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61E8721F8A1E for <gen-art@ietfa.amsl.com>; Mon, 31 Dec 2012 18:04:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.515
X-Spam-Level: 
X-Spam-Status: No, score=-6.515 tagged_above=-999 required=5 tests=[AWL=0.084,  BAYES_00=-2.599, 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 9G70oDfbrtnb for <gen-art@ietfa.amsl.com>; Mon, 31 Dec 2012 18:04:08 -0800 (PST)
Received: from wsget1.nist.gov (wsget1.nist.gov [129.6.13.150]) by ietfa.amsl.com (Postfix) with ESMTP id 1FBA321F86A9 for <gen-art@ietf.org>; Mon, 31 Dec 2012 18:04:07 -0800 (PST)
Received: from WSXGHUB2.xchange.nist.gov (129.6.18.19) by wsget1.nist.gov (129.6.13.150) with Microsoft SMTP Server (TLS) id 14.2.328.9; Mon, 31 Dec 2012 21:03:42 -0500
Received: from MBCLUSTER.xchange.nist.gov ([fe80::d479:3188:aec0:cb66]) by WSXGHUB2.xchange.nist.gov ([129.6.18.19]) with mapi; Mon, 31 Dec 2012 21:04:06 -0500
From: "Sriram, Kotikalapudi" <kotikalapudi.sriram@nist.gov>
To: Elwyn Davies <elwynd@dial.pipex.com>
Date: Mon, 31 Dec 2012 21:04:05 -0500
Thread-Topic: Gen-art LC/Telechat review of  draft-ietf-sidr-usecases-05.txt
Thread-Index: Ac3mohMResKKQD51T0KCJ4n6B5ep2wBGwGp2
Message-ID: <D7A0423E5E193F40BE6E94126930C4930BB91F89FE@MBCLUSTER.xchange.nist.gov>
References: <CCF9F24F.2E422%terry.manderson@icann.org> ,<1356091602.11916.15388.camel@mightyatom> , <D7A0423E5E193F40BE6E94126930C4930BB91F89E7@MBCLUSTER.xchange.nist.gov> <D7A0423E5E193F40BE6E94126930C4930BB91F89F3@MBCLUSTER.xchange.nist.gov>, <1356881140.11916.16732.camel@mightyatom>
In-Reply-To: <1356881140.11916.16732.camel@mightyatom>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Russ White <russw@riw.us>, General Area Review Team <gen-art@ietf.org>, "Sriram, Kotikalapudi" <kotikalapudi.sriram@nist.gov>, Terry Manderson <terry.manderson@icann.org>
Subject: Re: [Gen-art] Gen-art LC/Telechat review of draft-ietf-sidr-usecases-05.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Jan 2013 02:04:09 -0000

>
> The new draft covers almost everything in the review and is fine with
> one exception.

Thanks for the re-read.

Please see further down for my next comment/response.

>
> On ree-reading the draft and Terry's reponse to my original comment
> about 'make-before-break', I have come to the conclusion that this
> phrase is possibly confusing.  Arguably you actually have a
> 'break-before-make' policy!
>
> So if I (now) understand correctly the following explanation:
>
>> > s6.x: Given the 'make-before-break' principle, would it be sensible
>> to
>> > describe the add before the revoke in each case?
>>
>> ahh.. I think we have a disconnect. make before break is considered in
>> the
>> routing sense that a route is considered o.k. (UNKNOWN) unless proven
>> otherwise, this means you can remove ALL RPKI object for a route, and
>> it
>> will still exist happily until a new and conflicting RPKI ROA is
>> created..
>> And we are working to that. Not necessarily making a new valid object
>> before
>> breaking the old valid object. That would then imply ownership of a
>> prefix
>> can then be in two places at the same time. And like the transfer of
>> title
>> for a house, overlap tends to be considered a bad thing. (co-authors,
>> chime
>> in here!)
>>
> the timeline for the transition between one ROA and a new one would be
>
> Time BGP FIB Event       ROA Event              Route Validation status
> T0   Route R1 recvd                             (initially?) NotFound
> T0+  Route R1 installed                         NotFound
> T1                       ROA1 covering R1 recvd Valid
> T2                       ROA1 revoked           NotFound
> T3                       ROA2 recvd             Invalid (or Valid)
> T3+  Route R1 removed    (for the Invalid case)
>
> So to my mind the treatment of the toutes might be described as
> 'optimistic acceptance' or 'negative vetting' (as routes are only thrown
> out if explicit negative evidence is received) but the ROA
> mechanism/policy is definitely break the old ROA before issuing a new
> one to avoid having conflicting ones in existence.

The make-before-break principle clearly applies in these two situations:
(1) When there is a suballocation situation; see Example 1 below,
(2) If it is the same prefix owner creating a different ROA=20
for all or part of the prefix; see Example 2 below.

Example 1 (suballocation situation):=20

My ISP used to originate my prefix (suballocation) from their AS.
Now I have my own ASN and I wish to announce my prefix
with my AS as the origin,
and I still connect upstream to the same ISP AS.
The ISP had previously created a ROA for my suballocation
with their ASN as the origin AS.
Even though I will be creating a new ROA for my own said route origination,=
=20
I would much prefer (even require) that they continue to keep that existing=
 ROA active
at least until I am all good with my own new ROA.
I also prefer they continue to announce my prefix (or an aggregate above it=
)=20
while I am getting up to speed.
They (my upstream ISP) will anyway receive my traffic and pass it down to m=
y AS.
There will be no conflict between the two ROAs (mine and ISP's).=20
They can be both be active and valid simultaneously.=20
I (as suballocation owner) would be happy for that.
ISP can withdraw their ROA for my suballoaction later if they wish.

Example 2 (same prefix owner creating a different ROA):

Say, Org. A owns 10.1.0.0/20 and have ROA {10.1.0.0/20, AS 64499},
and currently announces route (10.1.0.0/20, AS 64499).=20
They also have another AS that is AS 64511.
Say, they decided they want to split the prefix for TE or other purpose, an=
d=20
wish to announce=20
10.1.0.0/21 from AS 64499, and 10.1.8.0/21 from AS64511.
Certainly, they should create new ROAs {10.1.0.0/21, AS 64499}
and {10.1.8.0/21, AS 64511}=20
before they revoke/withdraw their existing ROA {10.1.0.0/20, AS 64499}.
They may even create the new more specific ROAs, and not withdraw the exist=
ing ROA. =20
There is no conflict due to the different ROAs in this case.

Example 3 (the transfer case):
When there is a transfer of prefix ownership from Org. A to Org. B,
the onus is on the Org. B to create a ROA for their proposed
route announcement before actually announcing the route.
Note that Org. B has its own AS  (different from AS that Org. A has).=20
Org. B creating its own ROA first is a safe thing to do rather than assume =
that=20
the previous owner=92s ROA will be revoked/withdrawn before=20
Org. B announces its route.
A CRL will propagate for Org. A=92s cert for that prefix
and their old ROA will be withdrawn/revoked,
but with this type of transfer use case, it is prudent for
Org. B to allow some time for its own ROA to be in place
before announcing its route.
This is more like make-ROA-then-announce principle.
We can add some clarification/suggestion of this nature in Section 6.
Please let us know if this seems reasonable.

Sriram=20

>
> It may be that:
> - not using the term 'make-before-break' but rather using Terry's words
> would avoid 'interpretation'.
> - explaining that seeing contradictory ROAs in a router is bad news and
> one should check for revocations - presumably the RPKI infrastructure
> would prevent a DoS attack here.
>
> Best wishes for the New Year,
> Elwyn=
