
From elwynd@dial.pipex.com  Thu Feb  2 05:09:31 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 5431D21F89F4 for <gen-art@ietfa.amsl.com>; Thu,  2 Feb 2012 05:09:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.246
X-Spam-Level: 
X-Spam-Status: No, score=-1.246 tagged_above=-999 required=5 tests=[AWL=1.354,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id olZoj9UcFpQq for <gen-art@ietfa.amsl.com>; Thu,  2 Feb 2012 05:09:31 -0800 (PST)
Received: from b.c.painless.aaisp.net.uk (c.painless.aaisp.net.uk [IPv6:2001:8b0:0:30::51bb:1e35]) by ietfa.amsl.com (Postfix) with ESMTP id 7640221F89F1 for <gen-art@ietf.org>; Thu,  2 Feb 2012 05:09:24 -0800 (PST)
Received: from 250.254.187.81.in-addr.arpa ([81.187.254.250]) by c.painless.aaisp.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <elwynd@dial.pipex.com>) id 1RswPi-0003Lj-JQ for gen-art@ietf.org; Thu, 02 Feb 2012 13:09:22 +0000
From: Elwyn Davies <elwynd@dial.pipex.com>
To: General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain
Date: Thu, 02 Feb 2012 13:09:17 +0000
Message-Id: <1328188157.4790.2947.camel@mightyatom.folly.org.uk>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
Subject: [Gen-art] Gen-art review of draft-ietf-dime-pmip6-lr-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: Thu, 02 Feb 2012 13:09:31 -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-dime-pmip6-lr-07.txt
Reviewer: Elwyn Davies
Review Date: 2 February 2012
IETF LC End Date: 24 January 2012
IESG Telechat date: 16 February 2012

Summary:
I have a couple of queries/minor issues regarding checking whether LMA1
and LMA2 are the same node and some hand waving over the idea of
'localized routing setup/signaliing'.  There are also a few minor nits.
Otherwise this is ready for the IESG.

[This document missed the normal gen-art last call allocation
notification mechanism for some reason - so I didn't realize it was on
my allocation till the end of last call and as a result the review is a
bit late.]

Major issues:
None

Minor issues:
s5.1, para 3 and s5.2, last para:
In s5.1:
> MAG1 can verify
>    whether both MAGs are under the same LMA by comparing the addresses
>    of LMA1 and LMA2.
Is this guaranteed to work?  Should we care? Or is this just too bad if
the LMA has multiple addresses and the two MNs have different ideas?
However in s5.2:
> In the case where MNs share the same LMA, LR should be initiated by
>    LMA1 (i.e.,LMA2) since only LMA1 knows that both MN1 and MN2 belong
>    to itself by looking up the binding cache entries corresponding to
>    MN1 and MN2. 
I am unsure whether these two statements are talking about the same
thing - and, if so, are they contradictory?

s5.1, last para:
> Figure 4 shows another example scenario, similar to the example
>    scenario illustrated in Figure 3, LMA1 does not respond to MAG1 with
>    the address of LMA2, instead setting up a localized routing path
>    directly between itself and LMA2 via localized routing signaling.
I am unsure what 'localized routing signaliing' would involve.  What
would the nodes do for this?  Appears to involve some waving of hands.

On a slightly broader point, there are a number of places where the
phrase 'localized routing setup' (or similar) is used.  It would, I
think, be useful to add a few words indicating what is thought to be
involved although actually doing it is clearly out of scope of this
document.

Nits/editorial comments:

s1, first sentence:
> Proxy Mobile IPv6 (PMIPv6) [RFC5213] allows the Mobility Access
>    Gateway to optimize media delivery by locally routing packets *within
>    itself*, 
Do you mean this? Shouldn't this be within the local network of the MAG?
I have to admit that s9.2 of RFC 5213 is a bit ambiguous here as it is
unclear whether 'locally connected' means a direct point-to-point
connection or just locally routed.  Presumabnly a static node could be
in the local net rather than actually directly connected.  Perhaps it
might be worth copying a bit of the text from RFC 5213 here.

s4.2: Expand IPv4-MN-HoA.
s4.3: Expand MN-HNP and HAAA. 

s5.1, para 3: Extraneous space in MIP6- Feature-Vector (MFV). (Might be
good to use non-breaking hyphens in the various AVP titles to avoid
splits across lines).
s5.1, para 3: s/indicating Direct routing/indicating direct routing/
55.1, para 6 (bottom of page 9): s/anchored to different MAGs is
   supported. .  LMA1/anchored to different MAGs is
   supported. LMA1/

Fig 5: Would improve readability to offset the 'Option 1' and 'Option 2'
labels one space rightwards as the '1' blends into the vertical line at
the moment.


From kathleen.moriarty@emc.com  Thu Feb  2 06:15:45 2012
Return-Path: <kathleen.moriarty@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 8B4AD21F86B1; Thu,  2 Feb 2012 06:15:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.814
X-Spam-Level: 
X-Spam-Status: No, score=-9.814 tagged_above=-999 required=5 tests=[AWL=0.785,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zB6DWUk7PwZK; Thu,  2 Feb 2012 06:15:45 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id DFE9721F86A7; Thu,  2 Feb 2012 06:15:44 -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 q12EFRI2009415 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Feb 2012 09:15:41 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.130]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Thu, 2 Feb 2012 09:15:16 -0500
Received: from mxhub21.corp.emc.com (mxhub21.corp.emc.com [128.222.70.133]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q12EFFj8017899; Thu, 2 Feb 2012 09:15:15 -0500
Received: from mx06a.corp.emc.com ([169.254.1.153]) by mxhub21.corp.emc.com ([128.222.70.133]) with mapi; Thu, 2 Feb 2012 09:15:15 -0500
From: <kathleen.moriarty@emc.com>
To: <draft-kucherawy-authres-spf-erratum.all@tools.ietf.org>, <ietf@ietf.org>,  <gen-art@ietf.org>
Date: Thu, 2 Feb 2012 09:15:11 -0500
Thread-Topic: Gen-ART review for draft-kucherawy-authres-spf-erratum-01
Thread-Index: AczhtRLJBvVGVkBJS/qwO9eQTEqwFQ==
Message-ID: <AE31510960917D478171C79369B660FA0E2C119FCA@MX06A.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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: msk@cloudmark.com
Subject: [Gen-art] Gen-ART review for draft-kucherawy-authres-spf-erratum-01
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, 02 Feb 2012 14:15:45 -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-kucherawy-authres-spf-erratum-01
Reviewer: Kathleen Moriarty
Review Date: 2012-02-02
IETF LC End Date: 2012-02-03
IESG Telechat date: (if known)

Summary:  This draft is ready for publication.
   This memo updates the registry of authentication method results in
   Authentication-Results: message header fields, correcting a
   discontinuity between the original registry creation and the SPF
   specification.


Major issues:

Minor issues:

Nits/editorial comments:
_______________________________________________
Gen-art mailing list
Gen-art@ietf.org<mailto:Gen-art@ietf.org>
https://www.ietf.org/mailman/listinfo/gen-art




From miguel.a.garcia@ericsson.com  Thu Feb  2 06:51:40 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 B91BA21F8596 for <gen-art@ietfa.amsl.com>; Thu,  2 Feb 2012 06:51:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.844
X-Spam-Level: 
X-Spam-Status: No, score=-9.844 tagged_above=-999 required=5 tests=[AWL=0.755,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pJHO7Fs+zqhd for <gen-art@ietfa.amsl.com>; Thu,  2 Feb 2012 06:51:40 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id D066D21F858F for <gen-art@ietf.org>; Thu,  2 Feb 2012 06:51:39 -0800 (PST)
X-AuditID: c1b4fb3d-b7b26ae000000a35-f8-4f2aa2fa3629
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 5A.C9.02613.AF2AA2F4; Thu,  2 Feb 2012 15:51:38 +0100 (CET)
Received: from [159.107.24.237] (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.94) with Microsoft SMTP Server id 8.3.137.0; Thu, 2 Feb 2012 15:51:38 +0100
Message-ID: <4F2AA2F8.4010004@ericsson.com>
Date: Thu, 2 Feb 2012 15:51:36 +0100
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:10.0) Gecko/20120129 Thunderbird/10.0
MIME-Version: 1.0
To: Zhen Cao <zehn.cao@gmail.com>, Hui Deng <denghui02@gmail.com>,  sunseawq@huawei.com, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Cc: General Area Review Team <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-hokey-erp-aak-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: Thu, 02 Feb 2012 14:51:40 -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-hokey-erp-aak-07
Reviewer: Miguel Garcia <miguel.a.garcia@ericsson.com>
Review Date: 2011-01-02
IETF LC End Date: 2012-02-07

Summary: This draft is on the right track but has open issues, described 
in the review.

Major issues:

- None

Minor issues:

- The main problem I have with this draft is the lack of normative text 
(RFC 2119 reserved words) in relevant paragraphs. If interoperability is 
to be granted, an effort should be taken in adding quite a few more 
normative statements.

However, having said that, the section where I find more that there 
should be more normative text, is Section 3, which is an "Overview" 
section. In general, an overview section should use descriptive, but not 
normative text.

For example, take the last paragraph in Page 5 (that continues to Page 
6). One possible change is to make normative the text and move it outside 
a section whose title is "Overview".

    Upon receiving the message, the ERP/AAK server MUST first use the
    keyName indicated in the keyName-NAI to look up the rIK and MUST
    check the integrity and freshness of the message. Then the ERP/AAK
    server MUST verify the identity of the peer by checking the username
    portion of the KeyName-NAI.  If any of the checks fail, the server
    MUST send an early- authentication finish message (EAP-Finish/Re-auth
    with E-flag set) with the Result flag set to '1'.  Next, the server
    MUST authorize the CAP specified in the CAP-Identifier TLV.  In
    success case, the server MUST derive a pMSK from the pRK for each CAP
    carried in the the CAP-Identifier field using the sequence number
    associated with CAP-Identifier as an input to the key derivation.
    (see d. in the figure 1).

    Then the ERP/AAK server MUST transport the pMSK to the authorized CAP
    via AAA Section 7 as described in figure 2 (see e.1,e.2 in the figure
    2). Note that key distribution in the figure 2 is one part of step d.
    in the figure 1.

The the last paragraph in Section 3 also contains an "Optionally", which 
I believe should be replaced with a capitalized "OPTIONAL"

Another instance: towards the end of Section 5.2, the text reads:

    HMAC-SHA256-128 is mandatory to implement and should be enabled in
    the default configuration.

and should probably be:

    HMAC-SHA256-128 is REQUIRED to be implemented and SHOULD be enabled in
    the default configuration.

Similarly, the last paragraph in Section 5.2 reads:

    If the EAP-Initiate/Re-auth packet is not supported by the SAP, it is
    discarded silently.

and should probably be:

    If the EAP-Initiate/Re-auth packet is not supported by the SAP, it
    SHOULD be discarded silently.



- Another topic, Section 9 (IANA Considerations) reads:

    Further, this document registers a Early authentication usage label
    from the "USRK Key Labels" name space with a value:

       EAP Early-Authentication Root Key@ietf.org


I am missing the sentence to name the master registry where the USRK Key 
Labels subregistry is stored. This is the Extended Master Session Key 
(EMSK) Parameters registry (I guess). And probably this comment is also 
valid for the rest of the IANA actions: the main registry is not named, 
and it is hard to find it.


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

From jeff_downs@partech.com  Thu Feb  2 10:58:38 2012
Return-Path: <jeff_downs@partech.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 E598F21F8534; Thu,  2 Feb 2012 10:58:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.413
X-Spam-Level: 
X-Spam-Status: No, score=-2.413 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VtyJOYHlMvYs; Thu,  2 Feb 2012 10:58:38 -0800 (PST)
Received: from imail2.partech.com (imail2b.partech.com [192.133.62.26]) by ietfa.amsl.com (Postfix) with ESMTP id D97A121F8508; Thu,  2 Feb 2012 10:58:31 -0800 (PST)
Received: from eclipse.partech.com (eclipse.partech.com [172.16.8.4]) by imail2.partech.com (8.13.1/8.12.11) with ESMTP id q12IwJkN024248; Thu, 2 Feb 2012 13:58:19 -0500
Received: from beasley.parcorp.local (beasley.partech.com [172.16.16.70]) by eclipse.partech.com (8.12.9/8.12.9) with ESMTP id q12IwAbs025706; Thu, 2 Feb 2012 13:58:18 -0500 (EST)
Received: from [192.168.167.155] ([192.168.167.155]) by beasley.parcorp.local with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 2 Feb 2012 13:56:56 -0500
Message-ID: <4F2ADC65.2010700@partech.com>
Date: Thu, 02 Feb 2012 13:56:37 -0500
From: Jeff Downs <jeff_downs@partech.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: "Richard L. Barnes" <rbarnes@bbn.com>
References: <84A8BD83-8B84-4049-B9CF-1AB0E36211F9@bbn.com>
In-Reply-To: <84A8BD83-8B84-4049-B9CF-1AB0E36211F9@bbn.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Feb 2012 18:56:58.0356 (UTC) FILETIME=[70828B40:01CCE1DC]
X-Mailman-Approved-At: Thu, 02 Feb 2012 11:05:55 -0800
Cc: jimsgti@gmail.com, General Area Review Team <gen-art@ietf.org>, abegen@cisco.com, IETF-Discussion Discussion <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-payload-rtp-klv-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: Thu, 02 Feb 2012 18:58:39 -0000

Richard and all:

I am one of the co-authors of the above named draft.  Thank you for the 
review and comments on the draft.

After discussion with the document shepherd and the WG co-chair, we 
decided to incorporate some of the suggested changes into a new revision 
(-03) of the draft.  This new revision was uploaded to the IETF 
datatracker yesterday and is available now:
http://tools.ietf.org/html/draft-ietf-payload-rtp-klv-03

Please see below for specifics on how each of the Gen-ART comments were 
addressed.

Again, thank you for the review and comments.

Jeff Downs
PAR Government Systems



On 1/26/2012 4:11 PM, Richard L. Barnes wrote:
 > ===== MINOR =====
 >
 > Section 6.1.: Given that the KLV format can carry a variety of data
 > types, would it be helpful for this type to have one or more
 > parameters to describe what types of KLVs might be in the stream?

The widely varied nature and use cases of this format do not lend very 
well to specific parametrization describing the data. KLV, by its very 
nature, is self-identifying through the use of universally unique keys.
No changes were made to the draft in this regard.

 > Section 8, "appropriate caution and security practices": It could be
 > helpful to note here that it is dangerous for implementations to
 > accept active content from streams that lack authenticity or
 > integrity protection, since this could make them vulnerable to
 > attacks using spoofed packets.

Text has been added to draft revision -03 in Section 8 to describe this 
scenario and to caution implementers.


 > ===== EDITORIAL =====
 >
 > Section 4: It would be helpful to note a little more explicitly that
 > a KLVunit is a sequence of KLVs, without any overall framing (thus
 > the requirement for the marker bit / timestamp to distinguish).

Text has been added to the preface of Section 4 to further clarify this 
in draft revision -03.

 > Section 4.2., last paragraph: It would be helpful to note explicitly
 > what this paragraph implies: A receiver MUST consider a KLV unit to
 > be completed when it receives either a packet with m=1 or a packet
 > with a new timestamp.  In the former case, the packet payload is
 > included in the KLVunit; in the latter case, it is not.

The suggested text has been added to draft revision -03 at the end of 
Section 4.2.

 > Section 4.3.1.1., "are left to each implementation": It could be
 > helpful to point to some ways that KLV recovery is done, as guidance
 > to implementors. (Provided this can be done without IPR concerns.)

In the interest of keeping the draft simple and focused on carriage 
within RTP specifically, I have not added guidance on KLV recovery 
techniques.  Techniques for this are not inherently unique to the 
carriage of KLV data over RTP (that is, such techniques can be applied 
to any KLV data where known damage/loss has occurred), and thus we feel 
this is outside the scope of this document.

 > Section 8, "The main security considerations ... alternatives may
 > exist": This chunk of text doesn't really add anything beyond the
 > normal security considerations for RTP.  Suggest just adding an
 > appropriate reference to standard RTP security practices.

This text comes directly from the template data in 
http://tools.ietf.org/id/draft-ietf-payload-rtp-howto-01.txt
To keep the reviewed draft in line with the template, no edits have been 
made here relevant to this comment.

 > Section 8, "Receivers are encouraged to place limits...": Suggest
 > changing "are encouraged to" to "SHOULD".

This change has been incorporated into revision -03 of the draft.

From mahoney@nostrum.com  Thu Feb  2 14:43: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 7048321F866E for <gen-art@ietfa.amsl.com>; Thu,  2 Feb 2012 14:43: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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zAAbFyebbD4D for <gen-art@ietfa.amsl.com>; Thu,  2 Feb 2012 14:43:30 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id E76A721F85D4 for <gen-art@ietf.org>; Thu,  2 Feb 2012 14:43:29 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-57-95-103.dllstx.fios.verizon.net [173.57.95.103]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q12MhTGO069811 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 2 Feb 2012 16:43:29 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <4F2B1191.4010209@nostrum.com>
Date: Thu, 02 Feb 2012 16:43:29 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
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.95.103 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2012-02-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: Thu, 02 Feb 2012 22:43:30 -0000

Hi all,

Here's the link to the new LC assignments:
http://wiki.tools.ietf.org/dav/genart/reviewers-120202-lc.html

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


And 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 miguel.a.garcia@ericsson.com  Thu Feb  2 23:18:45 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 C60E721F84E2 for <gen-art@ietfa.amsl.com>; Thu,  2 Feb 2012 23:18:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.907
X-Spam-Level: 
X-Spam-Status: No, score=-9.907 tagged_above=-999 required=5 tests=[AWL=0.692,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ee860JxQ2xuD for <gen-art@ietfa.amsl.com>; Thu,  2 Feb 2012 23:18:44 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id 94C4F21F8499 for <gen-art@ietf.org>; Thu,  2 Feb 2012 23:18:44 -0800 (PST)
X-AuditID: c1b4fb39-b7bf2ae0000069a1-88-4f2b8a523c75
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 27.72.27041.25A8B2F4; Fri,  3 Feb 2012 08:18:43 +0100 (CET)
Received: from [159.107.48.13] (153.88.115.8) by esessmw0256.eemea.ericsson.se (153.88.115.97) with Microsoft SMTP Server id 8.3.137.0; Fri, 3 Feb 2012 08:18:42 +0100
Message-ID: <4F2B8A50.9030901@ericsson.com>
Date: Fri, 3 Feb 2012 08:18:40 +0100
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:10.0) Gecko/20120129 Thunderbird/10.0
MIME-Version: 1.0
To: Zhen Cao <zehn.cao@gmail.com>
References: <4F2AA2F8.4010004@ericsson.com> <CAProHATtfqmXk0-EVOSDbQZqpNW-nFtrchA56XAMP2XWpnd6oA@mail.gmail.com>
In-Reply-To: <CAProHATtfqmXk0-EVOSDbQZqpNW-nFtrchA56XAMP2XWpnd6oA@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Cc: Hui Deng <denghui02@gmail.com>, General Area Review Team <gen-art@ietf.org>, "sunseawq@huawei.com" <sunseawq@huawei.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-hokey-erp-aak-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: Fri, 03 Feb 2012 07:18:45 -0000

Zhen,

The issue with IANA is double:

On one side, you need to clearly indicate to IANA which registry they 
need to change.

On another side, someone reading this RFC should be able to go to 
www.iana.org and find the registry.

The solve both issues you don't need a reference to RFC 5295. What you 
need to say "Extended Master Session Key (EMSK) Parameters registry" in 
the IANA considerations section, because this is the official name by 
which the registry is known.

BR,

          Miguel

On 03/02/2012 8:11, Zhen Cao wrote:
>> >
>> >  - Another topic, Section 9 (IANA Considerations) reads:
>> >
>> >     Further, this document registers a Early authentication usage label
>> >     from the "USRK Key Labels" name space with a value:
>> >
>> >        EAP Early-Authentication RootKey@ietf.org
>> >
>> >
>> >  I am missing the sentence to name the master registry where the USRK Key
>> >  Labels subregistry is stored. This is the Extended Master Session Key (EMSK)
>> >  Parameters registry (I guess). And probably this comment is also valid for
>> >  the rest of the IANA actions: the main registry is not named, and it is hard
>> >  to find it.
> [CZ]: EMSK or DSRK lable is defined in the section 8.1 "Key Lables" of
> RFC5295. We will add reference to RFC5295 to fix this. Thanks.
>
>> >

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

From miguel.a.garcia@ericsson.com  Thu Feb  2 23:57:16 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 E9C8C1F0C41 for <gen-art@ietfa.amsl.com>; Thu,  2 Feb 2012 23:57:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.961
X-Spam-Level: 
X-Spam-Status: No, score=-9.961 tagged_above=-999 required=5 tests=[AWL=0.638,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CxZPsMYTWm9I for <gen-art@ietfa.amsl.com>; Thu,  2 Feb 2012 23:57:16 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id D82921F0C43 for <gen-art@ietf.org>; Thu,  2 Feb 2012 23:57:15 -0800 (PST)
X-AuditID: c1b4fb3d-b7b26ae000000a35-82-4f2b935a34f8
Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 8C.96.02613.A539B2F4; Fri,  3 Feb 2012 08:57:14 +0100 (CET)
Received: from [159.107.48.13] (153.88.115.8) by esessmw0191.eemea.ericsson.se (153.88.115.85) with Microsoft SMTP Server id 8.3.137.0; Fri, 3 Feb 2012 08:57:13 +0100
Message-ID: <4F2B9358.3000503@ericsson.com>
Date: Fri, 3 Feb 2012 08:57:12 +0100
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:10.0) Gecko/20120129 Thunderbird/10.0
MIME-Version: 1.0
To: Qin Wu <bill.wu@huawei.com>
References: <4F2AA2F8.4010004@ericsson.com> <CAProHATtfqmXk0-EVOSDbQZqpNW-nFtrchA56XAMP2XWpnd6oA@mail.gmail.com> <4F2B8A50.9030901@ericsson.com> <9FDA0EEDC44A4921B6D7D5A536D96BC0@china.huawei.com>
In-Reply-To: <9FDA0EEDC44A4921B6D7D5A536D96BC0@china.huawei.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Cc: Hui Deng <denghui02@gmail.com>, Zhen Cao <zehn.cao@gmail.com>, General Area Review Team <gen-art@ietf.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-hokey-erp-aak-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: Fri, 03 Feb 2012 07:57:17 -0000

Hi Qin Wu:

As far as I remember, there is a policy in force that does not allow URLs 
in RFCs, in particular in the IANA section. I believe that the motivation 
is that URLs can change with time.

The proposal is (something around these lines):

     Further, this document instructs IANA to add a new lable in the User 
Specific Root Keys (USRK) Key Labels of the Extended Master Session Key 
(EMSK) Parameters registry, as follows:

         EAP Early-Authentication Root Key@ietf.org

/Miguel


On 03/02/2012 8:43, Qin Wu wrote:
> Hi, Miguel:
> I think you are looking for this registry.
> http://www.iana.org/assignments/emsk-parameters/emsk-parameters.xml
> To make clear, the proposed change is replace the OLD Text
> "
> Further, this document registers a Early authentication usage label
>     from the "USRK Key Labels" name space with a value:
>
>        EAP Early-Authentication Root Key@ietf.org
> "
> With the NEW Text:
> "
> Further, this document registers a Early authentication usage label
>     from the "User Specific Root Keys (USRK) Key Labels" name space maintained at
> http://www.iana.org/assignments/emsk-parameters/emsk-parameters.xml
>   with a value:
>
>        EAP Early-Authentication Root Key@ietf.org
> "
> Hope this addresses your comment.
>
> Regards!
> -Qin Wu
> ----- Original Message -----
> From: "Miguel A. Garcia"<Miguel.A.Garcia@ericsson.com>
> To: "Zhen Cao"<zehn.cao@gmail.com>
> Cc: "Hui Deng"<denghui02@gmail.com>;<sunseawq@huawei.com>; "Stephen Farrell"<stephen.farrell@cs.tcd.ie>; "General Area Review Team"<gen-art@ietf.org>
> Sent: Friday, February 03, 2012 3:18 PM
> Subject: Re: Gen-ART review of draft-ietf-hokey-erp-aak-07
>
>
>> Zhen,
>>
>> The issue with IANA is double:
>>
>> On one side, you need to clearly indicate to IANA which registry they
>> need to change.
>>
>> On another side, someone reading this RFC should be able to go to
>> www.iana.org and find the registry.
>>
>> The solve both issues you don't need a reference to RFC 5295. What you
>> need to say "Extended Master Session Key (EMSK) Parameters registry" in
>> the IANA considerations section, because this is the official name by
>> which the registry is known.
>>
>> BR,
>>
>>           Miguel
>>
>> On 03/02/2012 8:11, Zhen Cao wrote:
>>>>>
>>>>>   - Another topic, Section 9 (IANA Considerations) reads:
>>>>>
>>>>>      Further, this document registers a Early authentication usage label
>>>>>      from the "USRK Key Labels" name space with a value:
>>>>>
>>>>>         EAP Early-Authentication RootKey@ietf.org
>>>>>
>>>>>
>>>>>   I am missing the sentence to name the master registry where the USRK Key
>>>>>   Labels subregistry is stored. This is the Extended Master Session Key (EMSK)
>>>>>   Parameters registry (I guess). And probably this comment is also valid for
>>>>>   the rest of the IANA actions: the main registry is not named, and it is hard
>>>>>   to find it.
>>> [CZ]: EMSK or DSRK lable is defined in the section 8.1 "Key Lables" of
>>> RFC5295. We will add reference to RFC5295 to fix this. Thanks.
>>>
>>>>>
>>
>> --
>> Miguel A. Garcia
>> +34-91-339-3608
>> Ericsson Spain

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

From alexey.melnikov@isode.com  Fri Feb  3 05:14:21 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 46D5A21F8625; Fri,  3 Feb 2012 05:14:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.099
X-Spam-Level: 
X-Spam-Status: No, score=-102.099 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1wLe8FBT9DWy; Fri,  3 Feb 2012 05:14:20 -0800 (PST)
Received: from rufus.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id 6E70E21F856D; Fri,  3 Feb 2012 05:14:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1328274857; d=isode.com; s=selector; i=@isode.com; bh=p040+9qOAPW1BYfPD5JvCq4sWOPy7yNFjhEkpCArW6Q=; 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=Jhds+fq1zgVGtDOykvZX7ojd9Hz51G15ZXla6PpoaXs456uWdvdo/OTl77qxMOrZs/9toH hgo90Dzu26awl06pNURGGIR6C9/wBf1FqRoSGLwSZva5O97JqsEsHTXBpjEYnFe+5FY6zL +izWzbQRGOcjxPG5h1xJy+tsM+jxuTg=;
Received: from [144.254.105.99] (dhcp-guest-bru-peg1-144-254-105-99.cisco.com [144.254.105.99])  by rufus.isode.com (submission channel) via TCP with ESMTPSA  id <TyvdpwAvKKUJ@rufus.isode.com>; Fri, 3 Feb 2012 13:14:17 +0000
Message-ID: <4F2BDDB1.8030709@isode.com>
Date: Fri, 03 Feb 2012 13:14:25 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
To: Mike Jones <Michael.Jones@microsoft.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
References: <4F2575CE.9040001@isode.com> <4E1F6AAD24975D4BA5B16804296739436638B7AD@TK5EX14MBXC284.redmond.corp.microsoft.com> <4F27C37C.1090008@isode.com>
In-Reply-To: <4F27C37C.1090008@isode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: General Area Review Team <gen-art@ietf.org>, "oauth@ietf.org" <oauth@ietf.org>, "draft-ietf-oauth-v2-bearer.all@tools.ietf.org" <draft-ietf-oauth-v2-bearer.all@tools.ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>
Subject: Re: [Gen-art] [OAUTH-WG] Gen-ART review of draft-ietf-oauth-v2-bearer-15.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, 03 Feb 2012 13:14:21 -0000

On 31/01/2012 10:33, Alexey Melnikov wrote:
> On 30/01/2012 05:20, Mike Jones wrote:
  [...]
>> About your third minor issue on RFC 6125 versus RFC 2818, you'll find 
>> that, per the history entries, a previous reference to RFC 2818 was 
>> changed to RFC 6125 in draft 14 at the request of Security Area 
>> Director Stephen Farrell.
I've quickly chatted with Stephen and he said that he only asked the 
question and didn't necessarily instructed the WG to do the change from 
RFC 2818 to RFC 6125. Keeping this in mind...
>> If you'd like to see this reference reintroduced, I'd request that 
>> you work with Stephen on specific alternative proposed wording that 
>> is acceptable to both of you.
>  Ok, I can work with Stephen and Peter Saint-Andre (RFC 6125 
> co-author) on some text.

So, here are the proposed changes:

4.2.  Threat Mitigation

      To protect against token disclosure, confidentiality protection MUST
      be applied using TLS [RFC5246] with a ciphersuite that provides
      confidentiality and integrity protection.  This requires that the
      communication interaction between the client and the authorization
      server, as well as the interaction between the client and the
      resource server, utilize confidentiality and integrity protection.
      Since TLS is mandatory to implement and to use with this
      specification, it is the preferred approach for preventing token
      disclosure via the communication channel.  For those cases where the
      client is prevented from observing the contents of the token, token
      encryption MUST be applied in addition to the usage of TLS
      protection.  As a further defense against token disclosure, the
      client MUST validate the TLS certificate chain when making requests
      to protected resources.

I suggest inserting "[RFC5280]" at the end of the last sentence above.

      To deal with token capture and replay, the following recommendations
      are made: First, the lifetime of the token MUST be limited; one means
      of achieving this is by putting a validity time field inside the
      protected part of the token.  Note that using short-lived (one hour
      or less) tokens reduces the impact of them being leaked.  Second,
      confidentiality protection of the exchanges between the client and
      the authorization server and between the client and the resource
      server MUST be applied.  As a consequence, no eavesdropper along the
      communication path is able to observe the token exchange.
      Consequently, such an on-path adversary cannot replay the token.
      Furthermore, when presenting the token to a resource server, the
      client MUST verify the identity of that resource server, as per
      Representation and Verification of Domain-Based Application Service
      Identity within Internet Public Key Infrastructure Using X.509 (PKIX)
      Certificates in the Context of Transport Layer Security (TLS)
      [RFC6125].

Please replace the last sentence quoted above with:

      Furthermore, when presenting the token to a resource server, the
      client MUST verify the identity of that resource server, as per
      section 3.1 of [RFC2818].

[Expanded motivation for the change:
I think the reference to RFC 6125 needs to be replaced with the 
reference to section 3.1 of RFC 2818. Firstly, the procedure described 
in RFC 6125 differs slightly from RFC 2818 (matching of IP addresses is 
allowed, wildcards can be used with partial hostnames (e.g. foo* is 
allowed, where RFC 6125 doesn't allow for that). Secondly, if RFC 6125 
is referenced, then the OAuth document needs to say whether 
SRV-ID/URI-IDs are allowed and whether wildcards are allowed.]


From stephen.farrell@cs.tcd.ie  Fri Feb  3 05:17:54 2012
Return-Path: <stephen.farrell@cs.tcd.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 53A7721F856A; Fri,  3 Feb 2012 05:17:54 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hE7aKXORzqe0; Fri,  3 Feb 2012 05:17:53 -0800 (PST)
Received: from scss.tcd.ie (hermes.cs.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 1A12D21F8559; Fri,  3 Feb 2012 05:17:52 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id DD507171C25; Fri,  3 Feb 2012 13:17:51 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1328275071; bh=rCgo3aUfHyU0P3 j7PcJYxpIPsDcKFJXdpbM26as6Ppw=; b=YJIRE6iyfjwsolXos24jUKGEwv6qRf mVO2dOuqU/1OXTPfZviMP1OxLA7bxFdJLzfLOqh7qKmjawKuSSZfHcwPZABidHnh 6RYTi88X0vHVflGodBqSdZndrK+o2EtAbjGuuV7QNzoS0RwxTuLX8ADFo0/3Ns4B EhMbXl7w3/WamgqGdjH9NqiBxEXPVRniemdh2l3WUv7DztunB23bHp2JPFBBLFZh YajHxpspA5oxVvigPinKf6vqgBlEBCEapMOnNhHzzFUNa/a9pRWtVRzu8AMSeHX5 ffg5kMJhwf6A/QRgMZ+T33J9z/MVfZUMGu14BwerXhH/6/wP85N/QgcQ==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id 6BKpEOxwmkm1; Fri,  3 Feb 2012 13:17:51 +0000 (GMT)
Received: from [IPv6:2001:770:10:203:a288:b4ff:fe9c:bc5c] (unknown [IPv6:2001:770:10:203:a288:b4ff:fe9c:bc5c]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id C3537171C06; Fri,  3 Feb 2012 13:17:50 +0000 (GMT)
Message-ID: <4F2BDE75.4080405@cs.tcd.ie>
Date: Fri, 03 Feb 2012 13:17:41 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>
References: <4F2575CE.9040001@isode.com> <4E1F6AAD24975D4BA5B16804296739436638B7AD@TK5EX14MBXC284.redmond.corp.microsoft.com> <4F27C37C.1090008@isode.com> <4F2BDDB1.8030709@isode.com>
In-Reply-To: <4F2BDDB1.8030709@isode.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Mike Jones <Michael.Jones@microsoft.com>, IETF-Discussion Discussion <ietf@ietf.org>, General Area Review Team <gen-art@ietf.org>, "draft-ietf-oauth-v2-bearer.all@tools.ietf.org" <draft-ietf-oauth-v2-bearer.all@tools.ietf.org>, "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [Gen-art] [OAUTH-WG] Gen-ART review of draft-ietf-oauth-v2-bearer-15.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, 03 Feb 2012 13:17:54 -0000

That looks fine to me fwiw,
Thanks,
S.

On 02/03/2012 01:14 PM, Alexey Melnikov wrote:
> On 31/01/2012 10:33, Alexey Melnikov wrote:
>> On 30/01/2012 05:20, Mike Jones wrote:
> [...]
>>> About your third minor issue on RFC 6125 versus RFC 2818, you'll find
>>> that, per the history entries, a previous reference to RFC 2818 was
>>> changed to RFC 6125 in draft 14 at the request of Security Area
>>> Director Stephen Farrell.
> I've quickly chatted with Stephen and he said that he only asked the
> question and didn't necessarily instructed the WG to do the change from
> RFC 2818 to RFC 6125. Keeping this in mind...
>>> If you'd like to see this reference reintroduced, I'd request that
>>> you work with Stephen on specific alternative proposed wording that
>>> is acceptable to both of you.
>> Ok, I can work with Stephen and Peter Saint-Andre (RFC 6125 co-author)
>> on some text.
>
> So, here are the proposed changes:
>
> 4.2. Threat Mitigation
>
> To protect against token disclosure, confidentiality protection MUST
> be applied using TLS [RFC5246] with a ciphersuite that provides
> confidentiality and integrity protection. This requires that the
> communication interaction between the client and the authorization
> server, as well as the interaction between the client and the
> resource server, utilize confidentiality and integrity protection.
> Since TLS is mandatory to implement and to use with this
> specification, it is the preferred approach for preventing token
> disclosure via the communication channel. For those cases where the
> client is prevented from observing the contents of the token, token
> encryption MUST be applied in addition to the usage of TLS
> protection. As a further defense against token disclosure, the
> client MUST validate the TLS certificate chain when making requests
> to protected resources.
>
> I suggest inserting "[RFC5280]" at the end of the last sentence above.
>
> To deal with token capture and replay, the following recommendations
> are made: First, the lifetime of the token MUST be limited; one means
> of achieving this is by putting a validity time field inside the
> protected part of the token. Note that using short-lived (one hour
> or less) tokens reduces the impact of them being leaked. Second,
> confidentiality protection of the exchanges between the client and
> the authorization server and between the client and the resource
> server MUST be applied. As a consequence, no eavesdropper along the
> communication path is able to observe the token exchange.
> Consequently, such an on-path adversary cannot replay the token.
> Furthermore, when presenting the token to a resource server, the
> client MUST verify the identity of that resource server, as per
> Representation and Verification of Domain-Based Application Service
> Identity within Internet Public Key Infrastructure Using X.509 (PKIX)
> Certificates in the Context of Transport Layer Security (TLS)
> [RFC6125].
>
> Please replace the last sentence quoted above with:
>
> Furthermore, when presenting the token to a resource server, the
> client MUST verify the identity of that resource server, as per
> section 3.1 of [RFC2818].
>
> [Expanded motivation for the change:
> I think the reference to RFC 6125 needs to be replaced with the
> reference to section 3.1 of RFC 2818. Firstly, the procedure described
> in RFC 6125 differs slightly from RFC 2818 (matching of IP addresses is
> allowed, wildcards can be used with partial hostnames (e.g. foo* is
> allowed, where RFC 6125 doesn't allow for that). Secondly, if RFC 6125
> is referenced, then the OAuth document needs to say whether
> SRV-ID/URI-IDs are allowed and whether wildcards are allowed.]
>
>

From bill.wu@huawei.com  Thu Feb  2 20:53:22 2012
Return-Path: <bill.wu@huawei.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 D7FAF21F85DD for <gen-art@ietfa.amsl.com>; Thu,  2 Feb 2012 20:53:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.99
X-Spam-Level: 
X-Spam-Status: No, score=-5.99 tagged_above=-999 required=5 tests=[AWL=0.009,  BAYES_00=-2.599, J_CHICKENPOX_37=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X1ZAuGjIzo5e for <gen-art@ietfa.amsl.com>; Thu,  2 Feb 2012 20:53:22 -0800 (PST)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id BAABF21F85D7 for <gen-art@ietf.org>; Thu,  2 Feb 2012 20:53:21 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LYS0029RW8QWX@szxga04-in.huawei.com> for gen-art@ietf.org; Fri, 03 Feb 2012 12:53:15 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LYS00DDFW8QJ6@szxga04-in.huawei.com> for gen-art@ietf.org; Fri, 03 Feb 2012 12:53:14 +0800 (CST)
Received: from szxeml210-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AGR35175; Fri, 03 Feb 2012 12:53:13 +0800
Received: from SZXEML410-HUB.china.huawei.com (10.82.67.137) by szxeml210-edg.china.huawei.com (172.24.2.183) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 03 Feb 2012 12:52:48 +0800
Received: from w53375q (10.138.41.130) by szxeml410-hub.china.huawei.com (10.82.67.137) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 03 Feb 2012 12:53:03 +0800
Date: Fri, 03 Feb 2012 12:53:02 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: Elwyn Davies <davieseb@scss.tcd.ie>, General Area Review Team <gen-art@ietf.org>
Message-id: <BB94D1B3E4CD4E1BA7107AF5A99D19BE@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <1328187998.4790.2946.camel@mightyatom.folly.org.uk>
X-Mailman-Approved-At: Fri, 03 Feb 2012 05:24:12 -0800
Cc: draft-ietf-dime-pmip6-lr.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art review of draft-ietf-dime-pmip6-lr-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: Fri, 03 Feb 2012 04:53:23 -0000

Hi,Elwyn:
Thank for your valuable review. please see our replies below.
----- Original Message ----- 
From: "Elwyn Davies" <davieseb@scss.tcd.ie>
To: "General Area Review Team" <gen-art@ietf.org>
Cc: <draft-ietf-dime-pmip6-lr.all@tools.ietf.org>
Sent: Thursday, February 02, 2012 9:06 PM
Subject: Gen-art review of draft-ietf-dime-pmip6-lr-07


>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-dime-pmip6-lr-07.txt
> Reviewer: Elwyn Davies
> Review Date: 2 February 2012
> IETF LC End Date: 24 January 2012
> IESG Telechat date: 16 February 2012
> 
> Summary:
> I have a couple of queries/minor issues regarding checking whether LMA1
> and LMA2 are the same node and some hand waving over the idea of
> 'localized routing setup/signaliing'.  There are also a few minor nits.
> Otherwise this is ready for the IESG.
> 
> [This document missed the normal gen-art last call allocation
> notification mechanism for some reason - so I didn't realize it was on
> my allocation till the end of last call and as a result the review is a
> bit late.]
> 
> Major issues:
> None
> 
> Minor issues:
> s5.1, para 3 and s5.2, last para:
> In s5.1:
>> MAG1 can verify
>>    whether both MAGs are under the same LMA by comparing the addresses
>>    of LMA1 and LMA2.
> Is this guaranteed to work?  Should we care? Or is this just too bad if
> the LMA has multiple addresses and the two MNs have different ideas?

[Qin]: In the example described in the s5.1, we don't consider one LMA has two LMA address.
LMA1 and LMA2 may represent two different mobility entities identified by LMA1 adress and LMA2 adress respectively.
If LMA1 address is LMA2 address, this just indicate LMA1 and LMA2 are the same mobility entity.
Even one LMA have more than one LMA address, this still work since MAG can know if these LMA addresses come from
the same mobility entity based on MN1 and MN2's binding update list.

> However in s5.2:
>> In the case where MNs share the same LMA, LR should be initiated by
>>    LMA1 (i.e.,LMA2) since only LMA1 knows that both MN1 and MN2 belong
>>    to itself by looking up the binding cache entries corresponding to
>>    MN1 and MN2. 
> I am unsure whether these two statements are talking about the same
> thing - and, if so, are they contradictory?
> 

[Qin]: No Confliction, See above.

> s5.1, last para:
>> Figure 4 shows another example scenario, similar to the example
>>    scenario illustrated in Figure 3, LMA1 does not respond to MAG1 with
>>    the address of LMA2, instead setting up a localized routing path
>>    directly between itself and LMA2 via localized routing signaling.
> I am unsure what 'localized routing signaliing' would involve.  What
> would the nodes do for this?  Appears to involve some waving of hands.

[Qin]: LMA1 and LMA2 exchange to trigger corresponding LMA to setup binding entries
on the correspoding MAG for localized routing and establish localized
routing path between MAG1 and MAG2.

> On a slightly broader point, there are a number of places where the
> phrase 'localized routing setup' (or similar) is used.  It would, I
> think, be useful to add a few words indicating what is thought to be
> involved although actually doing it is clearly out of scope of this
> document.

[Qin]: Okay.

> Nits/editorial comments:
> 
> s1, first sentence:
>> Proxy Mobile IPv6 (PMIPv6) [RFC5213] allows the Mobility Access
>>    Gateway to optimize media delivery by locally routing packets *within
>>    itself*, 
> Do you mean this? Shouldn't this be within the local network of the MAG?
> I have to admit that s9.2 of RFC 5213 is a bit ambiguous here as it is
> unclear whether 'locally connected' means a direct point-to-point
> connection or just locally routed.  Presumabnly a static node could be
> in the local net rather than actually directly connected.  Perhaps it
> might be worth copying a bit of the text from RFC 5213 here.

[Qin]: Yes,locally routing packets within itself means when MN1 and MN2 are attached 
to the same MAG, the packet sent from MN1 and destined for MN2 should not be forwarded from
MAG through tunnel (MAG->LMA) to LMA and then tunneled back to MAG and finally sent to the MN2
through the same MAG. Instead, the packet destined for MN2 should be intercepted by the MAG attached 
by both MN1 and MN2 and sent to the MN2 directly through this MAG.

> s4.2: Expand IPv4-MN-HoA.

[Qin]: Okay.

> s4.3: Expand MN-HNP and HAAA. 

[Qin]: Okay.
> 
> s5.1, para 3: Extraneous space in MIP6- Feature-Vector (MFV). (Might be
> good to use non-breaking hyphens in the various AVP titles to avoid
> splits across lines).

[Qin]: Okay.

> s5.1, para 3: s/indicating Direct routing/indicating direct routing/

[Qin]: Okay.

> 55.1, para 6 (bottom of page 9): s/anchored to different MAGs is
>   supported. .  LMA1/anchored to different MAGs is
>   supported. LMA1/

[Qin]: Okay.

> 
> Fig 5: Would improve readability to offset the 'Option 1' and 'Option 2'
> labels one space rightwards as the '1' blends into the vertical line at
> the moment.

[Qin]: Okay.
>

From zehn.cao@gmail.com  Thu Feb  2 23:11:25 2012
Return-Path: <zehn.cao@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 47D8721F856F for <gen-art@ietfa.amsl.com>; Thu,  2 Feb 2012 23:11:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.388
X-Spam-Level: 
X-Spam-Status: No, score=-3.388 tagged_above=-999 required=5 tests=[AWL=0.211,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0dcSN9c1zTsU for <gen-art@ietfa.amsl.com>; Thu,  2 Feb 2012 23:11:24 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7845921F85DF for <gen-art@ietf.org>; Thu,  2 Feb 2012 23:11:24 -0800 (PST)
Received: by iagf6 with SMTP id f6so5260249iag.31 for <gen-art@ietf.org>; Thu, 02 Feb 2012 23:11:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=fbEig1TJGAQpOR3GbZ8qyYf0HO9WAu1EhwGdG+70wmM=; b=xkJhwQCIz2FPrnmzgGQN+60hxcVuzeGVCs+S1gsKblgFPJ1uH5+Lf3CeBf0nzsPxCA hk9YSMuYGeY9WXchzp+EfnL44s5BUSBf8poPl2iAjANbcXgPb0nsP9lkjlmXNbbjl+Sw GT4gQcEKr05pO75zRKh5iHCxNEK04jvBrBwF8=
MIME-Version: 1.0
Received: by 10.43.51.66 with SMTP id vh2mr5439622icb.39.1328253084159; Thu, 02 Feb 2012 23:11:24 -0800 (PST)
Received: by 10.43.130.129 with HTTP; Thu, 2 Feb 2012 23:11:24 -0800 (PST)
In-Reply-To: <4F2AA2F8.4010004@ericsson.com>
References: <4F2AA2F8.4010004@ericsson.com>
Date: Fri, 3 Feb 2012 15:11:24 +0800
Message-ID: <CAProHATtfqmXk0-EVOSDbQZqpNW-nFtrchA56XAMP2XWpnd6oA@mail.gmail.com>
From: Zhen Cao <zehn.cao@gmail.com>
To: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Fri, 03 Feb 2012 05:24:12 -0800
Cc: Hui Deng <denghui02@gmail.com>, General Area Review Team <gen-art@ietf.org>, sunseawq@huawei.com, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-hokey-erp-aak-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: Fri, 03 Feb 2012 07:11:25 -0000

Dear Miguel,

Thanks for the valuable view, see our replies inline.

Best regards,
Zhen

On Thu, Feb 2, 2012 at 10:51 PM, Miguel A. Garcia
<Miguel.A.Garcia@ericsson.com> wrote:
> 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 recei=
ve.
>
> Document: draft-ietf-hokey-erp-aak-07
> Reviewer: Miguel Garcia <miguel.a.garcia@ericsson.com>
> Review Date: 2011-01-02
> IETF LC End Date: 2012-02-07
>
> Summary: This draft is on the right track but has open issues, described =
in
> the review.
>
> Major issues:
>
> - None
>
> Minor issues:
>
> - The main problem I have with this draft is the lack of normative text (=
RFC
> 2119 reserved words) in relevant paragraphs. If interoperability is to be
> granted, an effort should be taken in adding quite a few more normative
> statements.
>
> However, having said that, the section where I find more that there shoul=
d
> be more normative text, is Section 3, which is an "Overview" section. In
> general, an overview section should use descriptive, but not normative te=
xt.
>
> For example, take the last paragraph in Page 5 (that continues to Page 6)=
.
> One possible change is to make normative the text and move it outside a
> section whose title is "Overview".
>
> =A0 Upon receiving the message, the ERP/AAK server MUST first use the
> =A0 keyName indicated in the keyName-NAI to look up the rIK and MUST
> =A0 check the integrity and freshness of the message. Then the ERP/AAK
> =A0 server MUST verify the identity of the peer by checking the username
> =A0 portion of the KeyName-NAI. =A0If any of the checks fail, the server
> =A0 MUST send an early- authentication finish message (EAP-Finish/Re-auth
> =A0 with E-flag set) with the Result flag set to '1'. =A0Next, the server
> =A0 MUST authorize the CAP specified in the CAP-Identifier TLV. =A0In
> =A0 success case, the server MUST derive a pMSK from the pRK for each CAP
> =A0 carried in the the CAP-Identifier field using the sequence number
> =A0 associated with CAP-Identifier as an input to the key derivation.
> =A0 (see d. in the figure 1).
>
> =A0 Then the ERP/AAK server MUST transport the pMSK to the authorized CAP
> =A0 via AAA Section 7 as described in figure 2 (see e.1,e.2 in the figure
> =A0 2). Note that key distribution in the figure 2 is one part of step d.
> =A0 in the figure 1.
>
> The the last paragraph in Section 3 also contains an "Optionally", which =
I
> believe should be replaced with a capitalized "OPTIONAL"

[CZ]: Good suggestion, we will revise the draft to reflect this.

>
> Another instance: towards the end of Section 5.2, the text reads:
>
> =A0 HMAC-SHA256-128 is mandatory to implement and should be enabled in
> =A0 the default configuration.
>
> and should probably be:
>
> =A0 HMAC-SHA256-128 is REQUIRED to be implemented and SHOULD be enabled i=
n
> =A0 the default configuration.

[CZ] Okay.

>
> Similarly, the last paragraph in Section 5.2 reads:
>
> =A0 If the EAP-Initiate/Re-auth packet is not supported by the SAP, it is
> =A0 discarded silently.
>
> and should probably be:
>
> =A0 If the EAP-Initiate/Re-auth packet is not supported by the SAP, it
> =A0 SHOULD be discarded silently.
>

[CZ] Okay.

>
> - Another topic, Section 9 (IANA Considerations) reads:
>
> =A0 Further, this document registers a Early authentication usage label
> =A0 from the "USRK Key Labels" name space with a value:
>
> =A0 =A0 =A0EAP Early-Authentication Root Key@ietf.org
>
>
> I am missing the sentence to name the master registry where the USRK Key
> Labels subregistry is stored. This is the Extended Master Session Key (EM=
SK)
> Parameters registry (I guess). And probably this comment is also valid fo=
r
> the rest of the IANA actions: the main registry is not named, and it is h=
ard
> to find it.

[CZ]: EMSK or DSRK lable is defined in the section 8.1 "Key Lables" of
RFC5295. We will add reference to RFC5295 to fix this. Thanks.

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



--=20
Best regards,
Zhen

From bill.wu@huawei.com  Thu Feb  2 23:45:05 2012
Return-Path: <bill.wu@huawei.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 BD10A21F856D for <gen-art@ietfa.amsl.com>; Thu,  2 Feb 2012 23:45:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.274
X-Spam-Level: 
X-Spam-Status: No, score=-6.274 tagged_above=-999 required=5 tests=[AWL=0.325,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k5qotywrsiyv for <gen-art@ietfa.amsl.com>; Thu,  2 Feb 2012 23:45:05 -0800 (PST)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 8EAFB21F8567 for <gen-art@ietf.org>; Thu,  2 Feb 2012 23:45:04 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LYT007AW44EEI@szxga04-in.huawei.com> for gen-art@ietf.org; Fri, 03 Feb 2012 15:43:26 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LYT00B9344CCH@szxga04-in.huawei.com> for gen-art@ietf.org; Fri, 03 Feb 2012 15:43:26 +0800 (CST)
Received: from szxeml210-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AGR41137; Fri, 03 Feb 2012 15:43:25 +0800
Received: from SZXEML408-HUB.china.huawei.com (10.82.67.95) by szxeml210-edg.china.huawei.com (172.24.2.183) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 03 Feb 2012 15:43:00 +0800
Received: from w53375q (10.138.41.130) by szxeml408-hub.china.huawei.com (10.82.67.95) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 03 Feb 2012 15:43:05 +0800
Date: Fri, 03 Feb 2012 15:43:03 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>, Zhen Cao <zehn.cao@gmail.com>
Message-id: <9FDA0EEDC44A4921B6D7D5A536D96BC0@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <4F2AA2F8.4010004@ericsson.com> <CAProHATtfqmXk0-EVOSDbQZqpNW-nFtrchA56XAMP2XWpnd6oA@mail.gmail.com> <4F2B8A50.9030901@ericsson.com>
X-Mailman-Approved-At: Fri, 03 Feb 2012 05:24:12 -0800
Cc: Hui Deng <denghui02@gmail.com>, General Area Review Team <gen-art@ietf.org>, bill.wu@huawei.com, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-hokey-erp-aak-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: Fri, 03 Feb 2012 07:45:05 -0000

Hi, Miguel:
I think you are looking for this registry.
http://www.iana.org/assignments/emsk-parameters/emsk-parameters.xml
To make clear, the proposed change is replace the OLD Text 
"
Further, this document registers a Early authentication usage label
   from the "USRK Key Labels" name space with a value:

      EAP Early-Authentication Root Key@ietf.org
"
With the NEW Text:
"
Further, this document registers a Early authentication usage label
   from the "User Specific Root Keys (USRK) Key Labels" name space maintained at
http://www.iana.org/assignments/emsk-parameters/emsk-parameters.xml
 with a value:

      EAP Early-Authentication Root Key@ietf.org
"
Hope this addresses your comment.

Regards!
-Qin Wu
----- Original Message ----- 
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
To: "Zhen Cao" <zehn.cao@gmail.com>
Cc: "Hui Deng" <denghui02@gmail.com>; <sunseawq@huawei.com>; "Stephen Farrell" <stephen.farrell@cs.tcd.ie>; "General Area Review Team" <gen-art@ietf.org>
Sent: Friday, February 03, 2012 3:18 PM
Subject: Re: Gen-ART review of draft-ietf-hokey-erp-aak-07


> Zhen,
> 
> The issue with IANA is double:
> 
> On one side, you need to clearly indicate to IANA which registry they 
> need to change.
> 
> On another side, someone reading this RFC should be able to go to 
> www.iana.org and find the registry.
> 
> The solve both issues you don't need a reference to RFC 5295. What you 
> need to say "Extended Master Session Key (EMSK) Parameters registry" in 
> the IANA considerations section, because this is the official name by 
> which the registry is known.
> 
> BR,
> 
>          Miguel
> 
> On 03/02/2012 8:11, Zhen Cao wrote:
>>> >
>>> >  - Another topic, Section 9 (IANA Considerations) reads:
>>> >
>>> >     Further, this document registers a Early authentication usage label
>>> >     from the "USRK Key Labels" name space with a value:
>>> >
>>> >        EAP Early-Authentication RootKey@ietf.org
>>> >
>>> >
>>> >  I am missing the sentence to name the master registry where the USRK Key
>>> >  Labels subregistry is stored. This is the Extended Master Session Key (EMSK)
>>> >  Parameters registry (I guess). And probably this comment is also valid for
>>> >  the rest of the IANA actions: the main registry is not named, and it is hard
>>> >  to find it.
>> [CZ]: EMSK or DSRK lable is defined in the section 8.1 "Key Lables" of
>> RFC5295. We will add reference to RFC5295 to fix this. Thanks.
>>
>>> >
> 
> -- 
> Miguel A. Garcia
> +34-91-339-3608
> Ericsson Spain

From bill.wu@huawei.com  Fri Feb  3 00:02:56 2012
Return-Path: <bill.wu@huawei.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 79BA521F8574 for <gen-art@ietfa.amsl.com>; Fri,  3 Feb 2012 00:02:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.281
X-Spam-Level: 
X-Spam-Status: No, score=-6.281 tagged_above=-999 required=5 tests=[AWL=0.318,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2cN5sdCsmGQl for <gen-art@ietfa.amsl.com>; Fri,  3 Feb 2012 00:02:55 -0800 (PST)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id E0FD721F8537 for <gen-art@ietf.org>; Fri,  3 Feb 2012 00:02:54 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LYT006PN4YA94@szxga04-in.huawei.com> for gen-art@ietf.org; Fri, 03 Feb 2012 16:01:23 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LYT00B754YACH@szxga04-in.huawei.com> for gen-art@ietf.org; Fri, 03 Feb 2012 16:01:22 +0800 (CST)
Received: from szxeml209-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AGU49226; Fri, 03 Feb 2012 16:01:22 +0800
Received: from SZXEML410-HUB.china.huawei.com (10.82.67.137) by szxeml209-edg.china.huawei.com (172.24.2.184) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 03 Feb 2012 16:00:48 +0800
Received: from w53375q (10.138.41.130) by szxeml410-hub.china.huawei.com (10.82.67.137) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 03 Feb 2012 16:01:13 +0800
Date: Fri, 03 Feb 2012 16:01:12 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
Message-id: <913D0A1AF3824099B6E8F09DDDF76BFF@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <4F2AA2F8.4010004@ericsson.com> <CAProHATtfqmXk0-EVOSDbQZqpNW-nFtrchA56XAMP2XWpnd6oA@mail.gmail.com> <4F2B8A50.9030901@ericsson.com> <9FDA0EEDC44A4921B6D7D5A536D96BC0@china.huawei.com> <4F2B9358.3000503@ericsson.com>
X-Mailman-Approved-At: Fri, 03 Feb 2012 05:24:12 -0800
Cc: Hui Deng <denghui02@gmail.com>, Zhen Cao <zehn.cao@gmail.com>, General Area Review Team <gen-art@ietf.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-hokey-erp-aak-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: Fri, 03 Feb 2012 08:02:56 -0000

Okay, your proposal looks good to me, many thanks.

Regards!
-Qin Wu
----- Original Message ----- 
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
To: "Qin Wu" <bill.wu@huawei.com>
Cc: "Zhen Cao" <zehn.cao@gmail.com>; "Hui Deng" <denghui02@gmail.com>; "Stephen Farrell" <stephen.farrell@cs.tcd.ie>; "General Area Review Team" <gen-art@ietf.org>
Sent: Friday, February 03, 2012 3:57 PM
Subject: Re: Gen-ART review of draft-ietf-hokey-erp-aak-07


> Hi Qin Wu:
> 
> As far as I remember, there is a policy in force that does not allow URLs 
> in RFCs, in particular in the IANA section. I believe that the motivation 
> is that URLs can change with time.
> 
> The proposal is (something around these lines):
> 
>     Further, this document instructs IANA to add a new lable in the User 
> Specific Root Keys (USRK) Key Labels of the Extended Master Session Key 
> (EMSK) Parameters registry, as follows:
> 
>         EAP Early-Authentication Root Key@ietf.org
> 
> /Miguel
> 
> 
> On 03/02/2012 8:43, Qin Wu wrote:
>> Hi, Miguel:
>> I think you are looking for this registry.
>> http://www.iana.org/assignments/emsk-parameters/emsk-parameters.xml
>> To make clear, the proposed change is replace the OLD Text
>> "
>> Further, this document registers a Early authentication usage label
>>     from the "USRK Key Labels" name space with a value:
>>
>>        EAP Early-Authentication Root Key@ietf.org
>> "
>> With the NEW Text:
>> "
>> Further, this document registers a Early authentication usage label
>>     from the "User Specific Root Keys (USRK) Key Labels" name space maintained at
>> http://www.iana.org/assignments/emsk-parameters/emsk-parameters.xml
>>   with a value:
>>
>>        EAP Early-Authentication Root Key@ietf.org
>> "
>> Hope this addresses your comment.
>>
>> Regards!
>> -Qin Wu
>> ----- Original Message -----
>> From: "Miguel A. Garcia"<Miguel.A.Garcia@ericsson.com>
>> To: "Zhen Cao"<zehn.cao@gmail.com>
>> Cc: "Hui Deng"<denghui02@gmail.com>;<sunseawq@huawei.com>; "Stephen Farrell"<stephen.farrell@cs.tcd.ie>; "General Area Review Team"<gen-art@ietf.org>
>> Sent: Friday, February 03, 2012 3:18 PM
>> Subject: Re: Gen-ART review of draft-ietf-hokey-erp-aak-07
>>
>>
>>> Zhen,
>>>
>>> The issue with IANA is double:
>>>
>>> On one side, you need to clearly indicate to IANA which registry they
>>> need to change.
>>>
>>> On another side, someone reading this RFC should be able to go to
>>> www.iana.org and find the registry.
>>>
>>> The solve both issues you don't need a reference to RFC 5295. What you
>>> need to say "Extended Master Session Key (EMSK) Parameters registry" in
>>> the IANA considerations section, because this is the official name by
>>> which the registry is known.
>>>
>>> BR,
>>>
>>>           Miguel
>>>
>>> On 03/02/2012 8:11, Zhen Cao wrote:
>>>>>>
>>>>>>   - Another topic, Section 9 (IANA Considerations) reads:
>>>>>>
>>>>>>      Further, this document registers a Early authentication usage label
>>>>>>      from the "USRK Key Labels" name space with a value:
>>>>>>
>>>>>>         EAP Early-Authentication RootKey@ietf.org
>>>>>>
>>>>>>
>>>>>>   I am missing the sentence to name the master registry where the USRK Key
>>>>>>   Labels subregistry is stored. This is the Extended Master Session Key (EMSK)
>>>>>>   Parameters registry (I guess). And probably this comment is also valid for
>>>>>>   the rest of the IANA actions: the main registry is not named, and it is hard
>>>>>>   to find it.
>>>> [CZ]: EMSK or DSRK lable is defined in the section 8.1 "Key Lables" of
>>>> RFC5295. We will add reference to RFC5295 to fix this. Thanks.
>>>>
>>>>>>
>>>
>>> --
>>> Miguel A. Garcia
>>> +34-91-339-3608
>>> Ericsson Spain
> 
> -- 
> Miguel A. Garcia
> +34-91-339-3608
> Ericsson Spain
>

From david.black@emc.com  Fri Feb  3 10:57:18 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 2466A21F853D; Fri,  3 Feb 2012 10:57:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.412
X-Spam-Level: 
X-Spam-Status: No, score=-109.412 tagged_above=-999 required=5 tests=[AWL=1.187, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LIQjTD0d3glL; Fri,  3 Feb 2012 10:57:17 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 3BE0C21F8476; Fri,  3 Feb 2012 10:57:16 -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 q13Iv3ln014116 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 Feb 2012 13:57:06 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.145]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Fri, 3 Feb 2012 13:56:42 -0500
Received: from mxhub12.corp.emc.com (mxhub12.corp.emc.com [10.254.92.107]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q13IufHE016263; Fri, 3 Feb 2012 13:56:41 -0500
Received: from mx14a.corp.emc.com ([169.254.1.94]) by mxhub12.corp.emc.com ([10.254.92.107]) with mapi; Fri, 3 Feb 2012 13:56:40 -0500
From: <david.black@emc.com>
To: <ietf@cybernothing.org>, <msk@cloudmark.com>, <gen-art@ietf.org>, <ietf@ietf.org>
Date: Fri, 3 Feb 2012 13:56:39 -0500
Thread-Topic: Gen-ART review of draft-ietf-marf-redaction-08
Thread-Index: AczQCujbMXhqirD5Sk6EB1sS2KVtOQG/Hm+wAudY0sA=
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E05AD13B873@MX14A.corp.emc.com>
References: <7C4DFCE962635144B8FAE8CA11D0BF1E05A7B80D63@MX14A.corp.emc.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05A7CF1028@MX14A.corp.emc.com>
In-Reply-To: <7C4DFCE962635144B8FAE8CA11D0BF1E05A7CF1028@MX14A.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: presnick@qualcomm.com, marf@ietf.org
Subject: [Gen-art] Gen-ART review of draft-ietf-marf-redaction-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: Fri, 03 Feb 2012 18:57:18 -0000

The -08 version is a significant improvement that aligns the draft's
recommendations on mechanisms for redaction and anonymization with the
situation-dependent levels of security that are appropriate for those
purposes.

idnits 2.12.13 didn't find anything.

The -08 version is ready for publication as a Standards Track RFC.

Thanks,
--David


> -----Original Message-----
> From: Black, David
> Sent: Thursday, January 19, 2012 7:10 PM
> To: ietf@cybernothing.org; Murray S. Kucherawy; gen-art@ietf.org; ietf@ie=
tf.org
> Cc: marf@ietf.org; presnick@qualcomm.com; Black, David
> Subject: Gen-ART review of draft-ietf-marf-redaction-05
>=20
> Based on discussion with the authors, the -05 version of this draft resol=
ves the
> issues raised in the Gen-ART review of the -04 version.  An important ele=
ment of
> the approach taken to issue [1] has been to explain why the security requ=
irements
> for redaction are significantly weaker than the strength of the secure ha=
shes
> that are suggested by the draft.
>=20
> Thanks,
> --David
>=20
> > -----Original Message-----
> > From: Black, David
> > Sent: Tuesday, January 10, 2012 9:44 PM
> > To: ietf@cybernothing.org; Murray S. Kucherawy; gen-art@ietf.org; ietf@=
ietf.org
> > Cc: Black, David; marf@ietf.org; presnick@qualcomm.com
> > Subject: Gen-ART review of draft-ietf-marf-redaction-04
> >
> > I am the assigned Gen-ART reviewer for this draft. For background on Ge=
n-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 y=
ou may receive.
> >
> > Document: draft-ietf-marf-redaction-04
> > Reviewer: David L. Black
> > Review Date: January 10, 2012
> > IETF LC End Date: January 18, 2011
> > IESG Telechat Date: January 19, 2011
> >
> > Summary: This draft is on the right track but has open issues, describe=
d in the review.
> >
> > This draft specifies a method for redacting information from email abus=
e reports
> > (e.g., hiding the local part [user] of an email address), while still a=
llowing
> > correlation of the redacted information across related abuse reports fr=
om the same
> > source. The draft is short, clear, and well written.
> >
> > There are two open issues:
> >
> > [1] The first open issue is the absence of security guidance to ensure =
that this
> > redaction technique effectively hides the redacted information.  The re=
daction
> > technique is to concatenate a secret string (called the "redaction key"=
) to the
> > information to be redacted, apply "any hashing/digest algorithm", conve=
rt the output
> > to base64 and use that base64 string to replace the redacted informatio=
n.
> >
> > There are two important ways in which this technique could fail to effe=
ctively hide
> > the redacted information:
> > 	- The secret string may inject insufficient entropy.
> > 	- The hashing/digest algorithm may be weak.
> >
> > To take an extreme example, if the secret string ("redaction key") cons=
ists of a
> > single ASCII character, and a short email local part is being redacted,=
 then the
> > output is highly vulnerable to dictionary and brute force attacks becau=
se only 6 bits
> > of entropy are added (the result may look secure, but it's not).  Beyon=
d this extreme
> > example, this is a potentially real concern - e.g., applying the rule o=
f thumb that
> > ASCII text contains 4-5 bits of entropy per character, the example in A=
ppendix A
> > uses a "redaction key" of "potatoes" that injects at most 40 bits of en=
tropy -
> > is that sufficient for email redaction purposes?
> >
> > To take a silly example, if a CRC is used as the hash with that sort of=
 short input,
> > the result is not particularly difficult to invert.
> >
> > I suggest a couple of changes:
> > 1) Change "any hashing/digest algorithm" to require use of a secure has=
h, and
> > 	explain what is meant by "secure hash" in the security considerations =
section.
> > 2) Require a minimum length of the "redaction key" string, and strongly=
 suggest
> > 	(SHOULD) that it be randomly generated (e.g., by running sufficient ou=
tput
> > 	of an entropy-rich random number generator through a base64 converter)=
.
> >
> > For the latter change, figure out the amount of entropy that should be =
used
> > for redaction - the recommended string length will be larger because pr=
intable
> > ASCII is not entropy-dense (at best it's good for 6 bits of entropy in =
each
> > 8-bit character, and human-written text such as this message has signif=
icantly
> > less).
> >
> > From a pure security perspective, use of HMAC with specified secure has=
hes
> > (SHA2-family) and an approach of hashing the "redaction key" down to a =
binary
> > key for HMAC would be a stronger approach. I suggest that authors consi=
der
> > approach, but  there may be practical usage concerns that suggest not a=
dopting it.
> >
> > [2] The second open issue is absence of security considerations for the=
 redaction
> > key.  The security considerations section needs to caution that the red=
action key
> > is a secret key that must be managed and protected as a secret key.  Di=
sclosure
> > of a redaction key removes the redaction from all reports that used tha=
t key.
> > As part of this, guidance should be provided on when and how to change =
the
> > redaction key in order to limit the effects of loss of secrecy for a si=
ngle
> > redaction key.
> >
> > Editorial Nit: I believe that "anonymization" is a better description o=
f what
> > this draft is doing (as opposed to "redaction"), particularly as the re=
sult is
> > intended to be correlatable via string match across reports from the sa=
me source.
> >
> > idnits 2.12.13 didn't find any nits.
> >
> > 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=
-7786
> > david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> > ----------------------------------------------------


From Francis.Dupont@fdupont.fr  Mon Feb  6 07:05:09 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 66AAB21F86B0 for <gen-art@ietfa.amsl.com>; Mon,  6 Feb 2012 07:05:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.578
X-Spam-Level: 
X-Spam-Status: No, score=-2.578 tagged_above=-999 required=5 tests=[AWL=0.021,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ELaYgid7nbpP for <gen-art@ietfa.amsl.com>; Mon,  6 Feb 2012 07:05:08 -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 5C4F721F863C for <gen-art@ietf.org>; Mon,  6 Feb 2012 07:05:08 -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 q16F55wY093298; Mon, 6 Feb 2012 16:05:05 +0100 (CET) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201202061505.q16F55wY093298@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: gen-art@ietf.org
Date: Mon, 06 Feb 2012 16:05:05 +0100
Sender: Francis.Dupont@fdupont.fr
Cc: draft-ietf-dnsext-xnamercode.all@tools.ietf.org
Subject: [Gen-art] review of draft-ietf-dnsext-xnamercode-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: Mon, 06 Feb 2012 15:05:09 -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-dnsext-xnamercode-00.txt
Reviewer: Francis Dupont
Review Date: 20120202
IETF LC End Date: 20120206
IESG Telechat date: unknown

Summary: Ready

Major issues: None

Minor issues: None

Nits/editorial comments:
 - no Acknowledgments?

 - Author's Address page 8: please add the country (USA) in the postal address

 - Change History page 8 (BTW will be removed by the RFC Editor :-):
  opion -> option

Thanks

Francis.Dupont@fdupont.fr

From ben@nostrum.com  Mon Feb  6 15:17:25 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 36CEB21F85EA; Mon,  6 Feb 2012 15:17:25 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yWtJ+D2eOKg2; Mon,  6 Feb 2012 15:17:24 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 51A8121F8582; Mon,  6 Feb 2012 15:17:24 -0800 (PST)
Received: from dn3-53.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q16NHN9L014007 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 6 Feb 2012 17:17:23 -0600 (CST) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Date: Mon, 6 Feb 2012 17:17:22 -0600
Message-Id: <A57C4722-5E13-451E-ACB4-CAA8064FA68B@nostrum.com>
To: draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1257)
X-Mailer: Apple Mail (2.1257)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>
Subject: [Gen-art] Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-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: Mon, 06 Feb 2012 23:17: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 resolve these comments along with any other Last Call comments =
you may receive.

Document: draft-ietf-dhc-forcerenew-nonce-03
Reviewer: Ben Campbell
Review Date: 2012-02-06
IETF LC End Date: 2012-02-06

Summary:This draft is not quite ready for publication as a proposed =
standard. There are some potentially significant issues that should be =
addressed first.

[Note: Hopefully this draft has had or will have a SecDir review, since =
it seems ripe for significant security implications.]


*** Major issues:

-- I admit to not being a DHCP expert, but If I understand this draft =
correctly, it proposes to send what is effectively a secret-key in a =
DHCPACK request, then use that key to authenticate a force renew =
message. It seems like any eavesdropper could sniff that key, and use it =
to spoof force renew requests. The introduction mentions that there may =
be some environments where the use of RFC3118 authentication could be =
relaxed, and offers an example of such an environment. But nowhere does =
this draft appear to be limited in scope to such environments.=20

I think some additional text in (perhaps in the security considerations) =
is needed to explain either why the vulnerability to eavesdroppers is =
either okay in general, or limits the mechanism's use to environment =
where it is okay. It also seems like that, in the best case, this =
mechanism proves only that a Forcerenew request comes from the same DHCP =
server as in the original transaction, but otherwise does not prove =
anything about the identity of that server. If so, it would be worth =
mentioning it.

-- The mechanism appears to be limited to HMAC-MD5, and there does not =
appear to be any way of selecting other algorithms. Is HMAC-MD5 really =
sufficient as the only choice? Is there some expectation that stronger =
mechanisms or algorithm extensibility would be too expensive? (Perhaps =
the extensibility method would be to specify another mechanism that's =
identical except for a different HMAC algorithm. But if that's the =
intent it should be mentioned.)

*** Minor issues:

-- Section 1 "=20
In such environments the mandatory coupling between FORCERENEW and DHCP =
Authentication [RFC3118] can be relaxed."

It's not clear to me what connection that assertion has with this draft. =
Is there an intent that the proposed mechanisms be used only in such =
environments? I don't find any language scoping this proposal to any =
particular environment.

-- section 3:

Does this draft update either 3203 or 3118? If so, please state that =
explicitly in the abstract, introduction, and draft headers. (I think it =
must at least update 3203, since that draft requires the use of 3118, =
and this draft relaxes that.)

-- section 3.1, last paragraph: "...only if the client and server are =
not using any other authentication..."

That seems to conflict with the statement in section 3 that this =
mechanism is only used if RFC3118 is not used. That is, it's not a =
choice between this mechanism or any other mechanism, it's a choice =
between this mechanism or 3118.

-- section 3.1.3, 2nd paragraph: "The server SHOULD NOT include this =
option unless the client has indicated its capability in a DHCP =
Discovery message."

Why not; what harm would it do? And on the other hand, if you want to =
discourage it, why not go all the way to "MUST NOT"?

-- section 3.1.3, 5th paragraph: "...  computes an HMAC-MD5 of the =
Forcerenew message using the Forcerenew nonce =85"

Using it how? Is it the secret key for the HMAC calculation? (If so, why =
aren't we calling it a "key" in the first place?)

-- section 3.1.4, 1st paragraph: "DHCP servers that support Forcerenew =
nonce Protocol authentication MUST include the DHCP Forcerenew Nonce =
protocol authentication option=85"

Only if the client advertised it, right? Otherwise, this seems to =
conflict with the previous SHOULD NOT.

-- section 3.1.4, 4th paragraph: "=85 =20
the client computes an HMAC-MD5 over the DHCP Forcerenew message, using =
the Forcerenew Nonce =85"

Using it how?

-- section 6:

You mention this mechanism is vulnerable to MiTM attacks. Why is this =
okay? Are there some environments where it is good enough and others =
where it is not? (Also, do they really need to be MitM attackers? Seems =
like any eavesdropper could learn the nonce.)

*** Nits/editorial comments:

-- Abstract, second sentence:

I have trouble parsing this sentence. Are the propositions correct?

-- Section 3.1.1,4th paragraph: "=85 configured to require =85"

Do you mean configured to "require", or configured to "use"? I would =
normally take "requires" to mean that the server would not work with =
clients that don't advertise support for the mechanism.

-- section 3.1.1, message flow diagram:

It would be helpful if you could avoid widowing the top of the diagram. =
One has to keep flipping back to see the labels.

-- section 3.1.3, 5th paragraph:=20

Please expand "RDM"

-- section 3.1.4, first paragraph: "The client MUST=85"

A client that supports this mechanism MUST=85

-- section 3.1.4, 2nd and third paragraph, 1st sentence of each:

I'm confused by this sentence of each paragraph. Are they intended as =
conditionals for the rest of the respective paragraph?







From ben@nostrum.com  Mon Feb  6 15:27:45 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 9709711E80AE; Mon,  6 Feb 2012 15:27:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.197
X-Spam-Level: 
X-Spam-Status: No, score=-102.197 tagged_above=-999 required=5 tests=[AWL=-0.197, BAYES_00=-2.599, J_CHICKENPOX_74=0.6, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UmgCUjlJ+dbI; Mon,  6 Feb 2012 15:27:45 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id BF27621F84C9; Mon,  6 Feb 2012 15:27:44 -0800 (PST)
Received: from dn3-53.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q16NRds6015436 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 6 Feb 2012 17:27:44 -0600 (CST) (envelope-from ben@nostrum.com)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=windows-1252
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <A57C4722-5E13-451E-ACB4-CAA8064FA68B@nostrum.com>
Date: Mon, 6 Feb 2012 17:27:39 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <7492D649-454D-45CB-8983-4A6C385D13E2@nostrum.com>
References: <A57C4722-5E13-451E-ACB4-CAA8064FA68B@nostrum.com>
To: draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org
X-Mailer: Apple Mail (2.1257)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-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: Mon, 06 Feb 2012 23:27:45 -0000

Additionally, the I got a failed delivery notice (User Unknow) for David =
Miles's address.

On Feb 6, 2012, at 5:17 PM, Ben Campbell 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
> Please resolve these comments along with any other Last Call comments =
you may receive.
>=20
> Document: draft-ietf-dhc-forcerenew-nonce-03
> Reviewer: Ben Campbell
> Review Date: 2012-02-06
> IETF LC End Date: 2012-02-06
>=20
> Summary:This draft is not quite ready for publication as a proposed =
standard. There are some potentially significant issues that should be =
addressed first.
>=20
> [Note: Hopefully this draft has had or will have a SecDir review, =
since it seems ripe for significant security implications.]
>=20
>=20
> *** Major issues:
>=20
> -- I admit to not being a DHCP expert, but If I understand this draft =
correctly, it proposes to send what is effectively a secret-key in a =
DHCPACK request, then use that key to authenticate a force renew =
message. It seems like any eavesdropper could sniff that key, and use it =
to spoof force renew requests. The introduction mentions that there may =
be some environments where the use of RFC3118 authentication could be =
relaxed, and offers an example of such an environment. But nowhere does =
this draft appear to be limited in scope to such environments.=20
>=20
> I think some additional text in (perhaps in the security =
considerations) is needed to explain either why the vulnerability to =
eavesdroppers is either okay in general, or limits the mechanism's use =
to environment where it is okay. It also seems like that, in the best =
case, this mechanism proves only that a Forcerenew request comes from =
the same DHCP server as in the original transaction, but otherwise does =
not prove anything about the identity of that server. If so, it would be =
worth mentioning it.
>=20
> -- The mechanism appears to be limited to HMAC-MD5, and there does not =
appear to be any way of selecting other algorithms. Is HMAC-MD5 really =
sufficient as the only choice? Is there some expectation that stronger =
mechanisms or algorithm extensibility would be too expensive? (Perhaps =
the extensibility method would be to specify another mechanism that's =
identical except for a different HMAC algorithm. But if that's the =
intent it should be mentioned.)
>=20
> *** Minor issues:
>=20
> -- Section 1 "=20
> In such environments the mandatory coupling between FORCERENEW and =
DHCP Authentication [RFC3118] can be relaxed."
>=20
> It's not clear to me what connection that assertion has with this =
draft. Is there an intent that the proposed mechanisms be used only in =
such environments? I don't find any language scoping this proposal to =
any particular environment.
>=20
> -- section 3:
>=20
> Does this draft update either 3203 or 3118? If so, please state that =
explicitly in the abstract, introduction, and draft headers. (I think it =
must at least update 3203, since that draft requires the use of 3118, =
and this draft relaxes that.)
>=20
> -- section 3.1, last paragraph: "...only if the client and server are =
not using any other authentication..."
>=20
> That seems to conflict with the statement in section 3 that this =
mechanism is only used if RFC3118 is not used. That is, it's not a =
choice between this mechanism or any other mechanism, it's a choice =
between this mechanism or 3118.
>=20
> -- section 3.1.3, 2nd paragraph: "The server SHOULD NOT include this =
option unless the client has indicated its capability in a DHCP =
Discovery message."
>=20
> Why not; what harm would it do? And on the other hand, if you want to =
discourage it, why not go all the way to "MUST NOT"?
>=20
> -- section 3.1.3, 5th paragraph: "...  computes an HMAC-MD5 of the =
Forcerenew message using the Forcerenew nonce =85"
>=20
> Using it how? Is it the secret key for the HMAC calculation? (If so, =
why aren't we calling it a "key" in the first place?)
>=20
> -- section 3.1.4, 1st paragraph: "DHCP servers that support Forcerenew =
nonce Protocol authentication MUST include the DHCP Forcerenew Nonce =
protocol authentication option=85"
>=20
> Only if the client advertised it, right? Otherwise, this seems to =
conflict with the previous SHOULD NOT.
>=20
> -- section 3.1.4, 4th paragraph: "=85 =20
> the client computes an HMAC-MD5 over the DHCP Forcerenew message, =
using the Forcerenew Nonce =85"
>=20
> Using it how?
>=20
> -- section 6:
>=20
> You mention this mechanism is vulnerable to MiTM attacks. Why is this =
okay? Are there some environments where it is good enough and others =
where it is not? (Also, do they really need to be MitM attackers? Seems =
like any eavesdropper could learn the nonce.)
>=20
> *** Nits/editorial comments:
>=20
> -- Abstract, second sentence:
>=20
> I have trouble parsing this sentence. Are the propositions correct?
>=20
> -- Section 3.1.1,4th paragraph: "=85 configured to require =85"
>=20
> Do you mean configured to "require", or configured to "use"? I would =
normally take "requires" to mean that the server would not work with =
clients that don't advertise support for the mechanism.
>=20
> -- section 3.1.1, message flow diagram:
>=20
> It would be helpful if you could avoid widowing the top of the =
diagram. One has to keep flipping back to see the labels.
>=20
> -- section 3.1.3, 5th paragraph:=20
>=20
> Please expand "RDM"
>=20
> -- section 3.1.4, first paragraph: "The client MUST=85"
>=20
> A client that supports this mechanism MUST=85
>=20
> -- section 3.1.4, 2nd and third paragraph, 1st sentence of each:
>=20
> I'm confused by this sentence of each paragraph. Are they intended as =
conditionals for the rest of the respective paragraph?
>=20
>=20
>=20
>=20
>=20
>=20


From elwynd@dial.pipex.com  Wed Feb  8 02:56:44 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 6391921F86E4 for <gen-art@ietfa.amsl.com>; Wed,  8 Feb 2012 02:56:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.697
X-Spam-Level: 
X-Spam-Status: No, score=-1.697 tagged_above=-999 required=5 tests=[AWL=0.902,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RQ0JjvCWsB99 for <gen-art@ietfa.amsl.com>; Wed,  8 Feb 2012 02:56:44 -0800 (PST)
Received: from a.painless.aaisp.net.uk (auth.a.painless.aaisp.net.uk [IPv6:2001:8b0:0:30:230:48ff:fe72:d05c]) by ietfa.amsl.com (Postfix) with ESMTP id A4CD821F86CF for <gen-art@ietf.org>; Wed,  8 Feb 2012 02:56:17 -0800 (PST)
Received: from 250.254.187.81.in-addr.arpa ([81.187.254.250]) by a.painless.aaisp.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <elwynd@dial.pipex.com>) id 1Rv5C7-0000Lr-M9; Wed, 08 Feb 2012 10:56:11 +0000
From: Elwyn Davies <elwynd@dial.pipex.com>
To: Qin Wu <bill.wu@huawei.com>
In-Reply-To: <BB94D1B3E4CD4E1BA7107AF5A99D19BE@china.huawei.com>
References: <1328187998.4790.2946.camel@mightyatom.folly.org.uk> <BB94D1B3E4CD4E1BA7107AF5A99D19BE@china.huawei.com>
Content-Type: text/plain
Date: Wed, 08 Feb 2012 10:58:50 +0000
Message-Id: <1328698730.4345.364.camel@mightyatom.folly.org.uk>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-dime-pmip6-lr.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art review of draft-ietf-dime-pmip6-lr-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: Wed, 08 Feb 2012 10:56:44 -0000

Hi, Qin.

Thanks for your quick reponse.. some comments in line (I have deleted
the bits agreed),

/Elwyn

On Fri, 2012-02-03 at 12:53 +0800, Qin Wu wrote:
> Hi,Elwyn:
> Thank for your valuable review. please see our replies below.
> ----- Original Message ----- 
> From: "Elwyn Davies" <davieseb@scss.tcd.ie>
> To: "General Area Review Team" <gen-art@ietf.org>
> Cc: <draft-ietf-dime-pmip6-lr.all@tools.ietf.org>
> Sent: Thursday, February 02, 2012 9:06 PM
> Subject: Gen-art review of draft-ietf-dime-pmip6-lr-07
> 
> 
> >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-dime-pmip6-lr-07.txt
> > Reviewer: Elwyn Davies
> > Review Date: 2 February 2012
> > IETF LC End Date: 24 January 2012
> > IESG Telechat date: 16 February 2012
> > 
> > Summary:
> > I have a couple of queries/minor issues regarding checking whether LMA1
> > and LMA2 are the same node and some hand waving over the idea of
> > 'localized routing setup/signaliing'.  There are also a few minor nits.
> > Otherwise this is ready for the IESG.
> > 
> > [This document missed the normal gen-art last call allocation
> > notification mechanism for some reason - so I didn't realize it was on
> > my allocation till the end of last call and as a result the review is a
> > bit late.]
> > 
> > Major issues:
> > None
> > 
> > Minor issues:
> > s5.1, para 3 and s5.2, last para:
> > In s5.1:
> >> MAG1 can verify
> >>    whether both MAGs are under the same LMA by comparing the addresses
> >>    of LMA1 and LMA2.
> > Is this guaranteed to work?  Should we care? Or is this just too bad if
> > the LMA has multiple addresses and the two MNs have different ideas?
> 
> [Qin]: In the example described in the s5.1, we don't consider one LMA has two LMA address.
> LMA1 and LMA2 may represent two different mobility entities identified by LMA1 adress and LMA2 adress respectively.
> If LMA1 address is LMA2 address, this just indicate LMA1 and LMA2 are the same mobility entity.
> Even one LMA have more than one LMA address, this still work since MAG can know if these LMA addresses come from
> the same mobility entity based on MN1 and MN2's binding update list.
> 
> > However in s5.2:
> >> In the case where MNs share the same LMA, LR should be initiated by
> >>    LMA1 (i.e.,LMA2) since only LMA1 knows that both MN1 and MN2 belong
> >>    to itself by looking up the binding cache entries corresponding to
> >>    MN1 and MN2. 
> > I am unsure whether these two statements are talking about the same
> > thing - and, if so, are they contradictory?
> > 
> 
> [Qin]: No Confliction, See above.

I think this is exactly the point: You give two different (but allegedly
non-conflicting ways) of doing the same thing at two places in the
draft.  From what you say, I infer that you could do either thing in
both cases. If so then it would be better to give the alternatives
together for the first case and refer to the previous comments when the
second case is reached in the text.


> 
> > s5.1, last para:
> >> Figure 4 shows another example scenario, similar to the example
> >>    scenario illustrated in Figure 3, LMA1 does not respond to MAG1 with
> >>    the address of LMA2, instead setting up a localized routing path
> >>    directly between itself and LMA2 via localized routing signaling.
> > I am unsure what 'localized routing signaliing' would involve.  What
> > would the nodes do for this?  Appears to involve some waving of hands.
> 
> [Qin]: LMA1 and LMA2 exchange to trigger corresponding LMA to setup binding entries
> on the correspoding MAG for localized routing and establish localized
> routing path between MAG1 and MAG2.
> 
> > On a slightly broader point, there are a number of places where the
> > phrase 'localized routing setup' (or similar) is used.  It would, I
> > think, be useful to add a few words indicating what is thought to be
> > involved although actually doing it is clearly out of scope of this
> > document.
> 
> [Qin]: Okay.

I am afraid this doesn't really help: You say 'establish localized
routing path between MAG1 and MAG2'. How? Does this imply that the MAG
or some other component will (re-)configure the local packet routing
infrastructure? (Not something I would expect the MAG to be authorized
to do.) Or is this a matter of creating a tunnel?  I think this needs to
be a whole lot more concrete - both ends have to be expecting the
packets and know what to do with them.

Regards,
Elwyn  



From bill.wu@huawei.com  Wed Feb  8 03:49:43 2012
Return-Path: <bill.wu@huawei.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 F28A821F859E for <gen-art@ietfa.amsl.com>; Wed,  8 Feb 2012 03:49:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.881
X-Spam-Level: 
X-Spam-Status: No, score=-5.881 tagged_above=-999 required=5 tests=[AWL=0.718,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x7q576MLqMGz for <gen-art@ietfa.amsl.com>; Wed,  8 Feb 2012 03:49:42 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id A65F521F85A7 for <gen-art@ietf.org>; Wed,  8 Feb 2012 03:49:41 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LZ2005Y9ORBBY@szxga03-in.huawei.com> for gen-art@ietf.org; Wed, 08 Feb 2012 19:47:35 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LZ200CTMOR8GD@szxga03-in.huawei.com> for gen-art@ietf.org; Wed, 08 Feb 2012 19:47:35 +0800 (CST)
Received: from szxeml211-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AGY48202; Wed, 08 Feb 2012 19:47:34 +0800
Received: from SZXEML416-HUB.china.huawei.com (10.82.67.155) by szxeml211-edg.china.huawei.com (172.24.2.182) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 08 Feb 2012 19:46:53 +0800
Received: from w53375q (10.138.41.130) by szxeml416-hub.china.huawei.com (10.82.67.155) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 08 Feb 2012 19:47:27 +0800
Date: Wed, 08 Feb 2012 19:47:26 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: Elwyn Davies <elwynd@dial.pipex.com>
Message-id: <BF80F6B7104742079DDF846CD4863A4D@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <1328187998.4790.2946.camel@mightyatom.folly.org.uk> <BB94D1B3E4CD4E1BA7107AF5A99D19BE@china.huawei.com> <1328698730.4345.364.camel@mightyatom.folly.org.uk>
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-dime-pmip6-lr.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art review of draft-ietf-dime-pmip6-lr-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: Wed, 08 Feb 2012 11:49:43 -0000

Hi, Elwyn:
Thank for your followup comments, please see my replies inline.

Regards!
-Qin
----- Original Message ----- 
From: "Elwyn Davies" <elwynd@dial.pipex.com>
To: "Qin Wu" <bill.wu@huawei.com>
Cc: "General Area Review Team" <gen-art@ietf.org>; <draft-ietf-dime-pmip6-lr.all@tools.ietf.org>
Sent: Wednesday, February 08, 2012 6:58 PM
Subject: Re: [Gen-art] Gen-art review of draft-ietf-dime-pmip6-lr-07


> Hi, Qin.
> 
> Thanks for your quick reponse.. some comments in line (I have deleted
> the bits agreed),
> 
> /Elwyn
> 
> On Fri, 2012-02-03 at 12:53 +0800, Qin Wu wrote:
>> Hi,Elwyn:
>> Thank for your valuable review. please see our replies below.
>> ----- Original Message ----- 
>> From: "Elwyn Davies" <davieseb@scss.tcd.ie>
>> To: "General Area Review Team" <gen-art@ietf.org>
>> Cc: <draft-ietf-dime-pmip6-lr.all@tools.ietf.org>
>> Sent: Thursday, February 02, 2012 9:06 PM
>> Subject: Gen-art review of draft-ietf-dime-pmip6-lr-07
>> 
>> 
>> >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-dime-pmip6-lr-07.txt
>> > Reviewer: Elwyn Davies
>> > Review Date: 2 February 2012
>> > IETF LC End Date: 24 January 2012
>> > IESG Telechat date: 16 February 2012
>> > 
>> > Summary:
>> > I have a couple of queries/minor issues regarding checking whether LMA1
>> > and LMA2 are the same node and some hand waving over the idea of
>> > 'localized routing setup/signaliing'.  There are also a few minor nits.
>> > Otherwise this is ready for the IESG.
>> > 
>> > [This document missed the normal gen-art last call allocation
>> > notification mechanism for some reason - so I didn't realize it was on
>> > my allocation till the end of last call and as a result the review is a
>> > bit late.]
>> > 
>> > Major issues:
>> > None
>> > 
>> > Minor issues:
>> > s5.1, para 3 and s5.2, last para:
>> > In s5.1:
>> >> MAG1 can verify
>> >>    whether both MAGs are under the same LMA by comparing the addresses
>> >>    of LMA1 and LMA2.
>> > Is this guaranteed to work?  Should we care? Or is this just too bad if
>> > the LMA has multiple addresses and the two MNs have different ideas?
>> 
>> [Qin]: In the example described in the s5.1, we don't consider one LMA has two LMA address.
>> LMA1 and LMA2 may represent two different mobility entities identified by LMA1 adress and LMA2 adress respectively.
>> If LMA1 address is LMA2 address, this just indicate LMA1 and LMA2 are the same mobility entity.
>> Even one LMA have more than one LMA address, this still work since MAG can know if these LMA addresses come from
>> the same mobility entity based on MN1 and MN2's binding update list.
>> 
>> > However in s5.2:
>> >> In the case where MNs share the same LMA, LR should be initiated by
>> >>    LMA1 (i.e.,LMA2) since only LMA1 knows that both MN1 and MN2 belong
>> >>    to itself by looking up the binding cache entries corresponding to
>> >>    MN1 and MN2. 
>> > I am unsure whether these two statements are talking about the same
>> > thing - and, if so, are they contradictory?
>> > 
>> 
>> [Qin]: No Confliction, See above.
> 
> I think this is exactly the point: You give two different (but allegedly
> non-conflicting ways) of doing the same thing at two places in the
> draft.  From what you say, I infer that you could do either thing in
> both cases. If so then it would be better to give the alternatives
> together for the first case and refer to the previous comments when the
> second case is reached in the text.

[Qin]: Good suggestion and will follow this.
> 
>> 
>> > s5.1, last para:
>> >> Figure 4 shows another example scenario, similar to the example
>> >>    scenario illustrated in Figure 3, LMA1 does not respond to MAG1 with
>> >>    the address of LMA2, instead setting up a localized routing path
>> >>    directly between itself and LMA2 via localized routing signaling.
>> > I am unsure what 'localized routing signaliing' would involve.  What
>> > would the nodes do for this?  Appears to involve some waving of hands.
>> 
>> [Qin]: LMA1 and LMA2 exchange to trigger corresponding LMA to setup binding entries
>> on the correspoding MAG for localized routing and establish localized
>> routing path between MAG1 and MAG2.
>> 
>> > On a slightly broader point, there are a number of places where the
>> > phrase 'localized routing setup' (or similar) is used.  It would, I
>> > think, be useful to add a few words indicating what is thought to be
>> > involved although actually doing it is clearly out of scope of this
>> > document.
>> 
>> [Qin]: Okay.
> 
> I am afraid this doesn't really help: You say 'establish localized
> routing path between MAG1 and MAG2'. How? Does this imply that the MAG
> or some other component will (re-)configure the local packet routing
> infrastructure? (Not something I would expect the MAG to be authorized
> to do.) Or is this a matter of creating a tunnel?  I think this needs to
> be a whole lot more concrete - both ends have to be expecting the
> packets and know what to do with them.

[Qin]: Yes, your are right. Tunneling between MAG1 and MAG2 should be configured on both MAGs.
As default static behavior,tunnel between MAG1 and MAG2 uses the same encapsulation mechanism
as that being used for PMIP tunnel between MAG and LMA. In this case, MAG1 and MAG2
can start using the same tunneling mechanism without special configuration (e.g.using other 
tunnel mechanism that is uniform in the PMIP domain) on MAGs or dynamic tunneling negotiation between MAGs.
but special configuration on MAGs or dynamic tunnel negotiation can overide 
the default static behavior mentioned above if they are really needed.

Hope this clarifies.

> Regards,
> Elwyn  
> 
>

From elwynd@dial.pipex.com  Wed Feb  8 04:25:53 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 E5CC421F859E for <gen-art@ietfa.amsl.com>; Wed,  8 Feb 2012 04:25:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.996
X-Spam-Level: 
X-Spam-Status: No, score=-100.996 tagged_above=-999 required=5 tests=[AWL=-0.551, BAYES_00=-2.599, FRT_BELOW2=2.154, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3VPazAn4IOVG for <gen-art@ietfa.amsl.com>; Wed,  8 Feb 2012 04:25:53 -0800 (PST)
Received: from a.painless.aaisp.net.uk (auth.a.painless.aaisp.net.uk [IPv6:2001:8b0:0:30:230:48ff:fe72:d05c]) by ietfa.amsl.com (Postfix) with ESMTP id B650521F8597 for <gen-art@ietf.org>; Wed,  8 Feb 2012 04:25:52 -0800 (PST)
Received: from 250.254.187.81.in-addr.arpa ([81.187.254.250]) by a.painless.aaisp.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <elwynd@dial.pipex.com>) id 1Rv6ao-0006IE-4L; Wed, 08 Feb 2012 12:25:46 +0000
From: Elwyn Davies <elwynd@dial.pipex.com>
To: Qin Wu <bill.wu@huawei.com>
In-Reply-To: <BF80F6B7104742079DDF846CD4863A4D@china.huawei.com>
References: <1328187998.4790.2946.camel@mightyatom.folly.org.uk> <BB94D1B3E4CD4E1BA7107AF5A99D19BE@china.huawei.com> <1328698730.4345.364.camel@mightyatom.folly.org.uk> <BF80F6B7104742079DDF846CD4863A4D@china.huawei.com>
Content-Type: text/plain
Date: Wed, 08 Feb 2012 12:28:26 +0000
Message-Id: <1328704106.4345.410.camel@mightyatom.folly.org.uk>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-dime-pmip6-lr.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art review of draft-ietf-dime-pmip6-lr-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: Wed, 08 Feb 2012 12:25:54 -0000

Hi, Qin.

Fine - I think all will be good from my point of view if you say a few
words about linking the MAGs as per your last response belwow.

Cheers,
Elwyn

On Wed, 2012-02-08 at 19:47 +0800, Qin Wu wrote:
> Hi, Elwyn:
> Thank for your followup comments, please see my replies inline.
> 
> Regards!
> -Qin
> ----- Original Message ----- 
> From: "Elwyn Davies" <elwynd@dial.pipex.com>
> To: "Qin Wu" <bill.wu@huawei.com>
> Cc: "General Area Review Team" <gen-art@ietf.org>; <draft-ietf-dime-pmip6-lr.all@tools.ietf.org>
> Sent: Wednesday, February 08, 2012 6:58 PM
> Subject: Re: [Gen-art] Gen-art review of draft-ietf-dime-pmip6-lr-07
> 
> 
> > Hi, Qin.
> > 
> > Thanks for your quick reponse.. some comments in line (I have deleted
> > the bits agreed),
> > 
> > /Elwyn
> > 
> > On Fri, 2012-02-03 at 12:53 +0800, Qin Wu wrote:
> >> Hi,Elwyn:
> >> Thank for your valuable review. please see our replies below.
> >> ----- Original Message ----- 
> >> From: "Elwyn Davies" <davieseb@scss.tcd.ie>
> >> To: "General Area Review Team" <gen-art@ietf.org>
> >> Cc: <draft-ietf-dime-pmip6-lr.all@tools.ietf.org>
> >> Sent: Thursday, February 02, 2012 9:06 PM
> >> Subject: Gen-art review of draft-ietf-dime-pmip6-lr-07
> >> 
> >> 
> >> >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-dime-pmip6-lr-07.txt
> >> > Reviewer: Elwyn Davies
> >> > Review Date: 2 February 2012
> >> > IETF LC End Date: 24 January 2012
> >> > IESG Telechat date: 16 February 2012
> >> > 
> >> > Summary:
> >> > I have a couple of queries/minor issues regarding checking whether LMA1
> >> > and LMA2 are the same node and some hand waving over the idea of
> >> > 'localized routing setup/signaliing'.  There are also a few minor nits.
> >> > Otherwise this is ready for the IESG.
> >> > 
> >> > [This document missed the normal gen-art last call allocation
> >> > notification mechanism for some reason - so I didn't realize it was on
> >> > my allocation till the end of last call and as a result the review is a
> >> > bit late.]
> >> > 
> >> > Major issues:
> >> > None
> >> > 
> >> > Minor issues:
> >> > s5.1, para 3 and s5.2, last para:
> >> > In s5.1:
> >> >> MAG1 can verify
> >> >>    whether both MAGs are under the same LMA by comparing the addresses
> >> >>    of LMA1 and LMA2.
> >> > Is this guaranteed to work?  Should we care? Or is this just too bad if
> >> > the LMA has multiple addresses and the two MNs have different ideas?
> >> 
> >> [Qin]: In the example described in the s5.1, we don't consider one LMA has two LMA address.
> >> LMA1 and LMA2 may represent two different mobility entities identified by LMA1 adress and LMA2 adress respectively.
> >> If LMA1 address is LMA2 address, this just indicate LMA1 and LMA2 are the same mobility entity.
> >> Even one LMA have more than one LMA address, this still work since MAG can know if these LMA addresses come from
> >> the same mobility entity based on MN1 and MN2's binding update list.
> >> 
> >> > However in s5.2:
> >> >> In the case where MNs share the same LMA, LR should be initiated by
> >> >>    LMA1 (i.e.,LMA2) since only LMA1 knows that both MN1 and MN2 belong
> >> >>    to itself by looking up the binding cache entries corresponding to
> >> >>    MN1 and MN2. 
> >> > I am unsure whether these two statements are talking about the same
> >> > thing - and, if so, are they contradictory?
> >> > 
> >> 
> >> [Qin]: No Confliction, See above.
> > 
> > I think this is exactly the point: You give two different (but allegedly
> > non-conflicting ways) of doing the same thing at two places in the
> > draft.  From what you say, I infer that you could do either thing in
> > both cases. If so then it would be better to give the alternatives
> > together for the first case and refer to the previous comments when the
> > second case is reached in the text.
> 
> [Qin]: Good suggestion and will follow this.
> > 
> >> 
> >> > s5.1, last para:
> >> >> Figure 4 shows another example scenario, similar to the example
> >> >>    scenario illustrated in Figure 3, LMA1 does not respond to MAG1 with
> >> >>    the address of LMA2, instead setting up a localized routing path
> >> >>    directly between itself and LMA2 via localized routing signaling.
> >> > I am unsure what 'localized routing signaliing' would involve.  What
> >> > would the nodes do for this?  Appears to involve some waving of hands.
> >> 
> >> [Qin]: LMA1 and LMA2 exchange to trigger corresponding LMA to setup binding entries
> >> on the correspoding MAG for localized routing and establish localized
> >> routing path between MAG1 and MAG2.
> >> 
> >> > On a slightly broader point, there are a number of places where the
> >> > phrase 'localized routing setup' (or similar) is used.  It would, I
> >> > think, be useful to add a few words indicating what is thought to be
> >> > involved although actually doing it is clearly out of scope of this
> >> > document.
> >> 
> >> [Qin]: Okay.
> > 
> > I am afraid this doesn't really help: You say 'establish localized
> > routing path between MAG1 and MAG2'. How? Does this imply that the MAG
> > or some other component will (re-)configure the local packet routing
> > infrastructure? (Not something I would expect the MAG to be authorized
> > to do.) Or is this a matter of creating a tunnel?  I think this needs to
> > be a whole lot more concrete - both ends have to be expecting the
> > packets and know what to do with them.
> 
> [Qin]: Yes, your are right. Tunneling between MAG1 and MAG2 should be configured on both MAGs.
> As default static behavior,tunnel between MAG1 and MAG2 uses the same encapsulation mechanism
> as that being used for PMIP tunnel between MAG and LMA. In this case, MAG1 and MAG2
> can start using the same tunneling mechanism without special configuration (e.g.using other 
> tunnel mechanism that is uniform in the PMIP domain) on MAGs or dynamic tunneling negotiation between MAGs.
> but special configuration on MAGs or dynamic tunnel negotiation can overide 
> the default static behavior mentioned above if they are really needed.
> 
> Hope this clarifies.
> 
> > Regards,
> > Elwyn  
> > 
> >


From bill.wu@huawei.com  Wed Feb  8 04:58:27 2012
Return-Path: <bill.wu@huawei.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 AEDF621F851D for <gen-art@ietfa.amsl.com>; Wed,  8 Feb 2012 04:58:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.824
X-Spam-Level: 
X-Spam-Status: No, score=-4.824 tagged_above=-999 required=5 tests=[AWL=-0.379, BAYES_00=-2.599, FRT_BELOW2=2.154, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9sGeGrrylyNM for <gen-art@ietfa.amsl.com>; Wed,  8 Feb 2012 04:58:26 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 6497321F84F5 for <gen-art@ietf.org>; Wed,  8 Feb 2012 04:58:26 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LZ200G7TS1D9W@szxga03-in.huawei.com> for gen-art@ietf.org; Wed, 08 Feb 2012 20:58:25 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LZ200253S11HX@szxga03-in.huawei.com> for gen-art@ietf.org; Wed, 08 Feb 2012 20:58:25 +0800 (CST)
Received: from szxeml202-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AGY54543; Wed, 08 Feb 2012 20:58:24 +0800
Received: from SZXEML411-HUB.china.huawei.com (10.82.67.138) by szxeml202-edg.china.huawei.com (172.24.2.42) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 08 Feb 2012 20:58:17 +0800
Received: from w53375q (10.138.41.130) by szxeml411-hub.china.huawei.com (10.82.67.138) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 08 Feb 2012 20:58:16 +0800
Date: Wed, 08 Feb 2012 20:58:14 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: Elwyn Davies <elwynd@dial.pipex.com>
Message-id: <77EDC196D9C541439581B23447002099@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <1328187998.4790.2946.camel@mightyatom.folly.org.uk> <BB94D1B3E4CD4E1BA7107AF5A99D19BE@china.huawei.com> <1328698730.4345.364.camel@mightyatom.folly.org.uk> <BF80F6B7104742079DDF846CD4863A4D@china.huawei.com> <1328704106.4345.410.camel@mightyatom.folly.org.uk>
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-dime-pmip6-lr.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art review of draft-ietf-dime-pmip6-lr-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: Wed, 08 Feb 2012 12:58:27 -0000

Okay, many thanks to your valuable review.

Regards!
-Qin
----- Original Message ----- 
From: "Elwyn Davies" <elwynd@dial.pipex.com>
To: "Qin Wu" <bill.wu@huawei.com>
Cc: "General Area Review Team" <gen-art@ietf.org>; <draft-ietf-dime-pmip6-lr.all@tools.ietf.org>
Sent: Wednesday, February 08, 2012 8:28 PM
Subject: Re: [Gen-art] Gen-art review of draft-ietf-dime-pmip6-lr-07


> Hi, Qin.
> 
> Fine - I think all will be good from my point of view if you say a few
> words about linking the MAGs as per your last response belwow.
> 
> Cheers,
> Elwyn
> 
> On Wed, 2012-02-08 at 19:47 +0800, Qin Wu wrote:
>> Hi, Elwyn:
>> Thank for your followup comments, please see my replies inline.
>> 
>> Regards!
>> -Qin
>> ----- Original Message ----- 
>> From: "Elwyn Davies" <elwynd@dial.pipex.com>
>> To: "Qin Wu" <bill.wu@huawei.com>
>> Cc: "General Area Review Team" <gen-art@ietf.org>; <draft-ietf-dime-pmip6-lr.all@tools.ietf.org>
>> Sent: Wednesday, February 08, 2012 6:58 PM
>> Subject: Re: [Gen-art] Gen-art review of draft-ietf-dime-pmip6-lr-07
>> 
>> 
>> > Hi, Qin.
>> > 
>> > Thanks for your quick reponse.. some comments in line (I have deleted
>> > the bits agreed),
>> > 
>> > /Elwyn
>> > 
>> > On Fri, 2012-02-03 at 12:53 +0800, Qin Wu wrote:
>> >> Hi,Elwyn:
>> >> Thank for your valuable review. please see our replies below.
>> >> ----- Original Message ----- 
>> >> From: "Elwyn Davies" <davieseb@scss.tcd.ie>
>> >> To: "General Area Review Team" <gen-art@ietf.org>
>> >> Cc: <draft-ietf-dime-pmip6-lr.all@tools.ietf.org>
>> >> Sent: Thursday, February 02, 2012 9:06 PM
>> >> Subject: Gen-art review of draft-ietf-dime-pmip6-lr-07
>> >> 
>> >> 
>> >> >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-dime-pmip6-lr-07.txt
>> >> > Reviewer: Elwyn Davies
>> >> > Review Date: 2 February 2012
>> >> > IETF LC End Date: 24 January 2012
>> >> > IESG Telechat date: 16 February 2012
>> >> > 
>> >> > Summary:
>> >> > I have a couple of queries/minor issues regarding checking whether LMA1
>> >> > and LMA2 are the same node and some hand waving over the idea of
>> >> > 'localized routing setup/signaliing'.  There are also a few minor nits.
>> >> > Otherwise this is ready for the IESG.
>> >> > 
>> >> > [This document missed the normal gen-art last call allocation
>> >> > notification mechanism for some reason - so I didn't realize it was on
>> >> > my allocation till the end of last call and as a result the review is a
>> >> > bit late.]
>> >> > 
>> >> > Major issues:
>> >> > None
>> >> > 
>> >> > Minor issues:
>> >> > s5.1, para 3 and s5.2, last para:
>> >> > In s5.1:
>> >> >> MAG1 can verify
>> >> >>    whether both MAGs are under the same LMA by comparing the addresses
>> >> >>    of LMA1 and LMA2.
>> >> > Is this guaranteed to work?  Should we care? Or is this just too bad if
>> >> > the LMA has multiple addresses and the two MNs have different ideas?
>> >> 
>> >> [Qin]: In the example described in the s5.1, we don't consider one LMA has two LMA address.
>> >> LMA1 and LMA2 may represent two different mobility entities identified by LMA1 adress and LMA2 adress respectively.
>> >> If LMA1 address is LMA2 address, this just indicate LMA1 and LMA2 are the same mobility entity.
>> >> Even one LMA have more than one LMA address, this still work since MAG can know if these LMA addresses come from
>> >> the same mobility entity based on MN1 and MN2's binding update list.
>> >> 
>> >> > However in s5.2:
>> >> >> In the case where MNs share the same LMA, LR should be initiated by
>> >> >>    LMA1 (i.e.,LMA2) since only LMA1 knows that both MN1 and MN2 belong
>> >> >>    to itself by looking up the binding cache entries corresponding to
>> >> >>    MN1 and MN2. 
>> >> > I am unsure whether these two statements are talking about the same
>> >> > thing - and, if so, are they contradictory?
>> >> > 
>> >> 
>> >> [Qin]: No Confliction, See above.
>> > 
>> > I think this is exactly the point: You give two different (but allegedly
>> > non-conflicting ways) of doing the same thing at two places in the
>> > draft.  From what you say, I infer that you could do either thing in
>> > both cases. If so then it would be better to give the alternatives
>> > together for the first case and refer to the previous comments when the
>> > second case is reached in the text.
>> 
>> [Qin]: Good suggestion and will follow this.
>> > 
>> >> 
>> >> > s5.1, last para:
>> >> >> Figure 4 shows another example scenario, similar to the example
>> >> >>    scenario illustrated in Figure 3, LMA1 does not respond to MAG1 with
>> >> >>    the address of LMA2, instead setting up a localized routing path
>> >> >>    directly between itself and LMA2 via localized routing signaling.
>> >> > I am unsure what 'localized routing signaliing' would involve.  What
>> >> > would the nodes do for this?  Appears to involve some waving of hands.
>> >> 
>> >> [Qin]: LMA1 and LMA2 exchange to trigger corresponding LMA to setup binding entries
>> >> on the correspoding MAG for localized routing and establish localized
>> >> routing path between MAG1 and MAG2.
>> >> 
>> >> > On a slightly broader point, there are a number of places where the
>> >> > phrase 'localized routing setup' (or similar) is used.  It would, I
>> >> > think, be useful to add a few words indicating what is thought to be
>> >> > involved although actually doing it is clearly out of scope of this
>> >> > document.
>> >> 
>> >> [Qin]: Okay.
>> > 
>> > I am afraid this doesn't really help: You say 'establish localized
>> > routing path between MAG1 and MAG2'. How? Does this imply that the MAG
>> > or some other component will (re-)configure the local packet routing
>> > infrastructure? (Not something I would expect the MAG to be authorized
>> > to do.) Or is this a matter of creating a tunnel?  I think this needs to
>> > be a whole lot more concrete - both ends have to be expecting the
>> > packets and know what to do with them.
>> 
>> [Qin]: Yes, your are right. Tunneling between MAG1 and MAG2 should be configured on both MAGs.
>> As default static behavior,tunnel between MAG1 and MAG2 uses the same encapsulation mechanism
>> as that being used for PMIP tunnel between MAG and LMA. In this case, MAG1 and MAG2
>> can start using the same tunneling mechanism without special configuration (e.g.using other 
>> tunnel mechanism that is uniform in the PMIP domain) on MAGs or dynamic tunneling negotiation between MAGs.
>> but special configuration on MAGs or dynamic tunnel negotiation can overide 
>> the default static behavior mentioned above if they are really needed.
>> 
>> Hope this clarifies.
>> 
>> > Regards,
>> > Elwyn  
>> > 
>> >
>

From stephen.farrell@cs.tcd.ie  Wed Feb  8 08:45:57 2012
Return-Path: <stephen.farrell@cs.tcd.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 28C2721F86DF; Wed,  8 Feb 2012 08:45:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.149
X-Spam-Level: 
X-Spam-Status: No, score=-102.149 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_23=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UWVquEMrRESe; Wed,  8 Feb 2012 08:45:45 -0800 (PST)
Received: from scss.tcd.ie (hermes.cs.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 782DC21F8617; Wed,  8 Feb 2012 08:45:36 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 3BAF1171C91; Wed,  8 Feb 2012 16:45:35 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1328719534; bh=Y0XiOc+1BGwLBw ZiB8o668Mh2d+oAcGhlOwsYxlASZg=; b=3p2bis5GWtmIdlDpjH6HNf+2VohCAk shEZWugiOHRyxHphc3SsXQaZi517913ADxb0x8WrEFDcacSm/altEWUprI549Dss memS21SuuuuQcG6Rl76LeCh0El1xHpnrLkxTbO5afPg6OQyPkC75tlbOLyW1fcPK qYPQnUfehR9ihrh/h+g2ivabdkM7FtaekY9WkN3e+70pxG36Z9v2cCcMT5r9pq4W TaL5/pCOfcbEsnE+2ZGqBp2wRB49GScHJOJ6It1COkW6biB/uzmqEuGgcjn2/7zG shIC8aco89YMUDsJtAiOIoX1rfY6z2+PYtc3SyJtdH0gEitYaNA1PYfA==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id 3Y5WgGqKNBZY; Wed,  8 Feb 2012 16:45:34 +0000 (GMT)
Received: from [134.226.36.180] (stephen-think.dsg.cs.tcd.ie [134.226.36.180]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 5E092171C2F; Wed,  8 Feb 2012 16:45:27 +0000 (GMT)
Message-ID: <4F32A6A8.3010502@cs.tcd.ie>
Date: Wed, 08 Feb 2012 16:45:28 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
References: <4F2AA2F8.4010004@ericsson.com> <4F2AA5E2.2040106@cs.tcd.ie> <20857042-B4A9-4861-8AC2-5E7324DFEE16@huawei.com> <4F325F78.5070701@cs.tcd.ie> <E97BCF9E7A34470B9143D2F62222294A@china.huawei.com> <4F32802B.8090007@ericsson.com>
In-Reply-To: <4F32802B.8090007@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: General Area Review Team <gen-art@ietf.org>, Qin Wu <bill.wu@huawei.com>, "hokey@ietf.org" <hokey@ietf.org>, Tina TSOU <Tina.Tsou.Zouting@huawei.com>
Subject: Re: [Gen-art] [HOKEY] Fwd: Gen-ART review of draft-ietf-hokey-erp-aak-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: Wed, 08 Feb 2012 16:45:57 -0000

Thanks Miguel,

(cc'ing gen-art to close that loop)

S.

On 02/08/2012 02:01 PM, Miguel A. Garcia wrote:
> I did a quick past to the changes that I requested, and I think they are
> successfully implemented in version -08.
>
> /Miguel
>
> On 08/02/2012 13:52, Qin Wu wrote:
>> Hi, Stephen and all:
>> We have just done the update. Diff from previous version:
>> http://tools.ietf.org/rfcdiff?url2=draft-ietf-hokey-erp-aak-08
>>
>> Would you like to go ahead?
>>
>> Regards!
>> -Qin
>> ----- Original Message -----
>> From: "Stephen Farrell"<stephen.farrell@cs.tcd.ie>
>> To: "Tina TSOU"<Tina.Tsou.Zouting@huawei.com>
>> Cc:<miguel.a.garcia@ericsson.com>;<hokey@ietf.org>
>> Sent: Wednesday, February 08, 2012 7:41 PM
>> Subject: Re: [HOKEY] Fwd: Gen-ART review of draft-ietf-hokey-erp-aak-07
>>
>>
>>>
>>> Hi,
>>>
>>> IETF LC is ended for this.
>>>
>>> I think the only comment I saw a gen-art review (is
>>> that right?) but that there are changes resulting from
>>> that so I've marked this as revised I-D needed. Please
>>> submit a -08 that includes the changes needed. (I'm not
>>> sure if any of those will require something different
>>> from IANA, but if they do please also respond to IANA's
>>> mail, cc'ing me, if their actions are changed.)
>>>
>>> As soon as we have that I can put this on an IESG
>>> telechat agenda,
>>>
>>> Thanks,
>>> Stephen.
>>>
>>>
>>> On 02/04/2012 07:21 PM, Tina TSOU wrote:
>>>> Good catch. Thank u, Miguel.
>>>>
>>>> Sent from my iPad
>>>>
>>>> On Feb 2, 2012, at 7:04 AM, "Stephen
>>>> Farrell"<stephen.farrell@cs.tcd.ie> wrote:
>>>>
>>>>>
>>>>> FYI
>>>>>
>>>>> -------- Original Message --------
>>>>> Subject: Gen-ART review of draft-ietf-hokey-erp-aak-07
>>>>> Date: Thu, 2 Feb 2012 15:51:36 +0100
>>>>> From: Miguel A. Garcia<Miguel.A.Garcia@ericsson.com>
>>>>> To: Zhen Cao<zehn.cao@gmail.com>, Hui Deng<denghui02@gmail.com>,
>>>>> sunseawq@huawei.com, Stephen Farrell<stephen.farrell@cs.tcd.ie>
>>>>> CC: General Area Review Team<gen-art@ietf.org>
>>>>>
>>>>> 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-hokey-erp-aak-07
>>>>> Reviewer: Miguel Garcia<miguel.a.garcia@ericsson.com>
>>>>> Review Date: 2011-01-02
>>>>> IETF LC End Date: 2012-02-07
>>>>>
>>>>> Summary: This draft is on the right track but has open issues,
>>>>> described
>>>>> in the review.
>>>>>
>>>>> Major issues:
>>>>>
>>>>> - None
>>>>>
>>>>> Minor issues:
>>>>>
>>>>> - The main problem I have with this draft is the lack of normative
>>>>> text
>>>>> (RFC 2119 reserved words) in relevant paragraphs. If
>>>>> interoperability is
>>>>> to be granted, an effort should be taken in adding quite a few more
>>>>> normative statements.
>>>>>
>>>>> However, having said that, the section where I find more that there
>>>>> should be more normative text, is Section 3, which is an "Overview"
>>>>> section. In general, an overview section should use descriptive,
>>>>> but not
>>>>> normative text.
>>>>>
>>>>> For example, take the last paragraph in Page 5 (that continues to Page
>>>>> 6). One possible change is to make normative the text and move it
>>>>> outside
>>>>> a section whose title is "Overview".
>>>>>
>>>>> Upon receiving the message, the ERP/AAK server MUST first use the
>>>>> keyName indicated in the keyName-NAI to look up the rIK and MUST
>>>>> check the integrity and freshness of the message. Then the ERP/AAK
>>>>> server MUST verify the identity of the peer by checking the username
>>>>> portion of the KeyName-NAI. If any of the checks fail, the server
>>>>> MUST send an early- authentication finish message (EAP-Finish/Re-auth
>>>>> with E-flag set) with the Result flag set to '1'. Next, the server
>>>>> MUST authorize the CAP specified in the CAP-Identifier TLV. In
>>>>> success case, the server MUST derive a pMSK from the pRK for each CAP
>>>>> carried in the the CAP-Identifier field using the sequence number
>>>>> associated with CAP-Identifier as an input to the key derivation.
>>>>> (see d. in the figure 1).
>>>>>
>>>>> Then the ERP/AAK server MUST transport the pMSK to the authorized CAP
>>>>> via AAA Section 7 as described in figure 2 (see e.1,e.2 in the figure
>>>>> 2). Note that key distribution in the figure 2 is one part of step d.
>>>>> in the figure 1.
>>>>>
>>>>> The the last paragraph in Section 3 also contains an "Optionally",
>>>>> which
>>>>> I believe should be replaced with a capitalized "OPTIONAL"
>>>>>
>>>>> Another instance: towards the end of Section 5.2, the text reads:
>>>>>
>>>>> HMAC-SHA256-128 is mandatory to implement and should be enabled in
>>>>> the default configuration.
>>>>>
>>>>> and should probably be:
>>>>>
>>>>> HMAC-SHA256-128 is REQUIRED to be implemented and SHOULD be enabled in
>>>>> the default configuration.
>>>>>
>>>>> Similarly, the last paragraph in Section 5.2 reads:
>>>>>
>>>>> If the EAP-Initiate/Re-auth packet is not supported by the SAP, it is
>>>>> discarded silently.
>>>>>
>>>>> and should probably be:
>>>>>
>>>>> If the EAP-Initiate/Re-auth packet is not supported by the SAP, it
>>>>> SHOULD be discarded silently.
>>>>>
>>>>>
>>>>>
>>>>> - Another topic, Section 9 (IANA Considerations) reads:
>>>>>
>>>>> Further, this document registers a Early authentication usage label
>>>>> from the "USRK Key Labels" name space with a value:
>>>>>
>>>>> EAP Early-Authentication Root Key@ietf.org
>>>>>
>>>>>
>>>>> I am missing the sentence to name the master registry where the
>>>>> USRK Key
>>>>> Labels subregistry is stored. This is the Extended Master Session Key
>>>>> (EMSK) Parameters registry (I guess). And probably this comment is
>>>>> also
>>>>> valid for the rest of the IANA actions: the main registry is not
>>>>> named,
>>>>> and it is hard to find it.
>>>>>
>>>>>
>>>>> /Miguel
>>>>> --
>>>>> Miguel A. Garcia
>>>>> +34-91-339-3608
>>>>> Ericsson Spain
>>>>> _______________________________________________
>>>>> HOKEY mailing list
>>>>> HOKEY@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/hokey
>>>>
>>> _______________________________________________
>>> HOKEY mailing list
>>> HOKEY@ietf.org
>>> https://www.ietf.org/mailman/listinfo/hokey
>

From vkg@bell-labs.com  Wed Feb  8 08:56:56 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 9547521F8725 for <gen-art@ietfa.amsl.com>; Wed,  8 Feb 2012 08:56:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.837
X-Spam-Level: 
X-Spam-Status: No, score=-108.837 tagged_above=-999 required=5 tests=[AWL=1.762, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GmOztioX8tsp for <gen-art@ietfa.amsl.com>; Wed,  8 Feb 2012 08:56:55 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id A356D21F8711 for <gen-art@ietf.org>; Wed,  8 Feb 2012 08:56:55 -0800 (PST)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id q18GuqMw017820 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 8 Feb 2012 10:56:53 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q18GuqKj023127 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 8 Feb 2012 10:56:52 -0600
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.238.235]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q18GuowA006377; Wed, 8 Feb 2012 10:56:51 -0600 (CST)
Message-ID: <4F32AA52.1050700@bell-labs.com>
Date: Wed, 08 Feb 2012 11:01:06 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:9.0) Gecko/20111222 Thunderbird/9.0
MIME-Version: 1.0
To: draft-snell-atompub-tombstones@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.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Cc: General Area Review Team <gen-art@ietf.org>, Peter Saint-Andre <stpeter@stpeter.im>
Subject: [Gen-art] Gen-ART review of draft-snell-atompub-tombstones-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: Wed, 08 Feb 2012 16:56:56 -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-snell-atompub-tombstones-14
Reviewer: Vijay K. Gurbani
Review Date: Feb-08-2012
IETF LC End Date: Feb-21-2012
IESG Telechat date: Not known

Summary: This draft is ready as an Informational.

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

Thanks,

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


From elwynd@dial.pipex.com  Thu Feb  9 03:49:13 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 0D42E21F8700 for <gen-art@ietfa.amsl.com>; Thu,  9 Feb 2012 03:49:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.011
X-Spam-Level: 
X-Spam-Status: No, score=-102.011 tagged_above=-999 required=5 tests=[AWL=0.588, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vn0BGOfvBfXc for <gen-art@ietfa.amsl.com>; Thu,  9 Feb 2012 03:49:12 -0800 (PST)
Received: from b.c.painless.aaisp.net.uk (c.painless.aaisp.net.uk [IPv6:2001:8b0:0:30::51bb:1e35]) by ietfa.amsl.com (Postfix) with ESMTP id 7DAB221F8543 for <gen-art@ietf.org>; Thu,  9 Feb 2012 03:49:12 -0800 (PST)
Received: from 250.254.187.81.in-addr.arpa ([81.187.254.250]) by c.painless.aaisp.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <elwynd@dial.pipex.com>) id 1RvSUs-0008Rt-As; Thu, 09 Feb 2012 11:49:06 +0000
From: Elwyn Davies <elwynd@dial.pipex.com>
To: General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain
Date: Thu, 09 Feb 2012 11:52:06 +0000
Message-Id: <1328788326.4345.440.camel@mightyatom.folly.org.uk>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-netext-radius-pmip6.all@tools.ietf.org
Subject: [Gen-art] Gen-art: Telechat review of draft-ietf-netext-radius-pmip6-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, 09 Feb 2012 11:49:13 -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-netext-radius-pmip6-08
Reviewer: Elwyn Davies
Review Date: 9 February 2012
IETF LC End Date: 19 January 2012
IESG Telechat date: 19 January 2012-

Summary: Ready.  
For the record the various issues identified at last call have been fixed - thanks.

Major issues: 
None-

Minor issues:
None

Nits/editorial comments:
s4.1, last para: s/contradicting combination/contradictory combinations/ (2 places).


From mahoney@nostrum.com  Thu Feb  9 15:22:15 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 3370E21F85B8 for <gen-art@ietfa.amsl.com>; Thu,  9 Feb 2012 15:22:14 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sD3qXBELNIBT for <gen-art@ietfa.amsl.com>; Thu,  9 Feb 2012 15:22:12 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id D66AC21F85E3 for <gen-art@ietf.org>; Thu,  9 Feb 2012 15:22:11 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-71-170-125-181.dllstx.fios.verizon.net [71.170.125.181]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q19NMAvI098566 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 9 Feb 2012 17:22:10 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <4F345522.608@nostrum.com>
Date: Thu, 09 Feb 2012 17:22:10 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
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: 71.170.125.181 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2012-02-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, 09 Feb 2012 23:22:15 -0000

Hi all,

Here's the link to the new LC assignments:
http://wiki.tools.ietf.org/dav/genart/reviewers-120209-lc.html

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


And 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 mahoney@nostrum.com  Thu Feb  9 15:33:51 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 B7EB811E808F for <gen-art@ietfa.amsl.com>; Thu,  9 Feb 2012 15:33:51 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xj1UZqkUwcTc for <gen-art@ietfa.amsl.com>; Thu,  9 Feb 2012 15:33:51 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 9F63F11E8080 for <gen-art@ietf.org>; Thu,  9 Feb 2012 15:33:39 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-71-170-125-181.dllstx.fios.verizon.net [71.170.125.181]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q19NXWK8000429 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 9 Feb 2012 17:33:33 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <4F3457CC.20506@nostrum.com>
Date: Thu, 09 Feb 2012 17:33:32 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
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: 71.170.125.181 is authenticated by a trusted mechanism)
Subject: [Gen-art] Assignments for the 2012-02-16 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, 09 Feb 2012 23:33:51 -0000

Hi all,

Assignments for the telechat can be found here:
http://wiki.tools.ietf.org/dav/genart/reviewers-120216-telechat.html

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

I've also updated the review tool:
http://art.tools.ietf.org/tools/art/genart/

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 Feb  9 17:33:32 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 55B6F11E8079 for <gen-art@ietfa.amsl.com>; Thu,  9 Feb 2012 17:33:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.108
X-Spam-Level: 
X-Spam-Status: No, score=-102.108 tagged_above=-999 required=5 tests=[AWL=0.157, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NP-OH8hbAF0s for <gen-art@ietfa.amsl.com>; Thu,  9 Feb 2012 17:33:32 -0800 (PST)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id F3CE021F84D2 for <gen-art@ietf.org>; Thu,  9 Feb 2012 17:33:31 -0800 (PST)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by morbo.tigertech.net (Postfix) with ESMTP id D87D6CD4AE for <gen-art@ietf.org>; Thu,  9 Feb 2012 17:33:31 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id AAA6B2813BB; Thu,  9 Feb 2012 17:33:30 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [10.10.10.101] (pool-71-161-51-124.clppva.btas.verizon.net [71.161.51.124]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 2B1C52813AC; Thu,  9 Feb 2012 17:33:30 -0800 (PST)
Message-ID: <4F3473E6.4040904@joelhalpern.com>
Date: Thu, 09 Feb 2012 20:33:26 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>
References: <4F345522.608@nostrum.com>
In-Reply-To: <4F345522.608@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-ietf-v6ops-v6nd-problems-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: Fri, 10 Feb 2012 01:33: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-v6ops-v6nd-problems-04
     Operational Neighbor Discovery Problems
Reviewer: Joel M. Halpern
Review Date: 9-Feb-2012
IETF LC End Date: 20-Feb-2012
IESG Telechat date: 1-March-2012

Summary: This document is ready for publication as an Informational RFC


From roberta.maglione@telecomitalia.it  Fri Feb 10 05:52:53 2012
Return-Path: <roberta.maglione@telecomitalia.it>
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 8224F21F84B3; Fri, 10 Feb 2012 05:52:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.57
X-Spam-Level: 
X-Spam-Status: No, score=0.57 tagged_above=-999 required=5 tests=[AWL=1.289, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cfa7siBcV3AJ; Fri, 10 Feb 2012 05:52:51 -0800 (PST)
Received: from GRFEDG701BA020.telecomitalia.it (grfedg701ba020.telecomitalia.it [156.54.233.200]) by ietfa.amsl.com (Postfix) with ESMTP id BE57B21F8527; Fri, 10 Feb 2012 05:52:50 -0800 (PST)
Received: from grfhub704ba020.griffon.local (10.188.101.117) by GRFEDG701BA020.telecomitalia.it (10.188.45.100) with Microsoft SMTP Server (TLS) id 8.2.254.0; Fri, 10 Feb 2012 14:52:49 +0100
Received: from GRFMBX704BA020.griffon.local ([10.188.101.15]) by grfhub704ba020.griffon.local ([10.188.101.117]) with mapi; Fri, 10 Feb 2012 14:52:49 +0100
From: Maglione Roberta <roberta.maglione@telecomitalia.it>
To: 'Ben Campbell' <ben@nostrum.com>, "draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org" <draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org>
Date: Fri, 10 Feb 2012 14:52:48 +0100
Thread-Topic: Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-03
Thread-Index: AczlJZFTFF9sbXZqSKGvHQvAXvqfzQC0stGQ
Message-ID: <282BBE8A501E1F4DA9C775F964BB21FE3EC1467FB2@GRFMBX704BA020.griffon.local>
References: <A57C4722-5E13-451E-ACB4-CAA8064FA68B@nostrum.com>
In-Reply-To: <A57C4722-5E13-451E-ACB4-CAA8064FA68B@nostrum.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-Mailman-Approved-At: Fri, 10 Feb 2012 06:26:39 -0800
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, Ullio Mario <mario.ullio@telecomitalia.it>, The IETF <ietf@ietf.org>, "'Henderickx, Wim \(Wim\)'" <wim.henderickx@alcatel-lucent.com>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-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, 10 Feb 2012 13:52:53 -0000

Hello Ben,
   Thanks for reviewing this document.
Please see answers inline [RM]

Best regards,
Roberta

-----Original Message-----
From: Ben Campbell [mailto:ben@nostrum.com]
Sent: marted=EC 7 febbraio 2012 0.17
To: draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org
Cc: gen-art@ietf.org Review Team; The IETF
Subject: Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-03

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/Gen=
Artfaq>.

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

Document: draft-ietf-dhc-forcerenew-nonce-03
Reviewer: Ben Campbell
Review Date: 2012-02-06
IETF LC End Date: 2012-02-06

Summary:This draft is not quite ready for publication as a proposed standar=
d. There are some potentially significant issues that should be addressed f=
irst.

[Note: Hopefully this draft has had or will have a SecDir review, since it =
seems ripe for significant security implications.]


*** Major issues:

-- I admit to not being a DHCP expert, but If I understand this draft corre=
ctly, it proposes to send what is effectively a secret-key in a DHCPACK req=
uest, then use that key to authenticate a force renew message. It seems lik=
e any eavesdropper could sniff that key, and use it to spoof force renew re=
quests. The introduction mentions that there may be some environments where=
 the use of RFC3118 authentication could be relaxed, and offers an example =
of such an environment. But nowhere does this draft appear to be limited in=
 scope to such environments.

[RM] The intention is to use this method only for environments with native =
security mechanisms, such as the Broadband Access network. You are right it=
 is not clearly said in the document I can add the following sentence at th=
e end of the introduction in order to clarify this point:

"This   mechanism is intended to be use in networks that already have nativ=
e security mechanisms that provide sufficient protection against
spoofing of DHCP traffic."


I think some additional text in (perhaps in the security considerations) is=
 needed to explain either why the vulnerability to eavesdroppers is either =
okay in general, or limits the mechanism's use to environment where it is o=
kay. It also seems like that, in the best case, this mechanism proves only =
that a Forcerenew request comes from the same DHCP server as in the origina=
l transaction, but otherwise does not prove anything about the identity of =
that server. If so, it would be worth mentioning it.

[RM] That's correct this mechanism only proves only that a Forcerenew reque=
st comes from the same DHCP server: let me say this is a trade off between =
the total security provided by RFC 3118 and no security at all. In addition=
 this method relays on the same mechanism already used for DHCPv6 Reconfigu=
re message

-- The mechanism appears to be limited to HMAC-MD5, and there does not appe=
ar to be any way of selecting other algorithms. Is HMAC-MD5 really sufficie=
nt as the only choice? Is there some expectation that stronger mechanisms o=
r algorithm extensibility would be too expensive? (Perhaps the extensibilit=
y method would be to specify another mechanism that's identical except for =
a different HMAC algorithm. But if that's the intent it should be mentioned=
.)
[RM] This is because this mechanism relays on the authentication protocol d=
efined in section 21.5 of RFC 3315 for DHCPv6 Reconfigure and there HMAC-MD=
5 is used.

*** Minor issues:

-- Section 1 "
In such environments the mandatory coupling between FORCERENEW and DHCP Aut=
hentication [RFC3118] can be relaxed."

It's not clear to me what connection that assertion has with this draft. Is=
 there an intent that the proposed mechanisms be used only in such environm=
ents? I don't find any language scoping this proposal to any particular env=
ironment.

[RM] The intention is to use this method only in environments with native s=
ecurity mechanisms, I'll try to clarify this point

-- section 3:

Does this draft update either 3203 or 3118? If so, please state that explic=
itly in the abstract, introduction, and draft headers. (I think it must at =
least update 3203, since that draft requires the use of 3118, and this draf=
t relaxes that.)
[RM] Yes that's correct, it updates 3203, I'll add it in the document.

-- section 3.1, last paragraph: "...only if the client and server are not u=
sing any other authentication..."

That seems to conflict with the statement in section 3 that this mechanism =
is only used if RFC3118 is not used. That is, it's not a choice between thi=
s mechanism or any other mechanism, it's a choice between this mechanism or=
 3118.
[RM] I'll clarify the sentence

-- section 3.1.3, 2nd paragraph: "The server SHOULD NOT include this option=
 unless the client has indicated its capability in a DHCP Discovery message=
."

Why not; what harm would it do? And on the other hand, if you want to disco=
urage it, why not go all the way to "MUST NOT"?

[RM] For backward compatibility: if the client did not indicate its capabil=
ity for this feature it means it is a legacy client and it does not support=
 it, so the server should not send the nonce to this client

-- section 3.1.3, 5th paragraph: "...  computes an HMAC-MD5 of the Forceren=
ew message using the Forcerenew nonce ."

Using it how? Is it the secret key for the HMAC calculation? (If so, why ar=
en't we calling it a "key" in the first place?)
[RM] based on the procedure specified in section 21.5 of RFC 3315

-- section 3.1.4, 1st paragraph: "DHCP servers that support Forcerenew nonc=
e Protocol authentication MUST include the DHCP Forcerenew Nonce protocol a=
uthentication option."

Only if the client advertised it, right? Otherwise, this seems to conflict =
with the previous SHOULD NOT.
[RM] ok

-- section 3.1.4, 4th paragraph: ".
the client computes an HMAC-MD5 over the DHCP Forcerenew message, using the=
 Forcerenew Nonce ."

Using it how?
[RM] based on the procedure specified in section 21.5 of RFC 3315

-- section 6:

You mention this mechanism is vulnerable to MiTM attacks. Why is this okay?=
 Are there some environments where it is good enough and others where it is=
 not? (Also, do they really need to be MitM attackers? Seems like any eaves=
dropper could learn the nonce.)

*** Nits/editorial comments:
[RM] I'll address the following comments too.

-- Abstract, second sentence:

I have trouble parsing this sentence. Are the propositions correct?

-- Section 3.1.1,4th paragraph: ". configured to require ."

Do you mean configured to "require", or configured to "use"? I would normal=
ly take "requires" to mean that the server would not work with clients that=
 don't advertise support for the mechanism.

-- section 3.1.1, message flow diagram:

It would be helpful if you could avoid widowing the top of the diagram. One=
 has to keep flipping back to see the labels.

-- section 3.1.3, 5th paragraph:

Please expand "RDM"

-- section 3.1.4, first paragraph: "The client MUST."

A client that supports this mechanism MUST.

-- section 3.1.4, 2nd and third paragraph, 1st sentence of each:

I'm confused by this sentence of each paragraph. Are they intended as condi=
tionals for the rest of the respective paragraph?







Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle per=
sone indicate. La diffusione, copia o qualsiasi altra azione derivante dall=
a conoscenza di queste informazioni sono rigorosamente vietate. Qualora abb=
iate ricevuto questo documento per errore siete cortesemente pregati di dar=
ne immediata comunicazione al mittente e di provvedere alla sua distruzione=
, Grazie.

This e-mail and any attachments is confidential and may contain privileged =
information intended for the addressee(s) only. Dissemination, copying, pri=
nting or use by anybody else is unauthorised. If you are not the intended r=
ecipient, please delete this message and any attachments and advise the sen=
der by return e-mail, Thanks.


From martin.thomson@gmail.com  Fri Feb 10 09:15:33 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 E13DE21F86A7 for <gen-art@ietfa.amsl.com>; Fri, 10 Feb 2012 09:15:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.077
X-Spam-Level: 
X-Spam-Status: No, score=-5.077 tagged_above=-999 required=5 tests=[AWL=-1.478, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SPkCxUw8q6zr for <gen-art@ietfa.amsl.com>; Fri, 10 Feb 2012 09:15:33 -0800 (PST)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id F073321F8668 for <gen-art@ietf.org>; Fri, 10 Feb 2012 09:15:32 -0800 (PST)
Received: by bkuw12 with SMTP id w12so3000539bku.31 for <gen-art@ietf.org>; Fri, 10 Feb 2012 09:15:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=3RtuuDmO2gOekjsm7lcpaisApZGdP651VBN9NQ/4MPo=; b=sDCyKAiw/+n7yE9IeLzqQ+ziYrwIXo1wkEIvUM3a5kvI+I+kWCdhj6dnXUZmawla8H yiF4A3hMHBP1nxH9VwHapIu7JU50KBBzQgkTuxr1FySL7kBZKhDr2cV7F9g4pWbFvhYc KCrTjE4T0VFOHBz8pApJWhgyeAuBL82a1RbQY=
MIME-Version: 1.0
Received: by 10.204.153.195 with SMTP id l3mr2882209bkw.123.1328894132083; Fri, 10 Feb 2012 09:15:32 -0800 (PST)
Received: by 10.204.241.81 with HTTP; Fri, 10 Feb 2012 09:15:32 -0800 (PST)
Date: Fri, 10 Feb 2012 09:15:32 -0800
Message-ID: <CABkgnnWu8HaM-EaKbB=_yxNF0Q5k9PyF99yFOcq0S6DxMxFLcA@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: draft-george-travel-faq.all@tools.ietf.org
Content-Type: text/plain; charset=UTF-8
Cc: gen-art@ietf.org
Subject: [Gen-art] Gen-ART review of draft-george-travel-faq-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, 10 Feb 2012 17:15:34 -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-george-travel-faq-03
Reviewer: Martin Thomson
Review Date: 2012-02-10
IETF LC End Date: 2012-03-06
IESG Telechat date: ?

Summary: Ready

Major issues: none

Minor issues: none

Nits/editorial comments:
List construction throughout is a little haphazard. Check
capitalization in particular.
s/Souvenier/Souvenir/

From christer.holmberg@ericsson.com  Sat Feb 11 02:13:50 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 17BE221F854B for <gen-art@ietfa.amsl.com>; Sat, 11 Feb 2012 02:13:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.184
X-Spam-Level: 
X-Spam-Status: No, score=-9.184 tagged_above=-999 required=5 tests=[AWL=1.415,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ejJnsVSxrR3W for <gen-art@ietfa.amsl.com>; Sat, 11 Feb 2012 02:13:49 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id 2F12A21F8542 for <gen-art@ietf.org>; Sat, 11 Feb 2012 02:13:49 -0800 (PST)
X-AuditID: c1b4fb39-b7bf2ae0000069a1-af-4f363f5bfdec
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 28.64.27041.B5F363F4; Sat, 11 Feb 2012 11:13:48 +0100 (CET)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.175]) by esessmw0247.eemea.ericsson.se ([153.88.115.93]) with mapi; Sat, 11 Feb 2012 11:13:48 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "draft-ietf-simple-chat.all@tools.ietf.org" <draft-ietf-simple-chat.all@tools.ietf.org>
Date: Sat, 11 Feb 2012 11:13:47 +0100
Thread-Topic: Gen-ART review of draft-ietf-simple-chat-13
Thread-Index: AQHM6KXXwYnbX7WMyEKD7vOb2ZWL0A==
Message-ID: <7F2072F1E0DE894DA4B517B93C6A05852C3D31BA1E@ESESSCMS0356.eemea.ericsson.se>
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-Brightmail-Tracker: AAAAAA==
Cc: "gen-art@ietf.org" <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-simple-chat-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: Sat, 11 Feb 2012 10:13:50 -0000

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

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

Document:                  draft-ietf-simple-chat-13
Reviewer:                   Christer Holmberg
Review Date:              12-02.11
IETF LC End Date:     12-02-06
IESG Telechat date: (if known)

Summary:          Ready, but some additional text may be needed based on th=
e minor issues.

Major issues:     None

Minor issues:

- The second paragraph of section 7.1 says that a NICKNAME request MUST con=
tain a Use-Nickname header, but in the sixth paragraph the inclusion is a S=
HOULD.

- It is not clearly indicated whether the Use-Nickname header is allowed fo=
r other methods than NICKNAME.

- Section 8 does not specify whether there are SDP offer/answer considerati=
ons/restrictions associated with the new attribute. For example:=20
-- Must the attribute tokens in an answer be a subset of the tokens in an o=
ffer?
-- Can an SDP answer contain an attribute if the offer didn't?
-- If a user sends a new SDP offer within a session, can the token values b=
e modified? What does it mean if the attribute is not present in a new SDP =
offer?


Nits/editorial comments:

- Sometimes the document talks about "multi-party chat", "multi-party confe=
rence", "conference", and "chat room". Would it be possible to use more con=
sistant terminology?

- Requirements
-- REQ-4: Isn't this requirement already covered by REQ-3?
-- REQ-6: Change "progress" to "duration" or "length".

- There is no definition/reference for "roster".


Regards,

Christer=

From Ted.Lemon@nominum.com  Sat Feb 11 08:24:38 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 7537E21F84B9; Sat, 11 Feb 2012 08:24:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.51
X-Spam-Level: 
X-Spam-Status: No, score=-106.51 tagged_above=-999 required=5 tests=[AWL=0.089, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wrm4CJa6PWHr; Sat, 11 Feb 2012 08:24:38 -0800 (PST)
Received: from exprod7og127.obsmtp.com (exprod7og127.obsmtp.com [64.18.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 84A3F21F8497; Sat, 11 Feb 2012 08:24:37 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob127.postini.com ([64.18.6.12]) with SMTP ID DSNKTzaWRL0l725TjoS0phrPwfn0hGo2zTiD@postini.com; Sat, 11 Feb 2012 08:24:37 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 31ECA1B82C5; Sat, 11 Feb 2012 08:24:36 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (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 20188190052; Sat, 11 Feb 2012 08:24:36 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.01.0339.001; Sat, 11 Feb 2012 08:24:30 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Maglione Roberta <roberta.maglione@telecomitalia.it>
Thread-Topic: Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-03
Thread-Index: AQHM5SWUy8EqSdK3C0aOhQFr8l21aJY2slwAgAG8tQA=
Date: Sat, 11 Feb 2012 16:24:29 +0000
Message-ID: <CEA6CD8F-7DCD-448C-8C31-EC64FD9902A3@nominum.com>
References: <A57C4722-5E13-451E-ACB4-CAA8064FA68B@nostrum.com> <282BBE8A501E1F4DA9C775F964BB21FE3EC1467FB2@GRFMBX704BA020.griffon.local>
In-Reply-To: <282BBE8A501E1F4DA9C775F964BB21FE3EC1467FB2@GRFMBX704BA020.griffon.local>
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="iso-8859-1"
Content-ID: <D29119CD5394A942A43CB1A96A908D22@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Ben Campbell <ben@nostrum.com>, The IETF <ietf@ietf.org>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org" <draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org>, Ullio Mario <mario.ullio@telecomitalia.it>, "Henderickx, Wim \(Wim\)" <wim.henderickx@alcatel-lucent.com>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-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: Sat, 11 Feb 2012 16:24:38 -0000

> [RM] The intention is to use this method only for environments with nativ=
e security mechanisms, such as the Broadband Access network. You are right =
it is not clearly said in the document I can add the following sentence at =
the end of the introduction in order to clarify this point:
>=20
> "This   mechanism is intended to be use in networks that already have nat=
ive security mechanisms that provide sufficient protection against
> spoofing of DHCP traffic."

It's probably worth revisiting the purpose of this mechanism.   The problem=
 that we are trying to solve is that people are reluctant to implement DHCP=
FORCERENEW because it's possible that an off-link attacker could more accur=
ately guess the timing of DHCP renewal messages by first sending a DHCPFORC=
ERENEW.   The mechanism in RFC3315 (DHCPv6), which this document mirrors fo=
r DHCPv4, uses a nonce to prevent an off-link attacker from successfully tr=
iggering a renewal on a client by sending DHCPFORCERENEW; since the attacke=
r is off-link, it doesn't have the nonce, and can't force a renewal.

An on-link attacker can always simply watch the DHCP renewal message go out=
 and respond to it, so this mechanism is useless for preventing on-link att=
acks, and hence the security of the nonce in the case of on-link attacks is=
n't relevant.  So the above text isn't needed.   It's possible that the doc=
ument doesn't clearly document the use case for this functionality; if so, =
you are free to take the above paragraph, Roberta, and modify it to suit yo=
ur purposes.   But I am against adding the text you proposed, because it ex=
cludes the bulk of use cases for the DHCPFORCERENEW nonce mechanism.

> [RM] This is because this mechanism relays on the authentication protocol=
 defined in section 21.5 of RFC 3315 for DHCPv6 Reconfigure and there HMAC-=
MD5 is used.

Essentially HMAC-MD5 is being used here to package a secret into a chunk of=
 predictable size, and the fact that there are hacks for the mechanism isn'=
t terribly important because the only attacker we are attempting to foil is=
 one that doesn't have access to the cleartext or the ciphertext.=

From housley@vigilsec.com  Sun Feb 12 13:22:17 2012
Return-Path: <housley@vigilsec.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 8FB5721F86A8 for <gen-art@ietfa.amsl.com>; Sun, 12 Feb 2012 13:22:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.521
X-Spam-Level: 
X-Spam-Status: No, score=-101.521 tagged_above=-999 required=5 tests=[AWL=-1.076, BAYES_00=-2.599, FRT_BELOW2=2.154, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n-j9wbUq8O3T for <gen-art@ietfa.amsl.com>; Sun, 12 Feb 2012 13:22:16 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 5CE4C21F868A for <gen-art@ietf.org>; Sun, 12 Feb 2012 13:22:16 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 7DC56F2407C; Sun, 12 Feb 2012 16:22:20 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id YOWI-os7mThY; Sun, 12 Feb 2012 16:22:12 -0500 (EST)
Received: from [192.168.2.107] (pool-96-241-165-215.washdc.fios.verizon.net [96.241.165.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 4E73BF2402B; Sun, 12 Feb 2012 16:22:19 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <1328704106.4345.410.camel@mightyatom.folly.org.uk>
Date: Sun, 12 Feb 2012 16:22:14 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <41C110BA-F7A1-4E81-A48D-9114A6286901@vigilsec.com>
References: <1328187998.4790.2946.camel@mightyatom.folly.org.uk> <BB94D1B3E4CD4E1BA7107AF5A99D19BE@china.huawei.com> <1328698730.4345.364.camel@mightyatom.folly.org.uk> <BF80F6B7104742079DDF846CD4863A4D@china.huawei.com> <1328704106.4345.410.camel@mightyatom.folly.org.uk>
To: Qin Wu <bill.wu@huawei.com>
X-Mailer: Apple Mail (2.1084)
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-dime-pmip6-lr.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art review of draft-ietf-dime-pmip6-lr-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: Sun, 12 Feb 2012 21:22:17 -0000

The -07 version of this document is on the IESG telechat this week.  How =
will the agreed changes be made?

Russ


On Feb 8, 2012, at 7:28 AM, Elwyn Davies wrote:

> Hi, Qin.
>=20
> Fine - I think all will be good from my point of view if you say a few
> words about linking the MAGs as per your last response belwow.
>=20
> Cheers,
> Elwyn
>=20
> On Wed, 2012-02-08 at 19:47 +0800, Qin Wu wrote:
>> Hi, Elwyn:
>> Thank for your followup comments, please see my replies inline.
>>=20
>> Regards!
>> -Qin
>> ----- Original Message -----=20
>> From: "Elwyn Davies" <elwynd@dial.pipex.com>
>> To: "Qin Wu" <bill.wu@huawei.com>
>> Cc: "General Area Review Team" <gen-art@ietf.org>; =
<draft-ietf-dime-pmip6-lr.all@tools.ietf.org>
>> Sent: Wednesday, February 08, 2012 6:58 PM
>> Subject: Re: [Gen-art] Gen-art review of draft-ietf-dime-pmip6-lr-07
>>=20
>>=20
>>> Hi, Qin.
>>>=20
>>> Thanks for your quick reponse.. some comments in line (I have =
deleted
>>> the bits agreed),
>>>=20
>>> /Elwyn
>>>=20
>>> On Fri, 2012-02-03 at 12:53 +0800, Qin Wu wrote:
>>>> Hi,Elwyn:
>>>> Thank for your valuable review. please see our replies below.
>>>> ----- Original Message -----=20
>>>> From: "Elwyn Davies" <davieseb@scss.tcd.ie>
>>>> To: "General Area Review Team" <gen-art@ietf.org>
>>>> Cc: <draft-ietf-dime-pmip6-lr.all@tools.ietf.org>
>>>> Sent: Thursday, February 02, 2012 9:06 PM
>>>> Subject: Gen-art review of draft-ietf-dime-pmip6-lr-07
>>>>=20
>>>>=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 wait for direction from your document shepherd
>>>>> or AD before posting a new version of the draft.
>>>>>=20
>>>>> Document: draft-ietf-dime-pmip6-lr-07.txt
>>>>> Reviewer: Elwyn Davies
>>>>> Review Date: 2 February 2012
>>>>> IETF LC End Date: 24 January 2012
>>>>> IESG Telechat date: 16 February 2012
>>>>>=20
>>>>> Summary:
>>>>> I have a couple of queries/minor issues regarding checking whether =
LMA1
>>>>> and LMA2 are the same node and some hand waving over the idea of
>>>>> 'localized routing setup/signaliing'.  There are also a few minor =
nits.
>>>>> Otherwise this is ready for the IESG.
>>>>>=20
>>>>> [This document missed the normal gen-art last call allocation
>>>>> notification mechanism for some reason - so I didn't realize it =
was on
>>>>> my allocation till the end of last call and as a result the review =
is a
>>>>> bit late.]
>>>>>=20
>>>>> Major issues:
>>>>> None
>>>>>=20
>>>>> Minor issues:
>>>>> s5.1, para 3 and s5.2, last para:
>>>>> In s5.1:
>>>>>> MAG1 can verify
>>>>>>   whether both MAGs are under the same LMA by comparing the =
addresses
>>>>>>   of LMA1 and LMA2.
>>>>> Is this guaranteed to work?  Should we care? Or is this just too =
bad if
>>>>> the LMA has multiple addresses and the two MNs have different =
ideas?
>>>>=20
>>>> [Qin]: In the example described in the s5.1, we don't consider one =
LMA has two LMA address.
>>>> LMA1 and LMA2 may represent two different mobility entities =
identified by LMA1 adress and LMA2 adress respectively.
>>>> If LMA1 address is LMA2 address, this just indicate LMA1 and LMA2 =
are the same mobility entity.
>>>> Even one LMA have more than one LMA address, this still work since =
MAG can know if these LMA addresses come from
>>>> the same mobility entity based on MN1 and MN2's binding update =
list.
>>>>=20
>>>>> However in s5.2:
>>>>>> In the case where MNs share the same LMA, LR should be initiated =
by
>>>>>>   LMA1 (i.e.,LMA2) since only LMA1 knows that both MN1 and MN2 =
belong
>>>>>>   to itself by looking up the binding cache entries corresponding =
to
>>>>>>   MN1 and MN2.=20
>>>>> I am unsure whether these two statements are talking about the =
same
>>>>> thing - and, if so, are they contradictory?
>>>>>=20
>>>>=20
>>>> [Qin]: No Confliction, See above.
>>>=20
>>> I think this is exactly the point: You give two different (but =
allegedly
>>> non-conflicting ways) of doing the same thing at two places in the
>>> draft.  =46rom what you say, I infer that you could do either thing =
in
>>> both cases. If so then it would be better to give the alternatives
>>> together for the first case and refer to the previous comments when =
the
>>> second case is reached in the text.
>>=20
>> [Qin]: Good suggestion and will follow this.
>>>=20
>>>>=20
>>>>> s5.1, last para:
>>>>>> Figure 4 shows another example scenario, similar to the example
>>>>>>   scenario illustrated in Figure 3, LMA1 does not respond to MAG1 =
with
>>>>>>   the address of LMA2, instead setting up a localized routing =
path
>>>>>>   directly between itself and LMA2 via localized routing =
signaling.
>>>>> I am unsure what 'localized routing signaliing' would involve.  =
What
>>>>> would the nodes do for this?  Appears to involve some waving of =
hands.
>>>>=20
>>>> [Qin]: LMA1 and LMA2 exchange to trigger corresponding LMA to setup =
binding entries
>>>> on the correspoding MAG for localized routing and establish =
localized
>>>> routing path between MAG1 and MAG2.
>>>>=20
>>>>> On a slightly broader point, there are a number of places where =
the
>>>>> phrase 'localized routing setup' (or similar) is used.  It would, =
I
>>>>> think, be useful to add a few words indicating what is thought to =
be
>>>>> involved although actually doing it is clearly out of scope of =
this
>>>>> document.
>>>>=20
>>>> [Qin]: Okay.
>>>=20
>>> I am afraid this doesn't really help: You say 'establish localized
>>> routing path between MAG1 and MAG2'. How? Does this imply that the =
MAG
>>> or some other component will (re-)configure the local packet routing
>>> infrastructure? (Not something I would expect the MAG to be =
authorized
>>> to do.) Or is this a matter of creating a tunnel?  I think this =
needs to
>>> be a whole lot more concrete - both ends have to be expecting the
>>> packets and know what to do with them.
>>=20
>> [Qin]: Yes, your are right. Tunneling between MAG1 and MAG2 should be =
configured on both MAGs.
>> As default static behavior,tunnel between MAG1 and MAG2 uses the same =
encapsulation mechanism
>> as that being used for PMIP tunnel between MAG and LMA. In this case, =
MAG1 and MAG2
>> can start using the same tunneling mechanism without special =
configuration (e.g.using other=20
>> tunnel mechanism that is uniform in the PMIP domain) on MAGs or =
dynamic tunneling negotiation between MAGs.
>> but special configuration on MAGs or dynamic tunnel negotiation can =
overide=20
>> the default static behavior mentioned above if they are really =
needed.
>>=20
>> Hope this clarifies.
>>=20
>>> Regards,
>>> Elwyn =20
>>>=20
>>>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From bill.wu@huawei.com  Sun Feb 12 14:33:25 2012
Return-Path: <bill.wu@huawei.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 0EC2221F86B1 for <gen-art@ietfa.amsl.com>; Sun, 12 Feb 2012 14:33:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.325
X-Spam-Level: 
X-Spam-Status: No, score=-0.325 tagged_above=-999 required=5 tests=[AWL=-4.928, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, FRT_BELOW2=2.154, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RbxXkLjPtBbm for <gen-art@ietfa.amsl.com>; Sun, 12 Feb 2012 14:33:24 -0800 (PST)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id AF4A321F86A8 for <gen-art@ietf.org>; Sun, 12 Feb 2012 14:33:23 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LZA00I7RXBL0Q@szxga05-in.huawei.com> for gen-art@ietf.org; Mon, 13 Feb 2012 06:33:21 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LZA00II9XBL3H@szxga05-in.huawei.com> for gen-art@ietf.org; Mon, 13 Feb 2012 06:33:21 +0800 (CST)
Received: from szxeml214-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AGT82881; Mon, 13 Feb 2012 06:32:56 +0800
Received: from SZXEML421-HUB.china.huawei.com (10.82.67.160) by szxeml214-edg.china.huawei.com (172.24.2.29) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 13 Feb 2012 06:32:52 +0800
Received: from SZXEML523-MBS.china.huawei.com ([169.254.6.84]) by szxeml421-hub.china.huawei.com ([10.82.67.160]) with mapi id 14.01.0323.003; Mon, 13 Feb 2012 06:33:13 +0800
Date: Sun, 12 Feb 2012 22:32:51 +0000
From: Qin Wu <bill.wu@huawei.com>
In-reply-to: <41C110BA-F7A1-4E81-A48D-9114A6286901@vigilsec.com>
X-Originating-IP: [172.24.1.67]
To: Russ Housley <housley@vigilsec.com>
Message-id: <B8F9A780D330094D99AF023C5877DABA1BED33E9@szxeml523-mbs.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=gb2312
Content-language: zh-CN
Content-transfer-encoding: base64
Accept-Language: zh-CN, en-US
Thread-topic: [Gen-art] Gen-art review of draft-ietf-dime-pmip6-lr-07
Thread-index: AQHM5l0nzxZZd8CeaUGqmjviFOqUrZY5RfAAgACVcHE=
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: <1328187998.4790.2946.camel@mightyatom.folly.org.uk> <BB94D1B3E4CD4E1BA7107AF5A99D19BE@china.huawei.com> <1328698730.4345.364.camel@mightyatom.folly.org.uk> <BF80F6B7104742079DDF846CD4863A4D@china.huawei.com> <1328704106.4345.410.camel@mightyatom.folly.org.uk> <41C110BA-F7A1-4E81-A48D-9114A6286901@vigilsec.com>
Cc: General Area Review Team <gen-art@ietf.org>, "draft-ietf-dime-pmip6-lr.all@tools.ietf.org" <draft-ietf-dime-pmip6-lr.all@tools.ietf.org>
Subject: [Gen-art] =?gb2312?b?tPC4tDogIEdlbi1hcnQgcmV2aWV3IG9mIGRyYWZ0LWll?= =?gb2312?b?dGYtZGltZS1wbWlwNi1sci0wNw==?=
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, 12 Feb 2012 22:33:25 -0000

SGksIFJ1c3M6DQpTaG91bGQgSSBhZGRyZXNzIHRoZXNlIGNvbW1lbnRzIGJlZm9yZSBJRVNHIHRl
bGVjaGF0Pw0KTXkgcmVzcG9uc2UgbWF5IGJlIGxpbWl0ZWQgZHVlIHRvIGJ1c2luZXNzIHRyaXAg
aW4gbXkgbmV4dCB3ZWVrLiBIZXJlIGlzIG15IHByb3Bvc2VkIGNoYW5nZXMgdG8gdmVyc2lvbiAw
Ny4NCg0KMS5TZWN0aW9uIDUuMSwgM3JkIHBhcmFncmFwaCwgbGFzdCBzZW50ZW5jZS4NCk9MRCB0
ZXh0Og0KIg0KTUFHMSBjYW4gdmVyaWZ5DQogICB3aGV0aGVyIGJvdGggTUFHcyBhcmUgdW5kZXIg
dGhlIHNhbWUgTE1BIGJ5IGNvbXBhcmluZyB0aGUgYWRkcmVzc2VzZQ0KICAgb2YgTE1BMSBhbmQg
TE1BMi4gIE1BRzEgdGhlbiByZXF1ZXN0cyB0aGUgYWRkcmVzcyBvZiBNQUcyIGZyb20gTE1BMg0K
ICAgYW5kIHVzZXMgdGhhdCBhZGRyZXNzIHRvIHNldHVwIHRoZSBsb2NhbGl6ZWQgcm91dGluZyBw
YXRoIGJldHdlZW4NCiAgIGl0c2VsZiBhbmQgTUFHMiB2aWEgYSBQcm94eSBCaW5kaW5nIFVwZGF0
ZSAoUEJVKS9Qcm94eSBCaW5kaW5nDQogICBBY2tub3dsZWRnZW1lbnQgKFBCQSkgbWVzc2FnZSBl
eGNoYW5nZSBbUkZDNTIxM10uDQoiDQpORVcgdGV4dDoNCiINCklmICBNQUcxIGtub3dzIHRoYXQg
TU4xIGFuZCBNTjIgYmVsb25nIHRvIHRoZSBzYW1lIExNQSwgaXQgcmVxdWVzdHMgdGhlIGFkZHJl
c3Mgb2YgTUFHMiBmcm9tIExNQTINCiAgIGFuZCB1c2VzIHRoYXQgYWRkcmVzcyB0byBzZXR1cCB0
aGUgbG9jYWxpemVkIHJvdXRpbmcgcGF0aCBiZXR3ZWVuDQogICBpdHNlbGYgYW5kIE1BRzIgdmlh
IGEgUHJveHkgQmluZGluZyBVcGRhdGUgKFBCVSkvUHJveHkgQmluZGluZw0KICAgQWNrbm93bGVk
Z2VtZW50IChQQkEpIG1lc3NhZ2UgZXhjaGFuZ2UgW1JGQzUyMTNdLCBOb3RlIHRoYXQgd2hldGhl
ciBNTjENCiBhbmQgTU4yIGJlbG9uZyB0byB0aGUgc2FtZSBMTUEgY2FuIGJlIHZlcmlmaWVkIGJ5
IGxvb2tpbmcgdXAgdGhlIGJpbmRpbmcgY2FjaGUgZW50cmllcyBjb3JyZXNwb25kaW5nIHRvDQog
ICBNTjEgYW5kIE1OMiBhbmQgY29tcGFyaW5nIHRoZSBhZGRyZXNzZXMgb2YgTE1BMSBhbmQgTE1B
Mi4NCiINCjIuIFNlY3Rpb24gNS4yLCBMYXN0IFBhcmFncmFwaCwgMXN0IHNlbnRlbmNlDQpPTEQg
dGV4dDoNCiINCkluIHRoZSBjYXNlIHdoZXJlIE1OcyBzaGFyZSB0aGUgc2FtZSBMTUEsIExSIHNo
b3VsZCBiZSBpbml0aWF0ZWQgYnkNCiAgIExNQTEgKGkuZS4sTE1BMikgc2luY2Ugb25seSBMTUEx
IGtub3dzIHRoYXQgYm90aCBNTjEgYW5kIE1OMiBiZWxvbmcNCiAgIHRvIGl0c2VsZiBieSBsb29r
aW5nIHVwIHRoZSBiaW5kaW5nIGNhY2hlIGVudHJpZXMgY29ycmVzcG9uZGluZyB0bw0KICAgTU4x
IGFuZCBNTjIuIA0KIg0KTmV3IHRleHQ6DQoiDQpJbiB0aGUgY2FzZSB3aGVyZSBNTnMgc2hhcmUg
dGhlIHNhbWUgTE1BLCBMUiBzaG91bGQgYmUgaW5pdGlhdGVkIGJ5DQogICBMTUExIChpLmUuLExN
QTIpIHNpbmNlIG9ubHkgTE1BMSBrbm93cyB0aGF0IGJvdGggTU4xIGFuZCBNTjIgYmVsb25nDQog
ICB0byB0aGUgc2FtZSBMTUEgaW4gYWNjb3JkYW5jZSB3aXRoIHRoZSB2ZXJpZmljYXRpb24gcHJp
bmNpcGxlIHNwZWNpZmllZCBpbiB0aGUgc2VjdGlvbiA1LjEuDQoiDQozLiBTZWN0aW9uIDUuMSwg
TGFzdCBQYXJhZ3JhcGgNCk9MRCB0ZXh0Og0KIg0KLi4uLi5pbnN0ZWFkIHNldHRpbmcgdXAgYSBs
b2NhbGl6ZWQgcm91dGluZyBwYXRoDQogICBkaXJlY3RseSBiZXR3ZWVuIGl0c2VsZiBhbmQgTE1B
MiB2aWEgbG9jYWxpemVkIHJvdXRpbmcgc2lnbmFsaW5nLg0KIg0KTmV3IFRleHQ6DQoiDQouLi4g
aW5zdGVhZCBpbml0aWF0aW5nIExNQTEgYW5kIExNQTIgZXhjaGFuZ2UgdG8gdHJpZ2dlciBjb3Jy
ZXNwb25kaW5nIExNQSB0byBzZXR1cCBiaW5kaW5nIGVudHJpZXMNCm9uIHRoZSBjb3JyZXNwb25k
aW5nIE1BRyBmb3IgbG9jYWxpemVkIHJvdXRpbmcgYW5kIGNvbmZpZ3VyaW5nIE1BRzEgYW5kIE1B
RzIgdG8gdXNlIHRoZSBzYW1lIGVuY2Fwc3VsYXRpb24gbWVjaGFuaXNtIGFzIHRoYXQNCmJlaW5n
IHVzZWQgZm9yIFBNSVAgdHVubmVsIGJldHdlZW4gTUFHIGFuZCBMTUEgd2l0aG91dCBzcGVjaWFs
IGNvbmZpZ3VyYXRpb24gb3IgZHluYW1pYyB0dW5uZWxpbmcgbmVnb3RpYXRpb24gYmV0d2VlbiBN
QUdzLg0KQWx0ZXJuYXRpdmVseSBzcGVjaWFsIGNvbmZpZ3VyYXRpb24gZm9yIG90aGVyIGVuY2Fw
c3VsYXRpb24gbWVjaGFuaXNtIG9yIGR5bmFtaWMgdHVubmVsaW5nIG5lZ290aWF0aW9uIG1heSBi
ZSB1c2VkIHRvIG92ZXJyaWRlDQp0aGUgZGVmYXVsdCB0dW5uZWxpbmcuDQoNCiINCg0KUmVnYXJk
cyENCi1RaW4NCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCreivP7I
yzogUnVzcyBIb3VzbGV5IFtob3VzbGV5QHZpZ2lsc2VjLmNvbV0NCreiy83KsbzkOiAyMDEyxOoy
1MIxM8jVIDU6MjINCrW9OiBRaW4gV3UNCkNjOiBHZW5lcmFsIEFyZWEgUmV2aWV3IFRlYW07IGRy
YWZ0LWlldGYtZGltZS1wbWlwNi1sci5hbGxAdG9vbHMuaWV0Zi5vcmc7IEVsd3luIERhdmllcw0K
1vfM4jogUmU6IFtHZW4tYXJ0XSBHZW4tYXJ0IHJldmlldyBvZiBkcmFmdC1pZXRmLWRpbWUtcG1p
cDYtbHItMDcNCg0KVGhlIC0wNyB2ZXJzaW9uIG9mIHRoaXMgZG9jdW1lbnQgaXMgb24gdGhlIElF
U0cgdGVsZWNoYXQgdGhpcyB3ZWVrLiAgSG93IHdpbGwgdGhlIGFncmVlZCBjaGFuZ2VzIGJlIG1h
ZGU/DQoNClJ1c3MNCg0KDQpPbiBGZWIgOCwgMjAxMiwgYXQgNzoyOCBBTSwgRWx3eW4gRGF2aWVz
IHdyb3RlOg0KDQo+IEhpLCBRaW4uDQo+DQo+IEZpbmUgLSBJIHRoaW5rIGFsbCB3aWxsIGJlIGdv
b2QgZnJvbSBteSBwb2ludCBvZiB2aWV3IGlmIHlvdSBzYXkgYSBmZXcNCj4gd29yZHMgYWJvdXQg
bGlua2luZyB0aGUgTUFHcyBhcyBwZXIgeW91ciBsYXN0IHJlc3BvbnNlIGJlbHdvdy4NCj4NCj4g
Q2hlZXJzLA0KPiBFbHd5bg0KPg0KPiBPbiBXZWQsIDIwMTItMDItMDggYXQgMTk6NDcgKzA4MDAs
IFFpbiBXdSB3cm90ZToNCj4+IEhpLCBFbHd5bjoNCj4+IFRoYW5rIGZvciB5b3VyIGZvbGxvd3Vw
IGNvbW1lbnRzLCBwbGVhc2Ugc2VlIG15IHJlcGxpZXMgaW5saW5lLg0KPj4NCj4+IFJlZ2FyZHMh
DQo+PiAtUWluDQo+PiAtLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tDQo+PiBGcm9tOiAiRWx3
eW4gRGF2aWVzIiA8ZWx3eW5kQGRpYWwucGlwZXguY29tPg0KPj4gVG86ICJRaW4gV3UiIDxiaWxs
Lnd1QGh1YXdlaS5jb20+DQo+PiBDYzogIkdlbmVyYWwgQXJlYSBSZXZpZXcgVGVhbSIgPGdlbi1h
cnRAaWV0Zi5vcmc+OyA8ZHJhZnQtaWV0Zi1kaW1lLXBtaXA2LWxyLmFsbEB0b29scy5pZXRmLm9y
Zz4NCj4+IFNlbnQ6IFdlZG5lc2RheSwgRmVicnVhcnkgMDgsIDIwMTIgNjo1OCBQTQ0KPj4gU3Vi
amVjdDogUmU6IFtHZW4tYXJ0XSBHZW4tYXJ0IHJldmlldyBvZiBkcmFmdC1pZXRmLWRpbWUtcG1p
cDYtbHItMDcNCj4+DQo+Pg0KPj4+IEhpLCBRaW4uDQo+Pj4NCj4+PiBUaGFua3MgZm9yIHlvdXIg
cXVpY2sgcmVwb25zZS4uIHNvbWUgY29tbWVudHMgaW4gbGluZSAoSSBoYXZlIGRlbGV0ZWQNCj4+
PiB0aGUgYml0cyBhZ3JlZWQpLA0KPj4+DQo+Pj4gL0Vsd3luDQo+Pj4NCj4+PiBPbiBGcmksIDIw
MTItMDItMDMgYXQgMTI6NTMgKzA4MDAsIFFpbiBXdSB3cm90ZToNCj4+Pj4gSGksRWx3eW46DQo+
Pj4+IFRoYW5rIGZvciB5b3VyIHZhbHVhYmxlIHJldmlldy4gcGxlYXNlIHNlZSBvdXIgcmVwbGll
cyBiZWxvdy4NCj4+Pj4gLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLQ0KPj4+PiBGcm9tOiAi
RWx3eW4gRGF2aWVzIiA8ZGF2aWVzZWJAc2Nzcy50Y2QuaWU+DQo+Pj4+IFRvOiAiR2VuZXJhbCBB
cmVhIFJldmlldyBUZWFtIiA8Z2VuLWFydEBpZXRmLm9yZz4NCj4+Pj4gQ2M6IDxkcmFmdC1pZXRm
LWRpbWUtcG1pcDYtbHIuYWxsQHRvb2xzLmlldGYub3JnPg0KPj4+PiBTZW50OiBUaHVyc2RheSwg
RmVicnVhcnkgMDIsIDIwMTIgOTowNiBQTQ0KPj4+PiBTdWJqZWN0OiBHZW4tYXJ0IHJldmlldyBv
ZiBkcmFmdC1pZXRmLWRpbWUtcG1pcDYtbHItMDcNCj4+Pj4NCj4+Pj4NCj4+Pj4+IEkgYW0gdGhl
IGFzc2lnbmVkIEdlbi1BUlQgcmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQuIEZvciBiYWNrZ3JvdW5k
IG9uDQo+Pj4+PiBHZW4tQVJULCBwbGVhc2Ugc2VlIHRoZSBGQVEgYXQNCj4+Pj4+IDwgaHR0cDov
L3dpa2kudG9vbHMuaWV0Zi5vcmcvYXJlYS9nZW4vdHJhYy93aWtpL0dlbkFydGZhcT4uDQo+Pj4+
Pg0KPj4+Pj4gUGxlYXNlIHdhaXQgZm9yIGRpcmVjdGlvbiBmcm9tIHlvdXIgZG9jdW1lbnQgc2hl
cGhlcmQNCj4+Pj4+IG9yIEFEIGJlZm9yZSBwb3N0aW5nIGEgbmV3IHZlcnNpb24gb2YgdGhlIGRy
YWZ0Lg0KPj4+Pj4NCj4+Pj4+IERvY3VtZW50OiBkcmFmdC1pZXRmLWRpbWUtcG1pcDYtbHItMDcu
dHh0DQo+Pj4+PiBSZXZpZXdlcjogRWx3eW4gRGF2aWVzDQo+Pj4+PiBSZXZpZXcgRGF0ZTogMiBG
ZWJydWFyeSAyMDEyDQo+Pj4+PiBJRVRGIExDIEVuZCBEYXRlOiAyNCBKYW51YXJ5IDIwMTINCj4+
Pj4+IElFU0cgVGVsZWNoYXQgZGF0ZTogMTYgRmVicnVhcnkgMjAxMg0KPj4+Pj4NCj4+Pj4+IFN1
bW1hcnk6DQo+Pj4+PiBJIGhhdmUgYSBjb3VwbGUgb2YgcXVlcmllcy9taW5vciBpc3N1ZXMgcmVn
YXJkaW5nIGNoZWNraW5nIHdoZXRoZXIgTE1BMQ0KPj4+Pj4gYW5kIExNQTIgYXJlIHRoZSBzYW1l
IG5vZGUgYW5kIHNvbWUgaGFuZCB3YXZpbmcgb3ZlciB0aGUgaWRlYSBvZg0KPj4+Pj4gJ2xvY2Fs
aXplZCByb3V0aW5nIHNldHVwL3NpZ25hbGlpbmcnLiAgVGhlcmUgYXJlIGFsc28gYSBmZXcgbWlu
b3Igbml0cy4NCj4+Pj4+IE90aGVyd2lzZSB0aGlzIGlzIHJlYWR5IGZvciB0aGUgSUVTRy4NCj4+
Pj4+DQo+Pj4+PiBbVGhpcyBkb2N1bWVudCBtaXNzZWQgdGhlIG5vcm1hbCBnZW4tYXJ0IGxhc3Qg
Y2FsbCBhbGxvY2F0aW9uDQo+Pj4+PiBub3RpZmljYXRpb24gbWVjaGFuaXNtIGZvciBzb21lIHJl
YXNvbiAtIHNvIEkgZGlkbid0IHJlYWxpemUgaXQgd2FzIG9uDQo+Pj4+PiBteSBhbGxvY2F0aW9u
IHRpbGwgdGhlIGVuZCBvZiBsYXN0IGNhbGwgYW5kIGFzIGEgcmVzdWx0IHRoZSByZXZpZXcgaXMg
YQ0KPj4+Pj4gYml0IGxhdGUuXQ0KPj4+Pj4NCj4+Pj4+IE1ham9yIGlzc3VlczoNCj4+Pj4+IE5v
bmUNCj4+Pj4+DQo+Pj4+PiBNaW5vciBpc3N1ZXM6DQo+Pj4+PiBzNS4xLCBwYXJhIDMgYW5kIHM1
LjIsIGxhc3QgcGFyYToNCj4+Pj4+IEluIHM1LjE6DQo+Pj4+Pj4gTUFHMSBjYW4gdmVyaWZ5DQo+
Pj4+Pj4gICB3aGV0aGVyIGJvdGggTUFHcyBhcmUgdW5kZXIgdGhlIHNhbWUgTE1BIGJ5IGNvbXBh
cmluZyB0aGUgYWRkcmVzc2VzDQo+Pj4+Pj4gICBvZiBMTUExIGFuZCBMTUEyLg0KPj4+Pj4gSXMg
dGhpcyBndWFyYW50ZWVkIHRvIHdvcms/ICBTaG91bGQgd2UgY2FyZT8gT3IgaXMgdGhpcyBqdXN0
IHRvbyBiYWQgaWYNCj4+Pj4+IHRoZSBMTUEgaGFzIG11bHRpcGxlIGFkZHJlc3NlcyBhbmQgdGhl
IHR3byBNTnMgaGF2ZSBkaWZmZXJlbnQgaWRlYXM/DQo+Pj4+DQo+Pj4+IFtRaW5dOiBJbiB0aGUg
ZXhhbXBsZSBkZXNjcmliZWQgaW4gdGhlIHM1LjEsIHdlIGRvbid0IGNvbnNpZGVyIG9uZSBMTUEg
aGFzIHR3byBMTUEgYWRkcmVzcy4NCj4+Pj4gTE1BMSBhbmQgTE1BMiBtYXkgcmVwcmVzZW50IHR3
byBkaWZmZXJlbnQgbW9iaWxpdHkgZW50aXRpZXMgaWRlbnRpZmllZCBieSBMTUExIGFkcmVzcyBh
bmQgTE1BMiBhZHJlc3MgcmVzcGVjdGl2ZWx5Lg0KPj4+PiBJZiBMTUExIGFkZHJlc3MgaXMgTE1B
MiBhZGRyZXNzLCB0aGlzIGp1c3QgaW5kaWNhdGUgTE1BMSBhbmQgTE1BMiBhcmUgdGhlIHNhbWUg
bW9iaWxpdHkgZW50aXR5Lg0KPj4+PiBFdmVuIG9uZSBMTUEgaGF2ZSBtb3JlIHRoYW4gb25lIExN
QSBhZGRyZXNzLCB0aGlzIHN0aWxsIHdvcmsgc2luY2UgTUFHIGNhbiBrbm93IGlmIHRoZXNlIExN
QSBhZGRyZXNzZXMgY29tZSBmcm9tDQo+Pj4+IHRoZSBzYW1lIG1vYmlsaXR5IGVudGl0eSBiYXNl
ZCBvbiBNTjEgYW5kIE1OMidzIGJpbmRpbmcgdXBkYXRlIGxpc3QuDQo+Pj4+DQo+Pj4+PiBIb3dl
dmVyIGluIHM1LjI6DQo+Pj4+Pj4gSW4gdGhlIGNhc2Ugd2hlcmUgTU5zIHNoYXJlIHRoZSBzYW1l
IExNQSwgTFIgc2hvdWxkIGJlIGluaXRpYXRlZCBieQ0KPj4+Pj4+ICAgTE1BMSAoaS5lLixMTUEy
KSBzaW5jZSBvbmx5IExNQTEga25vd3MgdGhhdCBib3RoIE1OMSBhbmQgTU4yIGJlbG9uZw0KPj4+
Pj4+ICAgdG8gaXRzZWxmIGJ5IGxvb2tpbmcgdXAgdGhlIGJpbmRpbmcgY2FjaGUgZW50cmllcyBj
b3JyZXNwb25kaW5nIHRvDQo+Pj4+Pj4gICBNTjEgYW5kIE1OMi4NCj4+Pj4+IEkgYW0gdW5zdXJl
IHdoZXRoZXIgdGhlc2UgdHdvIHN0YXRlbWVudHMgYXJlIHRhbGtpbmcgYWJvdXQgdGhlIHNhbWUN
Cj4+Pj4+IHRoaW5nIC0gYW5kLCBpZiBzbywgYXJlIHRoZXkgY29udHJhZGljdG9yeT8NCj4+Pj4+
DQo+Pj4+DQo+Pj4+IFtRaW5dOiBObyBDb25mbGljdGlvbiwgU2VlIGFib3ZlLg0KPj4+DQo+Pj4g
SSB0aGluayB0aGlzIGlzIGV4YWN0bHkgdGhlIHBvaW50OiBZb3UgZ2l2ZSB0d28gZGlmZmVyZW50
IChidXQgYWxsZWdlZGx5DQo+Pj4gbm9uLWNvbmZsaWN0aW5nIHdheXMpIG9mIGRvaW5nIHRoZSBz
YW1lIHRoaW5nIGF0IHR3byBwbGFjZXMgaW4gdGhlDQo+Pj4gZHJhZnQuICBGcm9tIHdoYXQgeW91
IHNheSwgSSBpbmZlciB0aGF0IHlvdSBjb3VsZCBkbyBlaXRoZXIgdGhpbmcgaW4NCj4+PiBib3Ro
IGNhc2VzLiBJZiBzbyB0aGVuIGl0IHdvdWxkIGJlIGJldHRlciB0byBnaXZlIHRoZSBhbHRlcm5h
dGl2ZXMNCj4+PiB0b2dldGhlciBmb3IgdGhlIGZpcnN0IGNhc2UgYW5kIHJlZmVyIHRvIHRoZSBw
cmV2aW91cyBjb21tZW50cyB3aGVuIHRoZQ0KPj4+IHNlY29uZCBjYXNlIGlzIHJlYWNoZWQgaW4g
dGhlIHRleHQuDQo+Pg0KPj4gW1Fpbl06IEdvb2Qgc3VnZ2VzdGlvbiBhbmQgd2lsbCBmb2xsb3cg
dGhpcy4NCj4+Pg0KPj4+Pg0KPj4+Pj4gczUuMSwgbGFzdCBwYXJhOg0KPj4+Pj4+IEZpZ3VyZSA0
IHNob3dzIGFub3RoZXIgZXhhbXBsZSBzY2VuYXJpbywgc2ltaWxhciB0byB0aGUgZXhhbXBsZQ0K
Pj4+Pj4+ICAgc2NlbmFyaW8gaWxsdXN0cmF0ZWQgaW4gRmlndXJlIDMsIExNQTEgZG9lcyBub3Qg
cmVzcG9uZCB0byBNQUcxIHdpdGgNCj4+Pj4+PiAgIHRoZSBhZGRyZXNzIG9mIExNQTIsIGluc3Rl
YWQgc2V0dGluZyB1cCBhIGxvY2FsaXplZCByb3V0aW5nIHBhdGgNCj4+Pj4+PiAgIGRpcmVjdGx5
IGJldHdlZW4gaXRzZWxmIGFuZCBMTUEyIHZpYSBsb2NhbGl6ZWQgcm91dGluZyBzaWduYWxpbmcu
DQo+Pj4+PiBJIGFtIHVuc3VyZSB3aGF0ICdsb2NhbGl6ZWQgcm91dGluZyBzaWduYWxpaW5nJyB3
b3VsZCBpbnZvbHZlLiAgV2hhdA0KPj4+Pj4gd291bGQgdGhlIG5vZGVzIGRvIGZvciB0aGlzPyAg
QXBwZWFycyB0byBpbnZvbHZlIHNvbWUgd2F2aW5nIG9mIGhhbmRzLg0KPj4+Pg0KPj4+PiBbUWlu
XTogTE1BMSBhbmQgTE1BMiBleGNoYW5nZSB0byB0cmlnZ2VyIGNvcnJlc3BvbmRpbmcgTE1BIHRv
IHNldHVwIGJpbmRpbmcgZW50cmllcw0KPj4+PiBvbiB0aGUgY29ycmVzcG9kaW5nIE1BRyBmb3Ig
bG9jYWxpemVkIHJvdXRpbmcgYW5kIGVzdGFibGlzaCBsb2NhbGl6ZWQNCj4+Pj4gcm91dGluZyBw
YXRoIGJldHdlZW4gTUFHMSBhbmQgTUFHMi4NCj4+Pj4NCj4+Pj4+IE9uIGEgc2xpZ2h0bHkgYnJv
YWRlciBwb2ludCwgdGhlcmUgYXJlIGEgbnVtYmVyIG9mIHBsYWNlcyB3aGVyZSB0aGUNCj4+Pj4+
IHBocmFzZSAnbG9jYWxpemVkIHJvdXRpbmcgc2V0dXAnIChvciBzaW1pbGFyKSBpcyB1c2VkLiAg
SXQgd291bGQsIEkNCj4+Pj4+IHRoaW5rLCBiZSB1c2VmdWwgdG8gYWRkIGEgZmV3IHdvcmRzIGlu
ZGljYXRpbmcgd2hhdCBpcyB0aG91Z2h0IHRvIGJlDQo+Pj4+PiBpbnZvbHZlZCBhbHRob3VnaCBh
Y3R1YWxseSBkb2luZyBpdCBpcyBjbGVhcmx5IG91dCBvZiBzY29wZSBvZiB0aGlzDQo+Pj4+PiBk
b2N1bWVudC4NCj4+Pj4NCj4+Pj4gW1Fpbl06IE9rYXkuDQo+Pj4NCj4+PiBJIGFtIGFmcmFpZCB0
aGlzIGRvZXNuJ3QgcmVhbGx5IGhlbHA6IFlvdSBzYXkgJ2VzdGFibGlzaCBsb2NhbGl6ZWQNCj4+
PiByb3V0aW5nIHBhdGggYmV0d2VlbiBNQUcxIGFuZCBNQUcyJy4gSG93PyBEb2VzIHRoaXMgaW1w
bHkgdGhhdCB0aGUgTUFHDQo+Pj4gb3Igc29tZSBvdGhlciBjb21wb25lbnQgd2lsbCAocmUtKWNv
bmZpZ3VyZSB0aGUgbG9jYWwgcGFja2V0IHJvdXRpbmcNCj4+PiBpbmZyYXN0cnVjdHVyZT8gKE5v
dCBzb21ldGhpbmcgSSB3b3VsZCBleHBlY3QgdGhlIE1BRyB0byBiZSBhdXRob3JpemVkDQo+Pj4g
dG8gZG8uKSBPciBpcyB0aGlzIGEgbWF0dGVyIG9mIGNyZWF0aW5nIGEgdHVubmVsPyAgSSB0aGlu
ayB0aGlzIG5lZWRzIHRvDQo+Pj4gYmUgYSB3aG9sZSBsb3QgbW9yZSBjb25jcmV0ZSAtIGJvdGgg
ZW5kcyBoYXZlIHRvIGJlIGV4cGVjdGluZyB0aGUNCj4+PiBwYWNrZXRzIGFuZCBrbm93IHdoYXQg
dG8gZG8gd2l0aCB0aGVtLg0KPj4NCj4+IFtRaW5dOiBZZXMsIHlvdXIgYXJlIHJpZ2h0LiBUdW5u
ZWxpbmcgYmV0d2VlbiBNQUcxIGFuZCBNQUcyIHNob3VsZCBiZSBjb25maWd1cmVkIG9uIGJvdGgg
TUFHcy4NCj4+IEFzIGRlZmF1bHQgc3RhdGljIGJlaGF2aW9yLHR1bm5lbCBiZXR3ZWVuIE1BRzEg
YW5kIE1BRzIgdXNlcyB0aGUgc2FtZSBlbmNhcHN1bGF0aW9uIG1lY2hhbmlzbQ0KPj4gYXMgdGhh
dCBiZWluZyB1c2VkIGZvciBQTUlQIHR1bm5lbCBiZXR3ZWVuIE1BRyBhbmQgTE1BLiBJbiB0aGlz
IGNhc2UsIE1BRzEgYW5kIE1BRzINCj4+IGNhbiBzdGFydCB1c2luZyB0aGUgc2FtZSB0dW5uZWxp
bmcgbWVjaGFuaXNtIHdpdGhvdXQgc3BlY2lhbCBjb25maWd1cmF0aW9uIChlLmcudXNpbmcgb3Ro
ZXINCj4+IHR1bm5lbCBtZWNoYW5pc20gdGhhdCBpcyB1bmlmb3JtIGluIHRoZSBQTUlQIGRvbWFp
bikgb24gTUFHcyBvciBkeW5hbWljIHR1bm5lbGluZyBuZWdvdGlhdGlvbiBiZXR3ZWVuIE1BR3Mu
DQo+PiBidXQgc3BlY2lhbCBjb25maWd1cmF0aW9uIG9uIE1BR3Mgb3IgZHluYW1pYyB0dW5uZWwg
bmVnb3RpYXRpb24gY2FuIG92ZXJpZGUNCj4+IHRoZSBkZWZhdWx0IHN0YXRpYyBiZWhhdmlvciBt
ZW50aW9uZWQgYWJvdmUgaWYgdGhleSBhcmUgcmVhbGx5IG5lZWRlZC4NCj4+DQo+PiBIb3BlIHRo
aXMgY2xhcmlmaWVzLg0KPj4NCj4+PiBSZWdhcmRzLA0KPj4+IEVsd3luDQo+Pj4NCj4+Pg0KPg0K
PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBHZW4t
YXJ0IG1haWxpbmcgbGlzdA0KPiBHZW4tYXJ0QGlldGYub3JnDQo+IGh0dHBzOi8vd3d3LmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vZ2VuLWFydA==

From miguel.a.garcia@ericsson.com  Mon Feb 13 00:05:50 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 C649021F85F9 for <gen-art@ietfa.amsl.com>; Mon, 13 Feb 2012 00:05:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.225
X-Spam-Level: 
X-Spam-Status: No, score=-10.225 tagged_above=-999 required=5 tests=[AWL=0.374, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1pVJ1DfPkNeX for <gen-art@ietfa.amsl.com>; Mon, 13 Feb 2012 00:05:49 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id 7CF5221F8617 for <gen-art@ietf.org>; Mon, 13 Feb 2012 00:05:49 -0800 (PST)
X-AuditID: c1b4fb3d-b7bb7ae0000007b2-45-4f38c45adba4
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 87.5E.01970.A54C83F4; Mon, 13 Feb 2012 09:05:46 +0100 (CET)
Received: from [159.107.24.213] (153.88.115.8) by esessmw0197.eemea.ericsson.se (153.88.115.88) with Microsoft SMTP Server id 8.3.213.0; Mon, 13 Feb 2012 09:05:46 +0100
Message-ID: <4F38C459.4040704@ericsson.com>
Date: Mon, 13 Feb 2012 09:05:45 +0100
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:10.0) Gecko/20120129 Thunderbird/10.0
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <7F2072F1E0DE894DA4B517B93C6A05852C3D31BA1E@ESESSCMS0356.eemea.ericsson.se>
In-Reply-To: <7F2072F1E0DE894DA4B517B93C6A05852C3D31BA1E@ESESSCMS0356.eemea.ericsson.se>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Cc: "draft-ietf-simple-chat.all@tools.ietf.org" <draft-ietf-simple-chat.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>, Ben Campbell <ben@nostrum.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-simple-chat-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: Mon, 13 Feb 2012 08:05:50 -0000

Hi Christer,

Thanks for your comments, I agree with most of them. Allow me to answer a 
couple of issues of disagreements.

 > - Requirements
 > -- REQ-4: Isn't this requirement already covered by REQ-3?

No. Req-3 claims for a mechanism for the recipient of a message to 
determine whether the receive message is private or regular.

Req-4 claims for the a mechanism to send private messages.


 > - There is no definition/reference for "roster".

Roster is a not a technical term. According to the Merriam-Webster 
dictionary, there are two entrances for "roster":

1
   a : a roll or list of personnel
   b : such a list giving the order in which a duty is to be performed <a 
duty roster> c : the persons listed on a roster

2: an itemized list

I think the term is clear when we use it in the context of a conference 
with participants.



/Miguel



On 11/02/2012 11:13, Christer Holmberg 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-simple-chat-13
> Reviewer:                   Christer Holmberg
> Review Date:              12-02.11
> IETF LC End Date:     12-02-06
> IESG Telechat date: (if known)
>
> Summary:          Ready, but some additional text may be needed based on the minor issues.
>
> Major issues:     None
>
> Minor issues:
>
> - The second paragraph of section 7.1 says that a NICKNAME request MUST contain a Use-Nickname header, but in the sixth paragraph the inclusion is a SHOULD.
>
> - It is not clearly indicated whether the Use-Nickname header is allowed for other methods than NICKNAME.
>
> - Section 8 does not specify whether there are SDP offer/answer considerations/restrictions associated with the new attribute. For example:
> -- Must the attribute tokens in an answer be a subset of the tokens in an offer?
> -- Can an SDP answer contain an attribute if the offer didn't?
> -- If a user sends a new SDP offer within a session, can the token values be modified? What does it mean if the attribute is not present in a new SDP offer?
>
>
> Nits/editorial comments:
>
> - Sometimes the document talks about "multi-party chat", "multi-party conference", "conference", and "chat room". Would it be possible to use more consistant terminology?
>
> - Requirements
> -- REQ-4: Isn't this requirement already covered by REQ-3?
> -- REQ-6: Change "progress" to "duration" or "length".
>
> - There is no definition/reference for "roster".
>
>
> Regards,
>
> Christer
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art
>

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

From christer.holmberg@ericsson.com  Mon Feb 13 00:10:34 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 0FC7521F85A7 for <gen-art@ietfa.amsl.com>; Mon, 13 Feb 2012 00:10:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.255
X-Spam-Level: 
X-Spam-Status: No, score=-9.255 tagged_above=-999 required=5 tests=[AWL=1.344,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X9KCWq6HxvSp for <gen-art@ietfa.amsl.com>; Mon, 13 Feb 2012 00:10:33 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id 19B6321F8675 for <gen-art@ietf.org>; Mon, 13 Feb 2012 00:10:32 -0800 (PST)
X-AuditID: c1b4fb39-b7bf2ae0000069a1-68-4f38c577deed
Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 41.98.27041.775C83F4; Mon, 13 Feb 2012 09:10:31 +0100 (CET)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.175]) by esessmw0191.eemea.ericsson.se ([153.88.115.84]) with mapi; Mon, 13 Feb 2012 09:10:31 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Miguel Garcia A <miguel.a.garcia@ericsson.com>
Date: Mon, 13 Feb 2012 09:08:09 +0100
Thread-Topic: [Gen-art] Gen-ART review of draft-ietf-simple-chat-13
Thread-Index: AczqJkpUsuCqrJ5QSlGl2NXfQ6DF0AAAFXGf
Message-ID: <7F2072F1E0DE894DA4B517B93C6A05852C3D31BA25@ESESSCMS0356.eemea.ericsson.se>
References: <7F2072F1E0DE894DA4B517B93C6A05852C3D31BA1E@ESESSCMS0356.eemea.ericsson.se>, <4F38C459.4040704@ericsson.com>
In-Reply-To: <4F38C459.4040704@ericsson.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-Brightmail-Tracker: AAAAAA==
Cc: "draft-ietf-simple-chat.all@tools.ietf.org" <draft-ietf-simple-chat.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>, Ben Campbell <ben@nostrum.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-simple-chat-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: Mon, 13 Feb 2012 08:10:34 -0000

Hi,

> > - Requirements
>> -- REQ-4: Isn't this requirement already covered by REQ-3?
>
> No. Req-3 claims for a mechanism for the recipient of a message to
> determine whether the receive message is private or regular.
>
> Req-4 claims for the a mechanism to send private messages.

True. I didn't realize Req-3 was related to the recipient.

>> - There is no definition/reference for "roster".
>
> Roster is a not a technical term. According to the Merriam-Webster
> dictionary, there are two entrances for "roster":
>
> 1
>   a : a roll or list of personnel
>   b : such a list giving the order in which a duty is to be performed <a
> duty roster> c : the persons listed on a roster
>
> 2: an itemized list
>
> I think the term is clear when we use it in the context of a conference
> with participants.

Ok.

Regards,

Christer





On 11/02/2012 11:13, Christer Holmberg 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-simple-chat-13
> Reviewer:                   Christer Holmberg
> Review Date:              12-02.11
> IETF LC End Date:     12-02-06
> IESG Telechat date: (if known)
>
> Summary:          Ready, but some additional text may be needed based on =
the minor issues.
>
> Major issues:     None
>
> Minor issues:
>
> - The second paragraph of section 7.1 says that a NICKNAME request MUST c=
ontain a Use-Nickname header, but in the sixth paragraph the inclusion is a=
 SHOULD.
>
> - It is not clearly indicated whether the Use-Nickname header is allowed =
for other methods than NICKNAME.
>
> - Section 8 does not specify whether there are SDP offer/answer considera=
tions/restrictions associated with the new attribute. For example:
> -- Must the attribute tokens in an answer be a subset of the tokens in an=
 offer?
> -- Can an SDP answer contain an attribute if the offer didn't?
> -- If a user sends a new SDP offer within a session, can the token values=
 be modified? What does it mean if the attribute is not present in a new SD=
P offer?
>
>
> Nits/editorial comments:
>
> - Sometimes the document talks about "multi-party chat", "multi-party con=
ference", "conference", and "chat room". Would it be possible to use more c=
onsistant terminology?
>
> - Requirements
> -- REQ-4: Isn't this requirement already covered by REQ-3?
> -- REQ-6: Change "progress" to "duration" or "length".
>
> - There is no definition/reference for "roster".
>
>
> Regards,
>
> Christer
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art
>

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

From Francis.Dupont@fdupont.fr  Mon Feb 13 06:56:40 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 B889821F859E for <gen-art@ietfa.amsl.com>; Mon, 13 Feb 2012 06:56:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.582
X-Spam-Level: 
X-Spam-Status: No, score=-2.582 tagged_above=-999 required=5 tests=[AWL=0.017,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Oq1o253JfGsw for <gen-art@ietfa.amsl.com>; Mon, 13 Feb 2012 06:56:40 -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 8D15221F8595 for <gen-art@ietf.org>; Mon, 13 Feb 2012 06:56:39 -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 q1DEubl6006711; Mon, 13 Feb 2012 15:56:38 +0100 (CET) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201202131456.q1DEubl6006711@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: gen-art@ietf.org
Date: Mon, 13 Feb 2012 15:56:37 +0100
Sender: Francis.Dupont@fdupont.fr
Cc: draft-weil-shared-transition-space-request.all@tools.ietf.org
Subject: [Gen-art] (re)review of draft-weil-shared-transition-space-request-14.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: Mon, 13 Feb 2012 14:56:40 -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-weil-shared-transition-space-request-14.txt
Reviewer: Francis Dupont
Review Date: 20120208
IETF LC End Date: 20120216
IESG Telechat date: 20120216

Summary: Ready

Major issues: None

Minor issues: None (but with proposed changes agreed during the (last)
last call applied)

Nits/editorial comments:
 - 1 page 4: the CPE abbrev is not well known so should be introduced
  (or marked as well known as there are more and more documents in this
   area)

 - 4 page 7: my dictionary says the word proscription exists only singular,
  i.e., proscriptions -> proscription

Personal comments:
 - I am in favor of this document (as explained by some in the IETF ML,
  other solutions are worse)
 - I have no illusion about how it will be applied in the real world
 - this document and many others about CGN/LSN make the dangerous
  assumption there will be only one level of CGN/LSN
 - to delay the application of the document (i.e., the allocation of
   the shared address space) long enough there will be no /10
   available should be a very unfair way to (not) solve the problem (:-)

Regards

Francis.Dupont@fdupont.fr

From ben@nostrum.com  Mon Feb 13 12: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 0878A21E802A; Mon, 13 Feb 2012 12:37:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.512
X-Spam-Level: 
X-Spam-Status: No, score=-102.512 tagged_above=-999 required=5 tests=[AWL=0.088, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qTR9jmPo2784; Mon, 13 Feb 2012 12:37:15 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 049A221E8029; Mon, 13 Feb 2012 12:37:14 -0800 (PST)
Received: from dn3-53.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q1DKbCd5031086 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 13 Feb 2012 14:37:13 -0600 (CST) (envelope-from ben@nostrum.com)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <282BBE8A501E1F4DA9C775F964BB21FE3EC1467FB2@GRFMBX704BA020.griffon.local>
Date: Mon, 13 Feb 2012 14:37:26 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <7A76A706-9B9C-4911-A4E6-AEC187385557@nostrum.com>
References: <A57C4722-5E13-451E-ACB4-CAA8064FA68B@nostrum.com> <282BBE8A501E1F4DA9C775F964BB21FE3EC1467FB2@GRFMBX704BA020.griffon.local>
To: Maglione Roberta <roberta.maglione@telecomitalia.it>
X-Mailer: Apple Mail (2.1257)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: "'Henderickx, Wim \(Wim\)'" <wim.henderickx@alcatel-lucent.com>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, Ullio Mario <mario.ullio@telecomitalia.it>, "draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org" <draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org>, The IETF <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-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: Mon, 13 Feb 2012 20:37:16 -0000

Hi, thanks for the response. See additional comments inline. (I removed =
sections for which no further comment seems necessary)

On Feb 10, 2012, at 7:52 AM, Maglione Roberta wrote:

[...]

>=20
> -- I admit to not being a DHCP expert, but If I understand this draft =
correctly, it proposes to send what is effectively a secret-key in a =
DHCPACK request, then use that key to authenticate a force renew =
message. It seems like any eavesdropper could sniff that key, and use it =
to spoof force renew requests. The introduction mentions that there may =
be some environments where the use of RFC3118 authentication could be =
relaxed, and offers an example of such an environment. But nowhere does =
this draft appear to be limited in scope to such environments.
>=20
> [RM] The intention is to use this method only for environments with =
native security mechanisms, such as the Broadband Access network. You =
are right it is not clearly said in the document I can add the following =
sentence at the end of the introduction in order to clarify this point:
>=20
> "This   mechanism is intended to be use in networks that already have =
native security mechanisms that provide sufficient protection against
> spoofing of DHCP traffic."

That helps, although I would suggest an additional sentence mentioning =
the specific risk in using it in environments without sufficient =
protection. I note, however, that Ted objected to this in a separate =
email--I will reply there as well.

>=20
>=20
> I think some additional text in (perhaps in the security =
considerations) is needed to explain either why the vulnerability to =
eavesdroppers is either okay in general, or limits the mechanism's use =
to environment where it is okay. It also seems like that, in the best =
case, this mechanism proves only that a Forcerenew request comes from =
the same DHCP server as in the original transaction, but otherwise does =
not prove anything about the identity of that server. If so, it would be =
worth mentioning it.
>=20
> [RM] That's correct this mechanism only proves only that a Forcerenew =
request comes from the same DHCP server: let me say this is a trade off =
between the total security provided by RFC 3118 and no security at all. =
In addition this method relays on the same mechanism already used for =
DHCPv6 Reconfigure message

Understood, and your suggested text from the previous comment mitigates =
this a bit. It would help to include text describing exactly what =
security properties you expect from the mechanism. (e.g. Proving (with =
limitations) that Forcerenew requests come from the same server as the =
original transaction response, etc.)

>=20
> -- The mechanism appears to be limited to HMAC-MD5, and there does not =
appear to be any way of selecting other algorithms. Is HMAC-MD5 really =
sufficient as the only choice? Is there some expectation that stronger =
mechanisms or algorithm extensibility would be too expensive? (Perhaps =
the extensibility method would be to specify another mechanism that's =
identical except for a different HMAC algorithm. But if that's the =
intent it should be mentioned.)
> [RM] This is because this mechanism relays on the authentication =
protocol defined in section 21.5 of RFC 3315 for DHCPv6 Reconfigure and =
there HMAC-MD5 is used.

RFC 3315 was published in 2003. I'm not sure the general impression of =
HMACMD5 is the same now as it was in 2003. For example, =
http://www.ietf.org/mail-archive/web/cfrg/current/msg01197.html . I'm =
willing to accept that HMACMD5 is perfectly okay for this application, =
but it would be good to document more motivation than the fact it was =
used in 3315. If 3315 was being written today, would they use it? Is =
matching 3315 an important goal? I'm more interested in whether HMACMD5 =
is adequate for this particular use case based on today's knowledge =
about possible vulnerabilities or operational issues.

[I mentioned in my original review that I think this draft should get a =
SecDir review. They could certainly access whether hmacmd5 is an issue =
better than I can.]

>=20
> *** Minor issues:
>=20

[...]

>=20
> -- section 3.1.3, 2nd paragraph: "The server SHOULD NOT include this =
option unless the client has indicated its capability in a DHCP =
Discovery message."
>=20
> Why not; what harm would it do? And on the other hand, if you want to =
discourage it, why not go all the way to "MUST NOT"?
>=20
> [RM] For backward compatibility: if the client did not indicate its =
capability for this feature it means it is a legacy client and it does =
not support it, so the server should not send the nonce to this client

The text is not talking about sending the nonce--it's talking about =
sending the FORCERENEW_NONCE_CAPABLE option. Unless I read it wrong, it =
is saying the server SHOULD not advertise support unless the client has =
already indicated support.

>=20
> -- section 3.1.3, 5th paragraph: "...  computes an HMAC-MD5 of the =
Forcerenew message using the Forcerenew nonce ."
>=20
> Using it how? Is it the secret key for the HMAC calculation? (If so, =
why aren't we calling it a "key" in the first place?)
> [RM] based on the procedure specified in section 21.5 of RFC 3315

It would help to say that in the text.

[...]

>=20
>=20
> -- section 3.1.4, 4th paragraph: ".
> the client computes an HMAC-MD5 over the DHCP Forcerenew message, =
using the Forcerenew Nonce ."
>=20
> Using it how?
> [RM] based on the procedure specified in section 21.5 of RFC 3315
>=20

It would help to say that in the text.

> -- section 6:
>=20
> You mention this mechanism is vulnerable to MiTM attacks. Why is this =
okay? Are there some environments where it is good enough and others =
where it is not? (Also, do they really need to be MitM attackers? Seems =
like any eavesdropper could learn the nonce.)
>=20

You did not address this in your response. I think the "why is this =
okay" part is probably covered by other discussion, but the "do they =
really need to be MitM" question remains.


[...]=

From ben@nostrum.com  Mon Feb 13 13:06:07 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 DBBE921E8012; Mon, 13 Feb 2012 13:06:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.518
X-Spam-Level: 
X-Spam-Status: No, score=-102.518 tagged_above=-999 required=5 tests=[AWL=0.082, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iXXocE7lCV4m; Mon, 13 Feb 2012 13:06:06 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id E77B321E8022; Mon, 13 Feb 2012 13:06:05 -0800 (PST)
Received: from dn3-53.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q1DL62Q6035903 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 13 Feb 2012 15:06:02 -0600 (CST) (envelope-from ben@nostrum.com)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <CEA6CD8F-7DCD-448C-8C31-EC64FD9902A3@nominum.com>
Date: Mon, 13 Feb 2012 15:06:16 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <F184B794-3D1D-4A5A-860E-288DF2600DD6@nostrum.com>
References: <A57C4722-5E13-451E-ACB4-CAA8064FA68B@nostrum.com> <282BBE8A501E1F4DA9C775F964BB21FE3EC1467FB2@GRFMBX704BA020.griffon.local> <CEA6CD8F-7DCD-448C-8C31-EC64FD9902A3@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1257)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: The IETF <ietf@ietf.org>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org" <draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org>, Ullio Mario <mario.ullio@telecomitalia.it>, "Henderickx, Wim \(Wim\)" <wim.henderickx@alcatel-lucent.com>, Maglione Roberta <roberta.maglione@telecomitalia.it>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-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: Mon, 13 Feb 2012 21:06:07 -0000

On Feb 11, 2012, at 10:24 AM, Ted Lemon wrote:

>> [RM] The intention is to use this method only for environments with =
native security mechanisms, such as the Broadband Access network. You =
are right it is not clearly said in the document I can add the following =
sentence at the end of the introduction in order to clarify this point:
>>=20
>> "This   mechanism is intended to be use in networks that already have =
native security mechanisms that provide sufficient protection against
>> spoofing of DHCP traffic."
>=20
> It's probably worth revisiting the purpose of this mechanism.   The =
problem that we are trying to solve is that people are reluctant to =
implement DHCPFORCERENEW because it's possible that an off-link attacker =
could more accurately guess the timing of DHCP renewal messages by first =
sending a DHCPFORCERENEW.   The mechanism in RFC3315 (DHCPv6), which =
this document mirrors for DHCPv4, uses a nonce to prevent an off-link =
attacker from successfully triggering a renewal on a client by sending =
DHCPFORCERENEW; since the attacker is off-link, it doesn't have the =
nonce, and can't force a renewal.
>=20
> An on-link attacker can always simply watch the DHCP renewal message =
go out and respond to it, so this mechanism is useless for preventing =
on-link attacks, and hence the security of the nonce in the case of =
on-link attacks isn't relevant.  So the above text isn't needed.   It's =
possible that the document doesn't clearly document the use case for =
this functionality; if so, you are free to take the above paragraph, =
Roberta, and modify it to suit your purposes.   But I am against adding =
the text you proposed, because it excludes the bulk of use cases for the =
DHCPFORCERENEW nonce mechanism.

This is good information, and it would help to include it in the =
security considerations. I meant (but failed) to  comment in my original =
review that the security considerations would benefit from a more =
detailed discussion about the properties of the mechanism, and what =
attacks or vulnerabilities it is intended to mitigate. Your text above =
seems to do that.

>=20
>> [RM] This is because this mechanism relays on the authentication =
protocol defined in section 21.5 of RFC 3315 for DHCPv6 Reconfigure and =
there HMAC-MD5 is used.
>=20
> Essentially HMAC-MD5 is being used here to package a secret into a =
chunk of predictable size, and the fact that there are hacks for the =
mechanism isn't terribly important because the only attacker we are =
attempting to foil is one that doesn't have access to the cleartext or =
the ciphertext.

Do I infer correctly from your comment that the security properties of =
the mechanism don't really matter? That is, if the attacker we care =
about can't eavesdrop in the first place, does this really need to be an =
HMAC?=

From Ted.Lemon@nominum.com  Mon Feb 13 13:21:34 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 7F30B21E8038; Mon, 13 Feb 2012 13:21:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.523
X-Spam-Level: 
X-Spam-Status: No, score=-106.523 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AXwrF-XhHwXh; Mon, 13 Feb 2012 13:21:33 -0800 (PST)
Received: from exprod7og104.obsmtp.com (exprod7og104.obsmtp.com [64.18.2.161]) by ietfa.amsl.com (Postfix) with ESMTP id 741C021E802A; Mon, 13 Feb 2012 13:21:33 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob104.postini.com ([64.18.6.12]) with SMTP ID DSNKTzl+3AWBTH+ZBzbE8y6S311ALaG6upRI@postini.com; Mon, 13 Feb 2012 13:21:33 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 6C0861B81E4; Mon, 13 Feb 2012 13:21:32 -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 63025190052; Mon, 13 Feb 2012 13:21:32 -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.01.0339.001; Mon, 13 Feb 2012 13:21:32 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Ben Campbell <ben@nostrum.com>
Thread-Topic: Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-03
Thread-Index: AQHM5SWUy8EqSdK3C0aOhQFr8l21aJY2slwAgAG8tQCAA3NmAIAABEKA
Date: Mon, 13 Feb 2012 21:21:32 +0000
Message-ID: <EADDD673-E8FF-4579-9996-1E15C8933A70@nominum.com>
References: <A57C4722-5E13-451E-ACB4-CAA8064FA68B@nostrum.com> <282BBE8A501E1F4DA9C775F964BB21FE3EC1467FB2@GRFMBX704BA020.griffon.local> <CEA6CD8F-7DCD-448C-8C31-EC64FD9902A3@nominum.com> <F184B794-3D1D-4A5A-860E-288DF2600DD6@nostrum.com>
In-Reply-To: <F184B794-3D1D-4A5A-860E-288DF2600DD6@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: multipart/alternative; boundary="_000_EADDD673E8FF457999961E15C8933A70nominumcom_"
MIME-Version: 1.0
Cc: The IETF <ietf@ietf.org>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org" <draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org>, Ullio Mario <mario.ullio@telecomitalia.it>, "Henderickx, Wim \(Wim\)" <wim.henderickx@alcatel-lucent.com>, Maglione Roberta <roberta.maglione@telecomitalia.it>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-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: Mon, 13 Feb 2012 21:21:34 -0000

--_000_EADDD673E8FF457999961E15C8933A70nominumcom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

On Feb 13, 2012, at 4:06 PM, Ben Campbell wrote:
Do I infer correctly from your comment that the security properties of the =
mechanism don't really matter? That is, if the attacker we care about can't=
 eavesdrop in the first place, does this really need to be an HMAC?

Hm, I thought about that a bit more after I wrote my response.   The HMAC a=
llows us to avoid sending the nonce in the clear in the DHCPFORCERENEW.   I=
 don't think this adds any value from a security perspective, actually, eve=
n though it feels more comfortable.   I suspect it was put in in the origin=
al version simply because of that=97why send a secret over the wire when yo=
u don't have to?   However, the original motivation for using the mechanism=
 from RFC3315 was to avoid defining a new mechanism for a legacy protocol. =
  If we do need to change it, it's going to require a major rework of the d=
ocument, and a lot of delay, so if it causes no harm, I think that's not wo=
rth doing.

I too would like to see the text I proposed added to the security considera=
tions, so that we can be clear about what is being accomplished with this d=
raft.


--_000_EADDD673E8FF457999961E15C8933A70nominumcom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <7B06EB66C931E64DA8CFADC779C71AD5@nominum.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<div>On Feb 13, 2012, at 4:06 PM, Ben Campbell wrote:</div>
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; ">Do
 I infer correctly from your comment that the security properties of the me=
chanism don't really matter? That is, if the attacker we care about can't e=
avesdrop in the first place, does this really need to be an HMAC?</span></b=
lockquote>
</div>
<br>
<div>Hm, I thought about that a bit more after I wrote my response. &nbsp; =
The HMAC allows us to avoid sending the nonce in the clear in the DHCPFORCE=
RENEW. &nbsp; I don't think this adds any value from a security perspective=
, actually, even though it feels more comfortable.
 &nbsp; I suspect it was put in in the original version simply because of t=
hat=97why send a secret over the wire when you don't have to? &nbsp; Howeve=
r, the original motivation for using the mechanism from RFC3315 was to avoi=
d defining a new mechanism for a legacy protocol.
 &nbsp; If we do need to change it, it's going to require a major rework of=
 the document, and a lot of delay, so if it causes no harm, I think that's =
not worth doing.</div>
<div><br>
</div>
<div>I too would like to see the text I proposed added to the security cons=
iderations, so that we can be clear about what is being accomplished with t=
his draft.</div>
<div><br>
</div>
</body>
</html>

--_000_EADDD673E8FF457999961E15C8933A70nominumcom_--

From ben@nostrum.com  Mon Feb 13 13:25: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 4ABD421E803A; Mon, 13 Feb 2012 13:25:15 -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, HTML_MESSAGE=0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WLuApz9pbQM9; Mon, 13 Feb 2012 13:25:14 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 71D0F21E8038; Mon, 13 Feb 2012 13:25:14 -0800 (PST)
Received: from dn3-53.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q1DLP3Fp038815 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 13 Feb 2012 15:25:08 -0600 (CST) (envelope-from ben@nostrum.com)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: multipart/alternative; boundary="Apple-Mail=_FD17B377-A142-41D5-8A0D-80B8A1583758"
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <EADDD673-E8FF-4579-9996-1E15C8933A70@nominum.com>
Date: Mon, 13 Feb 2012 15:25:01 -0600
Message-Id: <D332B6D7-8855-44EE-8952-CACACCFE211D@nostrum.com>
References: <A57C4722-5E13-451E-ACB4-CAA8064FA68B@nostrum.com> <282BBE8A501E1F4DA9C775F964BB21FE3EC1467FB2@GRFMBX704BA020.griffon.local> <CEA6CD8F-7DCD-448C-8C31-EC64FD9902A3@nominum.com> <F184B794-3D1D-4A5A-860E-288DF2600DD6@nostrum.com> <EADDD673-E8FF-4579-9996-1E15C8933A70@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1257)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: The IETF <ietf@ietf.org>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org" <draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org>, Ullio Mario <mario.ullio@telecomitalia.it>, "Henderickx, Wim \(Wim\)" <wim.henderickx@alcatel-lucent.com>, Maglione Roberta <roberta.maglione@telecomitalia.it>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-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: Mon, 13 Feb 2012 21:25:15 -0000

--Apple-Mail=_FD17B377-A142-41D5-8A0D-80B8A1583758
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Feb 13, 2012, at 3:21 PM, Ted Lemon wrote:

> On Feb 13, 2012, at 4:06 PM, Ben Campbell wrote:
>> Do I infer correctly from your comment that the security properties =
of the mechanism don't really matter? That is, if the attacker we care =
about can't eavesdrop in the first place, does this really need to be an =
HMAC?
>=20
> Hm, I thought about that a bit more after I wrote my response.   The =
HMAC allows us to avoid sending the nonce in the clear in the =
DHCPFORCERENEW.   I don't think this adds any value from a security =
perspective, actually, even though it feels more comfortable.   I =
suspect it was put in in the original version simply because of that=97why=
 send a secret over the wire when you don't have to?   However, the =
original motivation for using the mechanism from RFC3315 was to avoid =
defining a new mechanism for a legacy protocol.   If we do need to =
change it, it's going to require a major rework of the document, and a =
lot of delay, so if it causes no harm, I think that's not worth doing.

I concur it's probably not worth changing at this point--but it does =
inform the "is MD5 good enough" discussion, which might make it worth =
mentioning in the security considerations.

>=20
> I too would like to see the text I proposed added to the security =
considerations, so that we can be clear about what is being accomplished =
with this draft.
>=20


--Apple-Mail=_FD17B377-A142-41D5-8A0D-80B8A1583758
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Feb 13, 2012, at 3:21 PM, Ted Lemon wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite">

<meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3DWindows-1252">

<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">
<div>
<div>On Feb 13, 2012, at 4:06 PM, Ben Campbell wrote:</div>
<blockquote type=3D"cite"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; font-family: Helvetica; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">Do
 I infer correctly from your comment that the security properties of the =
mechanism don't really matter? That is, if the attacker we care about =
can't eavesdrop in the first place, does this really need to be an =
HMAC?</span></blockquote>
</div>
<br>
<div>Hm, I thought about that a bit more after I wrote my response. =
&nbsp; The HMAC allows us to avoid sending the nonce in the clear in the =
DHCPFORCERENEW. &nbsp; I don't think this adds any value from a security =
perspective, actually, even though it feels more comfortable.
 &nbsp; I suspect it was put in in the original version simply because =
of that=97why send a secret over the wire when you don't have to? &nbsp; =
However, the original motivation for using the mechanism from RFC3315 =
was to avoid defining a new mechanism for a legacy protocol.
 &nbsp; If we do need to change it, it's going to require a major rework =
of the document, and a lot of delay, so if it causes no harm, I think =
that's not worth doing.</div></div></blockquote><div><br></div><div>I =
concur it's probably not worth changing at this point--but it does =
inform the "is MD5 good enough" discussion, which might make it worth =
mentioning in the security considerations.</div><br><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; ">
<div><br>
</div>
<div>I too would like to see the text I proposed added to the security =
considerations, so that we can be clear about what is being accomplished =
with this draft.</div>
<div><br>
</div>
</div>

</blockquote></div><br></body></html>=

--Apple-Mail=_FD17B377-A142-41D5-8A0D-80B8A1583758--

From housley@vigilsec.com  Mon Feb 13 14:52:48 2012
Return-Path: <housley@vigilsec.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 0189F21E8010 for <gen-art@ietfa.amsl.com>; Mon, 13 Feb 2012 14:52:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.039
X-Spam-Level: 
X-Spam-Status: No, score=-100.039 tagged_above=-999 required=5 tests=[AWL=-2.496, BAYES_00=-2.599, FRT_BELOW2=2.154, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, SARE_SUB_ENC_UTF8=0.152, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nwK8XNM3Ji+q for <gen-art@ietfa.amsl.com>; Mon, 13 Feb 2012 14:52:47 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id DBC7621F84C8 for <gen-art@ietf.org>; Mon, 13 Feb 2012 14:52:46 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id EA01AF24052; Mon, 13 Feb 2012 17:53:07 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id UFyM98zUgp+f; Mon, 13 Feb 2012 17:52:32 -0500 (EST)
Received: from [192.168.2.104] (pool-96-241-165-215.washdc.fios.verizon.net [96.241.165.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 2DF8BF24024; Mon, 13 Feb 2012 17:53:06 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=GB2312
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <B8F9A780D330094D99AF023C5877DABA1BED33E9@szxeml523-mbs.china.huawei.com>
Date: Mon, 13 Feb 2012 17:52:43 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <A2D5BBF5-654A-4B75-B2FD-0FF0B2B26732@vigilsec.com>
References: <1328187998.4790.2946.camel@mightyatom.folly.org.uk> <BB94D1B3E4CD4E1BA7107AF5A99D19BE@china.huawei.com> <1328698730.4345.364.camel@mightyatom.folly.org.uk> <BF80F6B7104742079DDF846CD4863A4D@china.huawei.com> <1328704106.4345.410.camel@mightyatom.folly.org.uk> <41C110BA-F7A1-4E81-A48D-9114A6286901@vigilsec.com> <B8F9A780D330094D99AF023C5877DABA1BED33E9@szxeml523-mbs.china.huawei.com>
To: Qin Wu <bill.wu@huawei.com>
X-Mailer: Apple Mail (2.1084)
Cc: General Area Review Team <gen-art@ietf.org>, "draft-ietf-dime-pmip6-lr.all@tools.ietf.org" <draft-ietf-dime-pmip6-lr.all@tools.ietf.org>
Subject: Re: [Gen-art] =?utf-8?b?562U5aSNOiAgR2VuLWFydCByZXZpZXcgb2YgZHJhZnQt?= =?utf-8?q?ietf-dime-pmip6-lr-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, 13 Feb 2012 22:52:48 -0000

You should make them when the sponsoring AD indicates.  I do not know if =
other changes are expected based on other reviews.

Russ


On Feb 12, 2012, at 5:32 PM, Qin Wu wrote:

> Hi, Russ:
> Should I address these comments before IESG telechat?
> My response may be limited due to business trip in my next week. Here =
is my proposed changes to version 07.
>=20
> 1.Section 5.1, 3rd paragraph, last sentence.
> OLD text:
> "
> MAG1 can verify
>   whether both MAGs are under the same LMA by comparing the addressese
>   of LMA1 and LMA2.  MAG1 then requests the address of MAG2 from LMA2
>   and uses that address to setup the localized routing path between
>   itself and MAG2 via a Proxy Binding Update (PBU)/Proxy Binding
>   Acknowledgement (PBA) message exchange [RFC5213].
> "
> NEW text:
> "
> If  MAG1 knows that MN1 and MN2 belong to the same LMA, it requests =
the address of MAG2 from LMA2
>   and uses that address to setup the localized routing path between
>   itself and MAG2 via a Proxy Binding Update (PBU)/Proxy Binding
>   Acknowledgement (PBA) message exchange [RFC5213], Note that whether =
MN1
> and MN2 belong to the same LMA can be verified by looking up the =
binding cache entries corresponding to
>   MN1 and MN2 and comparing the addresses of LMA1 and LMA2.
> "
> 2. Section 5.2, Last Paragraph, 1st sentence
> OLD text:
> "
> In the case where MNs share the same LMA, LR should be initiated by
>   LMA1 (i.e.,LMA2) since only LMA1 knows that both MN1 and MN2 belong
>   to itself by looking up the binding cache entries corresponding to
>   MN1 and MN2.=20
> "
> New text:
> "
> In the case where MNs share the same LMA, LR should be initiated by
>   LMA1 (i.e.,LMA2) since only LMA1 knows that both MN1 and MN2 belong
>   to the same LMA in accordance with the verification principle =
specified in the section 5.1.
> "
> 3. Section 5.1, Last Paragraph
> OLD text:
> "
> .....instead setting up a localized routing path
>   directly between itself and LMA2 via localized routing signaling.
> "
> New Text:
> "
> ... instead initiating LMA1 and LMA2 exchange to trigger corresponding =
LMA to setup binding entries
> on the corresponding MAG for localized routing and configuring MAG1 =
and MAG2 to use the same encapsulation mechanism as that
> being used for PMIP tunnel between MAG and LMA without special =
configuration or dynamic tunneling negotiation between MAGs.
> Alternatively special configuration for other encapsulation mechanism =
or dynamic tunneling negotiation may be used to override
> the default tunneling.
>=20
> "
>=20
> Regards!
> -Qin
> ________________________________________
> =B7=A2=BC=FE=C8=CB: Russ Housley [housley@vigilsec.com]
> =B7=A2=CB=CD=CA=B1=BC=E4: 2012=C4=EA2=D4=C213=C8=D5 5:22
> =B5=BD: Qin Wu
> Cc: General Area Review Team; =
draft-ietf-dime-pmip6-lr.all@tools.ietf.org; Elwyn Davies
> =D6=F7=CC=E2: Re: [Gen-art] Gen-art review of =
draft-ietf-dime-pmip6-lr-07
>=20
> The -07 version of this document is on the IESG telechat this week.  =
How will the agreed changes be made?
>=20
> Russ
>=20
>=20
> On Feb 8, 2012, at 7:28 AM, Elwyn Davies wrote:
>=20
>> Hi, Qin.
>>=20
>> Fine - I think all will be good from my point of view if you say a =
few
>> words about linking the MAGs as per your last response belwow.
>>=20
>> Cheers,
>> Elwyn
>>=20
>> On Wed, 2012-02-08 at 19:47 +0800, Qin Wu wrote:
>>> Hi, Elwyn:
>>> Thank for your followup comments, please see my replies inline.
>>>=20
>>> Regards!
>>> -Qin
>>> ----- Original Message -----
>>> From: "Elwyn Davies" <elwynd@dial.pipex.com>
>>> To: "Qin Wu" <bill.wu@huawei.com>
>>> Cc: "General Area Review Team" <gen-art@ietf.org>; =
<draft-ietf-dime-pmip6-lr.all@tools.ietf.org>
>>> Sent: Wednesday, February 08, 2012 6:58 PM
>>> Subject: Re: [Gen-art] Gen-art review of draft-ietf-dime-pmip6-lr-07
>>>=20
>>>=20
>>>> Hi, Qin.
>>>>=20
>>>> Thanks for your quick reponse.. some comments in line (I have =
deleted
>>>> the bits agreed),
>>>>=20
>>>> /Elwyn
>>>>=20
>>>> On Fri, 2012-02-03 at 12:53 +0800, Qin Wu wrote:
>>>>> Hi,Elwyn:
>>>>> Thank for your valuable review. please see our replies below.
>>>>> ----- Original Message -----
>>>>> From: "Elwyn Davies" <davieseb@scss.tcd.ie>
>>>>> To: "General Area Review Team" <gen-art@ietf.org>
>>>>> Cc: <draft-ietf-dime-pmip6-lr.all@tools.ietf.org>
>>>>> Sent: Thursday, February 02, 2012 9:06 PM
>>>>> Subject: Gen-art review of draft-ietf-dime-pmip6-lr-07
>>>>>=20
>>>>>=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 wait for direction from your document shepherd
>>>>>> or AD before posting a new version of the draft.
>>>>>>=20
>>>>>> Document: draft-ietf-dime-pmip6-lr-07.txt
>>>>>> Reviewer: Elwyn Davies
>>>>>> Review Date: 2 February 2012
>>>>>> IETF LC End Date: 24 January 2012
>>>>>> IESG Telechat date: 16 February 2012
>>>>>>=20
>>>>>> Summary:
>>>>>> I have a couple of queries/minor issues regarding checking =
whether LMA1
>>>>>> and LMA2 are the same node and some hand waving over the idea of
>>>>>> 'localized routing setup/signaliing'.  There are also a few minor =
nits.
>>>>>> Otherwise this is ready for the IESG.
>>>>>>=20
>>>>>> [This document missed the normal gen-art last call allocation
>>>>>> notification mechanism for some reason - so I didn't realize it =
was on
>>>>>> my allocation till the end of last call and as a result the =
review is a
>>>>>> bit late.]
>>>>>>=20
>>>>>> Major issues:
>>>>>> None
>>>>>>=20
>>>>>> Minor issues:
>>>>>> s5.1, para 3 and s5.2, last para:
>>>>>> In s5.1:
>>>>>>> MAG1 can verify
>>>>>>>  whether both MAGs are under the same LMA by comparing the =
addresses
>>>>>>>  of LMA1 and LMA2.
>>>>>> Is this guaranteed to work?  Should we care? Or is this just too =
bad if
>>>>>> the LMA has multiple addresses and the two MNs have different =
ideas?
>>>>>=20
>>>>> [Qin]: In the example described in the s5.1, we don't consider one =
LMA has two LMA address.
>>>>> LMA1 and LMA2 may represent two different mobility entities =
identified by LMA1 adress and LMA2 adress respectively.
>>>>> If LMA1 address is LMA2 address, this just indicate LMA1 and LMA2 =
are the same mobility entity.
>>>>> Even one LMA have more than one LMA address, this still work since =
MAG can know if these LMA addresses come from
>>>>> the same mobility entity based on MN1 and MN2's binding update =
list.
>>>>>=20
>>>>>> However in s5.2:
>>>>>>> In the case where MNs share the same LMA, LR should be initiated =
by
>>>>>>>  LMA1 (i.e.,LMA2) since only LMA1 knows that both MN1 and MN2 =
belong
>>>>>>>  to itself by looking up the binding cache entries corresponding =
to
>>>>>>>  MN1 and MN2.
>>>>>> I am unsure whether these two statements are talking about the =
same
>>>>>> thing - and, if so, are they contradictory?
>>>>>>=20
>>>>>=20
>>>>> [Qin]: No Confliction, See above.
>>>>=20
>>>> I think this is exactly the point: You give two different (but =
allegedly
>>>> non-conflicting ways) of doing the same thing at two places in the
>>>> draft.  =46rom what you say, I infer that you could do either thing =
in
>>>> both cases. If so then it would be better to give the alternatives
>>>> together for the first case and refer to the previous comments when =
the
>>>> second case is reached in the text.
>>>=20
>>> [Qin]: Good suggestion and will follow this.
>>>>=20
>>>>>=20
>>>>>> s5.1, last para:
>>>>>>> Figure 4 shows another example scenario, similar to the example
>>>>>>>  scenario illustrated in Figure 3, LMA1 does not respond to MAG1 =
with
>>>>>>>  the address of LMA2, instead setting up a localized routing =
path
>>>>>>>  directly between itself and LMA2 via localized routing =
signaling.
>>>>>> I am unsure what 'localized routing signaliing' would involve.  =
What
>>>>>> would the nodes do for this?  Appears to involve some waving of =
hands.
>>>>>=20
>>>>> [Qin]: LMA1 and LMA2 exchange to trigger corresponding LMA to =
setup binding entries
>>>>> on the correspoding MAG for localized routing and establish =
localized
>>>>> routing path between MAG1 and MAG2.
>>>>>=20
>>>>>> On a slightly broader point, there are a number of places where =
the
>>>>>> phrase 'localized routing setup' (or similar) is used.  It would, =
I
>>>>>> think, be useful to add a few words indicating what is thought to =
be
>>>>>> involved although actually doing it is clearly out of scope of =
this
>>>>>> document.
>>>>>=20
>>>>> [Qin]: Okay.
>>>>=20
>>>> I am afraid this doesn't really help: You say 'establish localized
>>>> routing path between MAG1 and MAG2'. How? Does this imply that the =
MAG
>>>> or some other component will (re-)configure the local packet =
routing
>>>> infrastructure? (Not something I would expect the MAG to be =
authorized
>>>> to do.) Or is this a matter of creating a tunnel?  I think this =
needs to
>>>> be a whole lot more concrete - both ends have to be expecting the
>>>> packets and know what to do with them.
>>>=20
>>> [Qin]: Yes, your are right. Tunneling between MAG1 and MAG2 should =
be configured on both MAGs.
>>> As default static behavior,tunnel between MAG1 and MAG2 uses the =
same encapsulation mechanism
>>> as that being used for PMIP tunnel between MAG and LMA. In this =
case, MAG1 and MAG2
>>> can start using the same tunneling mechanism without special =
configuration (e.g.using other
>>> tunnel mechanism that is uniform in the PMIP domain) on MAGs or =
dynamic tunneling negotiation between MAGs.
>>> but special configuration on MAGs or dynamic tunnel negotiation can =
overide
>>> the default static behavior mentioned above if they are really =
needed.
>>>=20
>>> Hope this clarifies.
>>>=20
>>>> Regards,
>>>> Elwyn
>>>>=20
>>>>=20
>>=20
>> _______________________________________________
>> Gen-art mailing list
>> Gen-art@ietf.org
>> https://www.ietf.org/mailman/listinfo/gen-art


From housley@vigilsec.com  Mon Feb 13 15:08:03 2012
Return-Path: <housley@vigilsec.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 6E99221F84F2 for <gen-art@ietfa.amsl.com>; Mon, 13 Feb 2012 15:08:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.495
X-Spam-Level: 
X-Spam-Status: No, score=-102.495 tagged_above=-999 required=5 tests=[AWL=0.104, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9Ey+vwbbHMs1 for <gen-art@ietfa.amsl.com>; Mon, 13 Feb 2012 15:08:02 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id A6F7621F84F1 for <gen-art@ietf.org>; Mon, 13 Feb 2012 15:08:02 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 6EA0DF24049; Mon, 13 Feb 2012 18:08:31 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id lyYknvhRgbpR; Mon, 13 Feb 2012 18:07:47 -0500 (EST)
Received: from [192.168.2.104] (pool-96-241-165-215.washdc.fios.verizon.net [96.241.165.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 9B00CF24024; Mon, 13 Feb 2012 18:08:30 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=windows-1252
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <4F271155.9080001@ogud.com>
Date: Mon, 13 Feb 2012 18:08:01 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <605759DF-CDD9-4B2D-A264-FC88512CEF7C@vigilsec.com>
References: <4f2570c6.11840e0a.6db6.09c6@mx.google.com> <4F271155.9080001@ogud.com>
To: Olafur Gudmundsson <ogud@ogud.com>
X-Mailer: Apple Mail (2.1084)
Cc: draft-ietf-dnsext-ecdsa.all@tools.ietf.org, IETF Gen-ART <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-dnsext-ecdsa-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: Mon, 13 Feb 2012 23:08:03 -0000

I have not seen a updated document to resolve this concern.

Russ


On Jan 30, 2012, at 4:53 PM, Olafur Gudmundsson wrote:

> On 29/01/2012 11:12, Roni Even 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
>> Please resolve these comments along with any other Last Call comments
>> you may receive.
>>=20
>> Document: draft-ietf-dnsext-ecdsa-04
>>=20
>> Reviewer: Roni Even
>>=20
>> Review Date:2012=961=9629
>>=20
>> IETF LC End Date: 2012=962=967
>>=20
>> IESG Telechat date:
>>=20
>> Summary: This draft is almost ready for publication as an =
Informational RFC.
>>=20
>> Major issues:
>>=20
>> The first IANA action is to update
>> http://www.iana.org/assignments/ds-rr-types/ds-rr-types.txt which
>> requires standard action for adding values.
>>=20
>=20
> Grrrrrr, my fault, overlooked that the editors put this text in the
> header of the document.
> WG LC was for standards track document.
>=20
> Please treat this document as standards track.
>=20
>> Minor issues:
>>=20
>> The important note in section 6 talks about the values in the =
examples.
>> I am wondering why not update the document with the correct values =
after
>> the IANA assignments by the RFC editor.
>=20
> Yes, once we have the IANA assigned values we will furnish the =
RFC-editor with better examples.
>=20
>=20
>>=20
>> Nits/editorial comments:
>>=20
>>=20
>>=20
> thanks for the review
>=20
> 	Olafur (document pusher)
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From paul.hoffman@vpnc.org  Mon Feb 13 15:11:11 2012
Return-Path: <paul.hoffman@vpnc.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 25E3D21F85D9 for <gen-art@ietfa.amsl.com>; Mon, 13 Feb 2012 15:11:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.568
X-Spam-Level: 
X-Spam-Status: No, score=-102.568 tagged_above=-999 required=5 tests=[AWL=0.031, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QEAeuExKSiJf for <gen-art@ietfa.amsl.com>; Mon, 13 Feb 2012 15:11:10 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 8F27A21F854B for <gen-art@ietf.org>; Mon, 13 Feb 2012 15:11:05 -0800 (PST)
Received: from [10.20.30.100] (50-0-66-4.dsl.dynamic.fusionbroadband.com [50.0.66.4]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.3) with ESMTP id q1DNB3FG020630 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 13 Feb 2012 16:11:04 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=windows-1252
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <605759DF-CDD9-4B2D-A264-FC88512CEF7C@vigilsec.com>
Date: Mon, 13 Feb 2012 15:11:03 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <32919081-E0A2-4908-B8C7-B72E62B616AD@vpnc.org>
References: <4f2570c6.11840e0a.6db6.09c6@mx.google.com> <4F271155.9080001@ogud.com> <605759DF-CDD9-4B2D-A264-FC88512CEF7C@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.1257)
Cc: draft-ietf-dnsext-ecdsa.all@tools.ietf.org, IETF Gen-ART <gen-art@ietf.org>, Olafur Gudmundsson <ogud@ogud.com>
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-dnsext-ecdsa-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: Mon, 13 Feb 2012 23:11:11 -0000

On Feb 13, 2012, at 3:08 PM, Russ Housley wrote:

> I have not seen a updated document to resolve this concern.

One was not requested. If you need it in order to prevent a DISCUSS, by =
all means let us know and we'll pump one out.

--Paul Hoffman


From paul.hoffman@vpnc.org  Mon Feb 13 17:51:38 2012
Return-Path: <paul.hoffman@vpnc.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 AF5C621F868C for <gen-art@ietfa.amsl.com>; Mon, 13 Feb 2012 17:51:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.569
X-Spam-Level: 
X-Spam-Status: No, score=-102.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K-LE4dViI0nJ for <gen-art@ietfa.amsl.com>; Mon, 13 Feb 2012 17:51:37 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id CF4BF21F8588 for <gen-art@ietf.org>; Mon, 13 Feb 2012 17:51:35 -0800 (PST)
Received: from [10.20.30.100] (50-0-66-4.dsl.dynamic.fusionbroadband.com [50.0.66.4]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.3) with ESMTP id q1E1pURY026761 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 13 Feb 2012 18:51:31 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=windows-1252
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <605759DF-CDD9-4B2D-A264-FC88512CEF7C@vigilsec.com>
Date: Mon, 13 Feb 2012 17:51:30 -0800
Content-Transfer-Encoding: 7bit
Message-Id: <6561D136-6B40-4FDA-A4B1-2AAB7EC2019A@vpnc.org>
References: <4f2570c6.11840e0a.6db6.09c6@mx.google.com> <4F271155.9080001@ogud.com> <605759DF-CDD9-4B2D-A264-FC88512CEF7C@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.1257)
Cc: draft-ietf-dnsext-ecdsa.all@tools.ietf.org, IETF Gen-ART <gen-art@ietf.org>, Olafur Gudmundsson <ogud@ogud.com>
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-dnsext-ecdsa-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: Tue, 14 Feb 2012 01:51:38 -0000

On Feb 13, 2012, at 3:08 PM, Russ Housley wrote:

> I have not seen a updated document to resolve this concern.

You have now. :-)

--Paul Hoffman


From roberta.maglione@telecomitalia.it  Tue Feb 14 02:23:04 2012
Return-Path: <roberta.maglione@telecomitalia.it>
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 31FBD21F86EA; Tue, 14 Feb 2012 02:23:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.248
X-Spam-Level: 
X-Spam-Status: No, score=0.248 tagged_above=-999 required=5 tests=[AWL=0.967,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ytzIAoNR8B2n; Tue, 14 Feb 2012 02:23:03 -0800 (PST)
Received: from GRFEDG702BA020.telecomitalia.it (grfedg702ba020.telecomitalia.it [156.54.233.201]) by ietfa.amsl.com (Postfix) with ESMTP id 19EB321F85B8; Tue, 14 Feb 2012 02:23:03 -0800 (PST)
Received: from GRFHUB702BA020.griffon.local (10.188.101.112) by GRFEDG702BA020.telecomitalia.it (10.188.45.101) with Microsoft SMTP Server (TLS) id 8.2.254.0; Tue, 14 Feb 2012 11:23:01 +0100
Received: from GRFMBX704BA020.griffon.local ([10.188.101.15]) by GRFHUB702BA020.griffon.local ([10.188.101.112]) with mapi; Tue, 14 Feb 2012 11:23:01 +0100
From: Maglione Roberta <roberta.maglione@telecomitalia.it>
To: 'Ben Campbell' <ben@nostrum.com>, Ted Lemon <Ted.Lemon@nominum.com>
Date: Tue, 14 Feb 2012 11:23:00 +0100
Thread-Topic: Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-03
Thread-Index: Aczqk08e6IUgLj+qQM2pFobKJW9qmwAbyLQw
Message-ID: <282BBE8A501E1F4DA9C775F964BB21FE3EC1467FC5@GRFMBX704BA020.griffon.local>
References: <A57C4722-5E13-451E-ACB4-CAA8064FA68B@nostrum.com> <282BBE8A501E1F4DA9C775F964BB21FE3EC1467FB2@GRFMBX704BA020.griffon.local> <CEA6CD8F-7DCD-448C-8C31-EC64FD9902A3@nominum.com> <F184B794-3D1D-4A5A-860E-288DF2600DD6@nostrum.com>
In-Reply-To: <F184B794-3D1D-4A5A-860E-288DF2600DD6@nostrum.com>
Accept-Language: en-US, it-IT
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, it-IT
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Henderickx, Wim \(Wim\)" <wim.henderickx@alcatel-lucent.com>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, Ullio Mario <mario.ullio@telecomitalia.it>, "draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org" <draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org>, The IETF <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-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: Tue, 14 Feb 2012 10:23:04 -0000

Hello Ted and Bell,
 I tried to address both your comments by combining your proposals:
Basically I added the text suggested by Ted in the security considerations =
section and then I slightly modified the introduction in order to clarify t=
he applicability.
I've just posted version -04 that includes these changes together with the =
resolutions of some other comments we received during the review.
Please let me know if you have additional comments.
Thanks,
Regards,
Roberta

-----Original Message-----
From: Ben Campbell [mailto:ben@nostrum.com]
Sent: luned=EC 13 febbraio 2012 22.06
To: Ted Lemon
Cc: Maglione Roberta; draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org; g=
en-art@ietf.org Review Team; The IETF; Henderickx, Wim (Wim); Ullio Mario
Subject: Re: Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-03

On Feb 11, 2012, at 10:24 AM, Ted Lemon wrote:

>> [RM] The intention is to use this method only for environments with nati=
ve security mechanisms, such as the Broadband Access network. You are right=
 it is not clearly said in the document I can add the following sentence at=
 the end of the introduction in order to clarify this point:
>>
>> "This   mechanism is intended to be use in networks that already have na=
tive security mechanisms that provide sufficient protection against
>> spoofing of DHCP traffic."
>
> It's probably worth revisiting the purpose of this mechanism.   The probl=
em that we are trying to solve is that people are reluctant to implement DH=
CPFORCERENEW because it's possible that an off-link attacker could more acc=
urately guess the timing of DHCP renewal messages by first sending a DHCPFO=
RCERENEW.   The mechanism in RFC3315 (DHCPv6), which this document mirrors =
for DHCPv4, uses a nonce to prevent an off-link attacker from successfully =
triggering a renewal on a client by sending DHCPFORCERENEW; since the attac=
ker is off-link, it doesn't have the nonce, and can't force a renewal.
>
> An on-link attacker can always simply watch the DHCP renewal message go o=
ut and respond to it, so this mechanism is useless for preventing on-link a=
ttacks, and hence the security of the nonce in the case of on-link attacks =
isn't relevant.  So the above text isn't needed.   It's possible that the d=
ocument doesn't clearly document the use case for this functionality; if so=
, you are free to take the above paragraph, Roberta, and modify it to suit =
your purposes.   But I am against adding the text you proposed, because it =
excludes the bulk of use cases for the DHCPFORCERENEW nonce mechanism.

This is good information, and it would help to include it in the security c=
onsiderations. I meant (but failed) to  comment in my original review that =
the security considerations would benefit from a more detailed discussion a=
bout the properties of the mechanism, and what attacks or vulnerabilities i=
t is intended to mitigate. Your text above seems to do that.

>
>> [RM] This is because this mechanism relays on the authentication protoco=
l defined in section 21.5 of RFC 3315 for DHCPv6 Reconfigure and there HMAC=
-MD5 is used.
>
> Essentially HMAC-MD5 is being used here to package a secret into a chunk =
of predictable size, and the fact that there are hacks for the mechanism is=
n't terribly important because the only attacker we are attempting to foil =
is one that doesn't have access to the cleartext or the ciphertext.

Do I infer correctly from your comment that the security properties of the =
mechanism don't really matter? That is, if the attacker we care about can't=
 eavesdrop in the first place, does this really need to be an HMAC?

Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle per=
sone indicate. La diffusione, copia o qualsiasi altra azione derivante dall=
a conoscenza di queste informazioni sono rigorosamente vietate. Qualora abb=
iate ricevuto questo documento per errore siete cortesemente pregati di dar=
ne immediata comunicazione al mittente e di provvedere alla sua distruzione=
, Grazie.

This e-mail and any attachments is confidential and may contain privileged =
information intended for the addressee(s) only. Dissemination, copying, pri=
nting or use by anybody else is unauthorised. If you are not the intended r=
ecipient, please delete this message and any attachments and advise the sen=
der by return e-mail, Thanks.


From Ted.Lemon@nominum.com  Tue Feb 14 05:52:58 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 AF07C21F869D; Tue, 14 Feb 2012 05:52:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.625
X-Spam-Level: 
X-Spam-Status: No, score=-105.625 tagged_above=-999 required=5 tests=[AWL=-0.830, BAYES_00=-2.599, HTML_MESSAGE=0.001, LONGWORDS=1.803, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MVobxRrWo+0S; Tue, 14 Feb 2012 05:52:53 -0800 (PST)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171]) by ietfa.amsl.com (Postfix) with ESMTP id AD0C721F8602; Tue, 14 Feb 2012 05:52:50 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob109.postini.com ([64.18.6.12]) with SMTP ID DSNKTzpnL5yiqIkdgypuBVSLf6UZjEJ4Esot@postini.com; Tue, 14 Feb 2012 05:52:51 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 11D6C1B82FC; Tue, 14 Feb 2012 05:52:47 -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 F38CF190052; Tue, 14 Feb 2012 05:52:46 -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.01.0339.001; Tue, 14 Feb 2012 05:52:41 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Maglione Roberta <roberta.maglione@telecomitalia.it>
Thread-Topic: Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-03
Thread-Index: AQHM5SWUy8EqSdK3C0aOhQFr8l21aJY2slwAgAG8tQCAA3NmAIAA3poAgAA6lIA=
Date: Tue, 14 Feb 2012 13:52:40 +0000
Message-ID: <F96A644A-5ABF-47E8-A519-FA6A252FA03B@nominum.com>
References: <A57C4722-5E13-451E-ACB4-CAA8064FA68B@nostrum.com> <282BBE8A501E1F4DA9C775F964BB21FE3EC1467FB2@GRFMBX704BA020.griffon.local> <CEA6CD8F-7DCD-448C-8C31-EC64FD9902A3@nominum.com> <F184B794-3D1D-4A5A-860E-288DF2600DD6@nostrum.com> <282BBE8A501E1F4DA9C775F964BB21FE3EC1467FC5@GRFMBX704BA020.griffon.local>
In-Reply-To: <282BBE8A501E1F4DA9C775F964BB21FE3EC1467FC5@GRFMBX704BA020.griffon.local>
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: multipart/alternative; boundary="_000_F96A644A5ABF47E8A519FA6A252FA03Bnominumcom_"
MIME-Version: 1.0
Cc: Ben Campbell <ben@nostrum.com>, The IETF <ietf@ietf.org>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org" <draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org>, Ullio Mario <mario.ullio@telecomitalia.it>, "Henderickx, Wim \(Wim\)" <wim.henderickx@alcatel-lucent.com>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-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: Tue, 14 Feb 2012 13:52:59 -0000

--_000_F96A644A5ABF47E8A519FA6A252FA03Bnominumcom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

On Feb 14, 2012, at 5:23 AM, Maglione Roberta wrote:
Please let me know if you have additional comments.

Thanks!   I think you should change this text in the introduction:


The mandatory authentication was
   originally motivated by a legitimate security concern whereby in some
   network environments DHCP messages can be spoofed and an attacker
   could more accurately guess the timing of DHCP renewal messages by
   first sending a FORCERENEW message.  However, in some networks native
   security mechanisms already provide sufficient protection against
   spoofing of DHCP traffic.  An example of such network is a Broadband
   Forum TR-101 [TR-101i2] compliant access network.  In such
   environments the mandatory coupling between FORCERENEW and DHCP
   Authentication [RFC3118] can be relaxed and a lighter authentication
   mechanism can be used for the FORCERENEW message.

To this:

[paragraph break]
The motivation for making authentication mandatory in DHCPFORCERENEW was to=
 prevent an off-network attacker from taking advantage of DHCPFORCERENEW to=
 accurately predict the timing of a DHCP renewal.   Without DHCPFORCERENEW,=
 DHCP renewal timing is under the control of the client, and an off-network=
 attacker has no way of predicting when it will happen, since it doesn't ha=
ve access to the exchange between the DHCP client and DHCP server.

However, the requirement to use the DHCP authentication described in RFC311=
8 is more stringent than is required for this use case, and has limited ado=
ption of DHCPFORCERENEW.   RFC3315 defines an authentication protocol using=
 a nonce to prevent off-network attackers from successfully causing clients=
 to renew.   Since the off-network attacker doesn't have access to the nonc=
e, it can't trick the client into renewing at a time of its choosing.

--_000_F96A644A5ABF47E8A519FA6A252FA03Bnominumcom_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <8FBF60972DBA3A448E23142F121884ED@nominum.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<div>On Feb 14, 2012, at 5:23 AM, Maglione Roberta wrote:</div>
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; ">Please
 let me know if you have additional comments.<br>
</span></blockquote>
</div>
<br>
<div>Thanks! &nbsp; I think you should change this text in the introduction=
:</div>
<div><br>
</div>
<div>
<pre style=3D"color: rgb(0, 0, 0); font-style: normal; font-variant: normal=
; font-weight: normal; letter-spacing: normal; line-height: normal; orphans=
: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; wido=
ws: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; word-wrap: break-word; white-space: pre-wrap; ">The mandator=
y authentication was
   originally motivated by a legitimate security concern whereby in some
   network environments DHCP messages can be spoofed and an attacker
   could more accurately guess the timing of DHCP renewal messages by
   first sending a FORCERENEW message.  However, in some networks native
   security mechanisms already provide sufficient protection against
   spoofing of DHCP traffic.  An example of such network is a Broadband
   Forum TR-101 [TR-101i2] compliant access network.  In such
   environments the mandatory coupling between FORCERENEW and DHCP
   Authentication [RFC3118] can be relaxed and a lighter authentication
   mechanism can be used for the FORCERENEW message.</pre>
<div><br>
</div>
</div>
<div>To this:</div>
<div><br>
</div>
<div>[paragraph break]</div>
<div>The motivation for making authentication mandatory in DHCPFORCERENEW w=
as to prevent an off-network attacker from taking advantage of DHCPFORCEREN=
EW to accurately predict the timing of a DHCP renewal. &nbsp; Without DHCPF=
ORCERENEW, DHCP renewal timing is under
 the control of the client, and an off-network attacker has no way of predi=
cting when it will happen, since it doesn't have access to the exchange bet=
ween the DHCP client and DHCP server.</div>
<div><br>
</div>
<div>However, the requirement to use the DHCP authentication described in R=
FC3118 is more stringent than is required for this use case, and has limite=
d adoption of DHCPFORCERENEW. &nbsp; RFC3315 defines an authentication prot=
ocol using a nonce to prevent off-network
 attackers from successfully causing clients to renew. &nbsp; Since the off=
-network attacker doesn't have access to the nonce, it can't trick the clie=
nt into renewing at a time of its choosing.</div>
</body>
</html>

--_000_F96A644A5ABF47E8A519FA6A252FA03Bnominumcom_--

From ben@nostrum.com  Tue Feb 14 12:11:47 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 CFBD621E80E9; Tue, 14 Feb 2012 12:11:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.3
X-Spam-Level: 
X-Spam-Status: No, score=-102.3 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_74=0.6, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xGOUsh+SGZEP; Tue, 14 Feb 2012 12:11:44 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 112D321E80FC; Tue, 14 Feb 2012 12:11:40 -0800 (PST)
Received: from [10.0.1.2] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q1EKBHu1068065 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 14 Feb 2012 14:11:18 -0600 (CST) (envelope-from ben@nostrum.com)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=windows-1252
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <A57C4722-5E13-451E-ACB4-CAA8064FA68B@nostrum.com>
Date: Tue, 14 Feb 2012 14:11:20 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <11343191-B00C-43DD-8C78-A746226C9566@nostrum.com>
References: <A57C4722-5E13-451E-ACB4-CAA8064FA68B@nostrum.com>
To: draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org
X-Mailer: Apple Mail (2.1257)
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>, The IETF <ietf@ietf.org>
Subject: [Gen-art] Followup Gen-ART Review on draft-ietf-dhc-forcerenew-nonce
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, 14 Feb 2012 20:11:50 -0000

Hi,

This is a followup on my Gen-ART review of =
draft-ietf-dhc-forcerenew-nonce-04, based on my previous review of =
version 03. In summary, this version is improved, but I still don't =
think it's ready for publication.


On Feb 6, 2012, at 5:17 PM, Ben Campbell 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
> Please resolve these comments along with any other Last Call comments =
you may receive.
>=20
> Document: draft-ietf-dhc-forcerenew-nonce-03
> Reviewer: Ben Campbell
> Review Date: 2012-02-06
> IETF LC End Date: 2012-02-06
>=20
> Summary:This draft is not quite ready for publication as a proposed =
standard. There are some potentially significant issues that should be =
addressed first.
>=20
> [Note: Hopefully this draft has had or will have a SecDir review, =
since it seems ripe for significant security implications.]
>=20

I didn't see a comment about whether this happened. I still recommend a =
SecDir review if one has not yet occurred.

>=20
> *** Major issues:
>=20
> -- I admit to not being a DHCP expert, but If I understand this draft =
correctly, it proposes to send what is effectively a secret-key in a =
DHCPACK request, then use that key to authenticate a force renew =
message. It seems like any eavesdropper could sniff that key, and use it =
to spoof force renew requests. The introduction mentions that there may =
be some environments where the use of RFC3118 authentication could be =
relaxed, and offers an example of such an environment. But nowhere does =
this draft appear to be limited in scope to such environments.=20
>=20
> I think some additional text in (perhaps in the security =
considerations) is needed to explain either why the vulnerability to =
eavesdroppers is either okay in general, or limits the mechanism's use =
to environment where it is okay. It also seems like that, in the best =
case, this mechanism proves only that a Forcerenew request comes from =
the same DHCP server as in the original transaction, but otherwise does =
not prove anything about the identity of that server. If so, it would be =
worth mentioning it.
>=20

This is improved by some changes to the introduction and the security =
considerations. But I still don't see a clear, normative statement about =
what environments this can be safely used in. I know Ted objected to =
Roberta's specific proposal, but I think to move forward this needs =
_some_ clear, concrete guidance about when to use or not to use it, or =
when 3118 authentication is more appropriate. Don't leave it up to the =
reader to draw the right conclusion.


> -- The mechanism appears to be limited to HMAC-MD5, and there does not =
appear to be any way of selecting other algorithms. Is HMAC-MD5 really =
sufficient as the only choice? Is there some expectation that stronger =
mechanisms or algorithm extensibility would be too expensive? (Perhaps =
the extensibility method would be to specify another mechanism that's =
identical except for a different HMAC algorithm. But if that's the =
intent it should be mentioned.)

There's a statement in the security considerations that "... security of =
the nonce in the case of on-link attacks isn't relevant." It would help =
drive the point home to add something to the effect that "Therefore =
HMAC-MD5 is by definition adequate for the purpose, and there is no need =
for an extensible HMAC mechanism."

>=20
> *** Minor issues:
>=20
> -- Section 1 "=20
> In such environments the mandatory coupling between FORCERENEW and =
DHCP Authentication [RFC3118] can be relaxed."
>=20
> It's not clear to me what connection that assertion has with this =
draft. Is there an intent that the proposed mechanisms be used only in =
such environments? I don't find any language scoping this proposal to =
any particular environment.

See comment under the first "major issue". I still think we need =
normative, concrete guidance about when to use or not to use this =
mechanism.

[...]


>=20
> -- section 3.1.3, 2nd paragraph: "The server SHOULD NOT include this =
option unless the client has indicated its capability in a DHCP =
Discovery message."
>=20
> Why not; what harm would it do? And on the other hand, if you want to =
discourage it, why not go all the way to "MUST NOT"?
>=20

I don't think my comment has been addressed by the discussion so far. I =
understand that the server should not insert a nonce unless the client =
has advertised support--but is it the author's intent that the server =
should not _advertise_ support unless the client has first advertised =
support?

Additionally, this update added the following text to the section:

> The=20
> server SHOULD NOT include the nonce in an ACK when responding to
>    a renew unless a nonce was generated.  This minimizes the number of
>    times the nonce is sent over the wire.


I don't understand the first sentence. Don't include a nonce unless you =
generated it first? That seems like a tautology. Do you mean to say =
unless the nonce was sent in a previous message? Or unless a _new_ nonce =
was generated?

[...]

>=20
> -- section 3.1.4, 1st paragraph: "DHCP servers that support Forcerenew =
nonce Protocol authentication MUST include the DHCP Forcerenew Nonce =
protocol authentication option=85"
>=20
> Only if the client advertised it, right? Otherwise, this seems to =
conflict with the previous SHOULD NOT.

The text is updated, but it still conflicts with the previous statement =
in 3.1.3, paragraph 2 that says the server SHOULD NOT insert the option =
unless the client first inserted it. (See comment above).

[...]


>=20
> -- section 6:
>=20
> You mention this mechanism is vulnerable to MiTM attacks. Why is this =
okay? Are there some environments where it is good enough and others =
where it is not? (Also, do they really need to be MitM attackers? Seems =
like any eavesdropper could learn the nonce.)

The text still refers to a MiTM attacker. Do you mean "on-link" =
attacker?=20

Otherwise, you've added text to motivate the mechanism for a specific =
use case. But I'd still like to see concrete guidance about when this =
draft is appropriate to use.

>=20
> *** Nits/editorial comments:
>=20
> -- Abstract, second sentence:
>=20
> I have trouble parsing this sentence. Are the propositions correct?

Partially fixed. Should "on the initial ACK" be "in the initial ACK"?

>=20
> -- Section 3.1.1,4th paragraph: "=85 configured to require =85"
>=20
> Do you mean configured to "require", or configured to "use"? I would =
normally take "requires" to mean that the server would not work with =
clients that don't advertise support for the mechanism.

You changed the text from "configured to require" to "requires". I'm =
still confused on whether "requires" means that the server will refuse =
to service clients that don't advertise support. This is in contrast to =
"use", which would mean to me the server would invoke the option if the =
client supports it, but still work with clients that don't support it.

[...]


From mccap@petoni.org  Wed Feb 15 11:35:40 2012
Return-Path: <mccap@petoni.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 E00A721E8071 for <gen-art@ietfa.amsl.com>; Wed, 15 Feb 2012 11:35:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L-Ca93LCxqoU for <gen-art@ietfa.amsl.com>; Wed, 15 Feb 2012 11:35:36 -0800 (PST)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6468821E8027 for <gen-art@ietf.org>; Wed, 15 Feb 2012 11:35:36 -0800 (PST)
Received: by ghbg16 with SMTP id g16so1002797ghb.31 for <gen-art@ietf.org>; Wed, 15 Feb 2012 11:35:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=petoni.org; s=google; h=mime-version:x-originating-ip:date:message-id:subject:from:to :content-type; bh=4d9v4/U01BjqNpG8ZbHlvW/B8XEO/O+T9C0KbcUc0Jg=; b=gNua3fLAUsCSAKJghmrLungQI7AwPzZmZOfgth0QuxVu/G8zRQVMLMztrt6SI6INi+ ZYd/rqc+Su99AK8mggyO9or6QnuZVpxIkUxK5q7mk6gVu99TmLrSG1s5zlPxrnMMBekU UewNYtQ00A4tNDZ6GAEoyz0LNln4FIOmECxhY=
MIME-Version: 1.0
Received: by 10.60.12.103 with SMTP id x7mr2881156oeb.51.1329334535931; Wed, 15 Feb 2012 11:35:35 -0800 (PST)
Received: by 10.60.13.102 with HTTP; Wed, 15 Feb 2012 11:35:35 -0800 (PST)
X-Originating-IP: [166.137.14.243]
Date: Wed, 15 Feb 2012 14:35:35 -0500
Message-ID: <CACvMsLEciyGLDKe5S4iGLNsfXSybKHrkKYixVMi07DW2_aWQbw@mail.gmail.com>
From: Pete McCann <mccap@petoni.org>
To: gen-art@ietf.org, draft-ietf-dhc-pd-exclude.all@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [Gen-art] Gen-ART Telechat Review of draft-ietf-dhc-pd-exclude-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, 15 Feb 2012 19:35:41 -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-dhc-pd-exclude-04
Reviewer: Peter McCann
Review Date: 2012-02-15
IETF LC End Date:
IESG Telechat date: 2012-02-16

Summary: Ready

Major issues: None

Minor issues:

Might want to point out that when the requesting router sends router
advertisements downstream,
it cannot simply advertise the whole delegated prefix but must instead
advertise chunks of it that
do not include the excluded prefix.  This may introduce complications
and extra overhead.

Nits/editorial comments: None

From jouni.nospam@gmail.com  Wed Feb 15 12:34:00 2012
Return-Path: <jouni.nospam@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 AD9A221F865E for <gen-art@ietfa.amsl.com>; Wed, 15 Feb 2012 12:34:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.324
X-Spam-Level: 
X-Spam-Status: No, score=-3.324 tagged_above=-999 required=5 tests=[AWL=0.275,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ALVQycAg2dgg for <gen-art@ietfa.amsl.com>; Wed, 15 Feb 2012 12:33:56 -0800 (PST)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3BC9421F8646 for <gen-art@ietf.org>; Wed, 15 Feb 2012 12:33:55 -0800 (PST)
Received: by lahl5 with SMTP id l5so1678119lah.31 for <gen-art@ietf.org>; Wed, 15 Feb 2012 12:33:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=AJj3vauumKWEgmV2RNN0ZW7Ctr8jHNNOIynxFyc01v8=; b=DVCy/yShW2flQevef6bhtFQytcQL8RLzZJBtZpEGc3YlylbcXKb9j2kESAKhzNp4Wy xg889fHK5Eeknh3BALO7ionqT0C0byTGReJ3MKv6s68wnh2qYjhhO7bQX2ulLghf2d/t l4w0eIFVZHNrkLmrDSuMrolKYjbn2beMhLgOU=
Received: by 10.112.54.38 with SMTP id g6mr692207lbp.43.1329338032164; Wed, 15 Feb 2012 12:33:52 -0800 (PST)
Received: from a83-245-213-3.elisa-laajakaista.fi (a83-245-213-3.elisa-laajakaista.fi. [83.245.213.3]) by mx.google.com with ESMTPS id j4sm4482979lbf.6.2012.02.15.12.33.49 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 15 Feb 2012 12:33:49 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: jouni korhonen <jouni.nospam@gmail.com>
In-Reply-To: <CACvMsLEciyGLDKe5S4iGLNsfXSybKHrkKYixVMi07DW2_aWQbw@mail.gmail.com>
Date: Wed, 15 Feb 2012 22:33:47 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <D368DD9B-B864-4F26-BA60-8B974633E4F2@gmail.com>
References: <CACvMsLEciyGLDKe5S4iGLNsfXSybKHrkKYixVMi07DW2_aWQbw@mail.gmail.com>
To: Pete McCann <mccap@petoni.org>
X-Mailer: Apple Mail (2.1084)
Cc: gen-art@ietf.org, draft-ietf-dhc-pd-exclude.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART Telechat Review of draft-ietf-dhc-pd-exclude-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, 15 Feb 2012 20:34:00 -0000

Pete,

Thanks for the review. Agree that in general having a hole in otherwise 
continuous prefix is guaranteed to cause always some undesired side effects.

Regarding sending RAs I don't this it will be much of an issue, though.
Assuming SLAAC is used, then the requesting router would anyway be sending
a /64 in each RA on its downstream interfaces, thus chopping the delegated
prefix into a number of smaller prefixes. And if each downstream interface
have their own /64 prefix, then including a summary prefix shorter than /64
does not really work.

- Jouni

On Feb 15, 2012, at 9:35 PM, Pete McCann 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-dhc-pd-exclude-04
> Reviewer: Peter McCann
> Review Date: 2012-02-15
> IETF LC End Date:
> IESG Telechat date: 2012-02-16
> 
> Summary: Ready
> 
> Major issues: None
> 
> Minor issues:
> 
> Might want to point out that when the requesting router sends router
> advertisements downstream,
> it cannot simply advertise the whole delegated prefix but must instead
> advertise chunks of it that
> do not include the excluded prefix.  This may introduce complications
> and extra overhead.
> 
> Nits/editorial comments: None


From mahoney@nostrum.com  Thu Feb 16 15:37: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 F3E7B21E8081 for <gen-art@ietfa.amsl.com>; Thu, 16 Feb 2012 15:37:06 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lzelU9q3XKJ0 for <gen-art@ietfa.amsl.com>; Thu, 16 Feb 2012 15:37:02 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id C907321E806E for <gen-art@ietf.org>; Thu, 16 Feb 2012 15:37:00 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-71-170-125-181.dllstx.fios.verizon.net [71.170.125.181]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q1GNb0a6093947 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 16 Feb 2012 17:37:00 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <4F3D931C.1000101@nostrum.com>
Date: Thu, 16 Feb 2012 17:37:00 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
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: 71.170.125.181 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2012-02-16
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, 16 Feb 2012 23:37:07 -0000

Hi all,

Here's the link to the new LC assignments:
http://wiki.tools.ietf.org/dav/genart/reviewers-120216-lc.html

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


And 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 miguel.a.garcia@ericsson.com  Fri Feb 17 00:39:47 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 C1F9F21F8883 for <gen-art@ietfa.amsl.com>; Fri, 17 Feb 2012 00:39:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.322
X-Spam-Level: 
X-Spam-Status: No, score=-10.322 tagged_above=-999 required=5 tests=[AWL=0.277, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NNxyjT9fzKp8 for <gen-art@ietfa.amsl.com>; Fri, 17 Feb 2012 00:39:47 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id BB73B21F887E for <gen-art@ietf.org>; Fri, 17 Feb 2012 00:39:46 -0800 (PST)
X-AuditID: c1b4fb39-b7bf2ae0000069a1-5b-4f3e12518e88
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id B6.CF.27041.1521E3F4; Fri, 17 Feb 2012 09:39:45 +0100 (CET)
Received: from [159.107.24.194] (153.88.115.8) by esessmw0237.eemea.ericsson.se (153.88.115.91) with Microsoft SMTP Server id 8.3.213.0; Fri, 17 Feb 2012 09:39:45 +0100
Message-ID: <4F3E124F.40603@ericsson.com>
Date: Fri, 17 Feb 2012 09:39:43 +0100
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1
MIME-Version: 1.0
To: darlewis@cisco.com, dmm@cisco.com, dino@cisco.com, vaf@cisco.com,  terry.manderson@icann.org, Jari Arkko <jari.arkko@piuha.net>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Cc: General Area Review Team <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-lisp-interworking-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, 17 Feb 2012 08:39:47 -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-lisp-interworking-03.txt
Reviewer: Miguel Garcia <miguel.a.garcia@ericsson.com>
Review Date: 2012-02-17
IETF LC End Date: 2012-02-23
IESG Telechat date: 2012-03-01

Summary: The document is ready for publication as an experimental RCFc.

Major issues: none

Minor issues: none

Nits/editorial comments:

- Section 5.2 describes a sequence of packet flows. I think it would be 
easier to understand if there is a companion figure to which the text can 
refer to. Otherwise, the reader has to compose this figure in his mind.

- Please expand acronyms at first occurrence. This includes: RLOC, CRIO

- Perhaps the terminology section should include RLOC, xTR, ETR, ITR, DFZ

- Idnits reveals a number of unused references: LIPS-MS, RFC4632, 
LISP-DEPLOY, RFC4787, RFC5382. They should be deleted.

- Idnits reveals an obsolete reference: RFC 2434 (Obsoleted by RFC 5226)

- Idnits reveals a number of instances where IP addresses are not 
compliant with RFC 5735. I am trying to identify which ones of these are. 
I guess they are the 220.x.x.x, 128.x.x.x EIDs. I think most of them are 
technically EIDs for LISP-NR, LISP-R LISP-NAT, etc. I don't know if RFC 
5735 applies to this draft or not, I am just letting you know in case you 
need to fix something.

BR,

      Miguel


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

From jari.arkko@piuha.net  Fri Feb 17 00:55:33 2012
Return-Path: <jari.arkko@piuha.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 32A3221F88B0 for <gen-art@ietfa.amsl.com>; Fri, 17 Feb 2012 00:55:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.559
X-Spam-Level: 
X-Spam-Status: No, score=-102.559 tagged_above=-999 required=5 tests=[AWL=0.040, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yUKZffr18NPA for <gen-art@ietfa.amsl.com>; Fri, 17 Feb 2012 00:55:32 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 26EE521F8898 for <gen-art@ietf.org>; Fri, 17 Feb 2012 00:55:32 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 293752D35A; Fri, 17 Feb 2012 10:55:30 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f1bvxJ4dClkc; Fri, 17 Feb 2012 10:55:25 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 798D72CC3C; Fri, 17 Feb 2012 10:55:25 +0200 (EET)
Message-ID: <4F3E15FC.80304@piuha.net>
Date: Fri, 17 Feb 2012 10:55:24 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0) Gecko/20120129 Thunderbird/10.0
MIME-Version: 1.0
To: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
References: <4F3E124F.40603@ericsson.com>
In-Reply-To: <4F3E124F.40603@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: darlewis@cisco.com, vaf@cisco.com, General Area Review Team <gen-art@ietf.org>, dmm@cisco.com, dino@cisco.com, terry.manderson@icann.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-lisp-interworking-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, 17 Feb 2012 08:55:33 -0000

Thanks for your review!

Jari

On 17.02.2012 10:39, Miguel A. Garcia wrote:
> 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-lisp-interworking-03.txt
> Reviewer: Miguel Garcia <miguel.a.garcia@ericsson.com>
> Review Date: 2012-02-17
> IETF LC End Date: 2012-02-23
> IESG Telechat date: 2012-03-01
>
> Summary: The document is ready for publication as an experimental RCFc.
>
> Major issues: none
>
> Minor issues: none
>
> Nits/editorial comments:
>
> - Section 5.2 describes a sequence of packet flows. I think it would be easier to understand if there is a companion figure to which the text can refer to. Otherwise, the reader has to compose this figure in his mind.
>
> - Please expand acronyms at first occurrence. This includes: RLOC, CRIO
>
> - Perhaps the terminology section should include RLOC, xTR, ETR, ITR, DFZ
>
> - Idnits reveals a number of unused references: LIPS-MS, RFC4632, LISP-DEPLOY, RFC4787, RFC5382. They should be deleted.
>
> - Idnits reveals an obsolete reference: RFC 2434 (Obsoleted by RFC 5226)
>
> - Idnits reveals a number of instances where IP addresses are not compliant with RFC 5735. I am trying to identify which ones of these are. I guess they are the 220.x.x.x, 128.x.x.x EIDs. I think most of them are technically EIDs for LISP-NR, LISP-R LISP-NAT, etc. I don't know if RFC 5735 applies to this draft or not, I am just letting you know in case you need to fix something.
>
> BR,
>
>      Miguel
>
>


From miguel.a.garcia@ericsson.com  Fri Feb 17 01:59:05 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 5CB4821F8889 for <gen-art@ietfa.amsl.com>; Fri, 17 Feb 2012 01:59:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.33
X-Spam-Level: 
X-Spam-Status: No, score=-10.33 tagged_above=-999 required=5 tests=[AWL=0.269,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZZXnPGELLV7F for <gen-art@ietfa.amsl.com>; Fri, 17 Feb 2012 01:59:04 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id 8688921F8887 for <gen-art@ietf.org>; Fri, 17 Feb 2012 01:59:04 -0800 (PST)
X-AuditID: c1b4fb3d-b7bb7ae0000007b2-d4-4f3e24e79cee
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id D8.94.01970.7E42E3F4; Fri, 17 Feb 2012 10:59:03 +0100 (CET)
Received: from [159.107.24.194] (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.94) with Microsoft SMTP Server id 8.3.213.0; Fri, 17 Feb 2012 10:59:03 +0100
Message-ID: <4F3E24E5.2050902@ericsson.com>
Date: Fri, 17 Feb 2012 10:59:01 +0100
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1
MIME-Version: 1.0
To: Zhen Cao <zehn.cao@gmail.com>, Hui Deng <denghui02@gmail.com>,  "sunseawq@huawei.com" <sunseawq@huawei.com>, glenzorn@gmail.com, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Cc: General Area Review Team <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-hokey-erp-aak-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: Fri, 17 Feb 2012 09:59:05 -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-hokey-erp-aak-09.txt
Reviewer: Miguel Garcia <miguel.a.garcia@ericsson.com>
Review Date: 2012-02-17
IETF LC End Date:
IESG Telechat date:

Summary: The document is ready for publication as a Standards Track RFC.

Major issues: none

Minor issues: none

Nits/editorial comments:

I reviewed version -07 of this document (see 
http://www.ietf.org/mail-archive/web/gen-art/current/msg07148.html ). At 
that time I had some minor issues with the draft, and they all have been 
successfully captured in version -09. So, from my point of view, the 
document is ready.

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

From darlewis@cisco.com  Fri Feb 17 09:16:37 2012
Return-Path: <darlewis@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 79CCD21F8543 for <gen-art@ietfa.amsl.com>; Fri, 17 Feb 2012 09:16:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.471
X-Spam-Level: 
X-Spam-Status: No, score=-6.471 tagged_above=-999 required=5 tests=[AWL=0.891,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_43=0.6, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8, SARE_LWSHORTT=1.24]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jjv2iS-NsxZ3 for <gen-art@ietfa.amsl.com>; Fri, 17 Feb 2012 09:16:32 -0800 (PST)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 210A721F853B for <gen-art@ietf.org>; Fri, 17 Feb 2012 09:16:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=darlewis@cisco.com; l=92377; q=dns/txt; s=iport; t=1329498992; x=1330708592; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to; bh=BVuHoHmREii5bEDhHaBzkFi8UTi3q7XNa8WJLhFmbFw=; b=UbKrFTBlZFg7rSwiv3r2M95wf4V0rdHy9JFcwPDgfJPzawy2ellm11OI gOaixirZWb+v8nIIbYunTed2NGjDgdKQv3h2H7XX7+AKLeVev/u+HQ0ya mJik3RUuwK2q7uWU9pVM6w2iW48DCx7moC23/MHAfX62+nNxC/4/RjA6H E=;
X-Files: draft-ietf-interworking-03-to-04-diffs.html, draft-ietf-lisp-interworking-04.txt : 42361, 43913
X-IronPort-AV: E=Sophos;i="4.73,439,1325462400";  d="txt'?html'217?scan'217,208,217";a="30849552"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-4.cisco.com with ESMTP; 17 Feb 2012 17:16:32 +0000
Received: from [10.154.208.44] ([10.154.208.44]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id q1HHGVJA001239; Fri, 17 Feb 2012 17:16:31 GMT
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: multipart/mixed; boundary="Apple-Mail=_0CFF713C-A48B-42C0-A5AC-275612E32ABC"
From: Darrel Lewis <darlewis@cisco.com>
In-Reply-To: <4F3E124F.40603@ericsson.com>
Date: Fri, 17 Feb 2012 09:16:31 -0800
Message-Id: <563138F8-5E09-410A-B2BF-6795ADBA8A2B@cisco.com>
References: <4F3E124F.40603@ericsson.com>
To: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
X-Mailer: Apple Mail (2.1257)
X-Mailman-Approved-At: Fri, 17 Feb 2012 10:54:50 -0800
Cc: Darrel Lewis <darlewis@cisco.com>, vaf@cisco.com, General Area Review Team <gen-art@ietf.org>, dmm@cisco.com, Jari Arkko <jari.arkko@piuha.net>, dino@cisco.com, terry.manderson@icann.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-lisp-interworking-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, 17 Feb 2012 17:16:37 -0000

--Apple-Mail=_0CFF713C-A48B-42C0-A5AC-275612E32ABC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Feb 17, 2012, at 12:39 AM, Miguel A. Garcia wrote:

> 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 =
receive.
>=20
> Document: draft-ietf-lisp-interworking-03.txt
> Reviewer: Miguel Garcia <miguel.a.garcia@ericsson.com>Review Date: =
2012-02-17
> IETF LC End Date: 2012-02-23
> IESG Telechat date: 2012-03-01
>=20
> Summary: The document is ready for publication as an experimental =
RCFc.
>=20
> Major issues: none
>=20
> Minor issues: none
>=20
> Nits/editorial comments:
>=20
> - Section 5.2 describes a sequence of packet flows. I think it would =
be easier to understand if there is a companion figure to which the text =
can refer to. Otherwise, the reader has to compose this figure in his =
mind.
>=20
> - Please expand acronyms at first occurrence. This includes: RLOC, =
CRIO
>=20

Thanks, fixed.

> - Perhaps the terminology section should include RLOC, xTR, ETR, ITR, =
DFZ
>=20

The WG/authors for all the related LISP documents decided that we would =
not repeat definitions from the main lisp spec (draft-ietf-lisp) and =
that document is a normative reference for this document.  At the end of =
the definitions section is a reference for the main spec for exactly =
this purpose.  So I am going to not repeat the definitions for RLOC, =
xTR, ETR and ITR.  I provided a definition for DFZ, thanks.

> - Idnits reveals a number of unused references: LIPS-MS, RFC4632, =
LISP-DEPLOY, RFC4787, RFC5382. They should be deleted.

These references were added at the request of other reviewers during the =
WG Last call. These references are only informative and I think help =
provide context for the concepts developed in the document.  I am going =
to leave them unless you feel its a critical issue. =20

>=20
> - Idnits reveals an obsolete reference: RFC 2434 (Obsoleted by RFC =
5226)
>=20

Thanks, fixed.=20

> - Idnits reveals a number of instances where IP addresses are not =
compliant with RFC 5735. I am trying to identify which ones of these =
are. I guess they are the 220.x.x.x, 128.x.x.x EIDs. I think most of =
them are technically EIDs for LISP-NR, LISP-R LISP-NAT, etc. I don't =
know if RFC 5735 applies to this draft or not, I am just letting you =
know in case you need to fix something.

Thanks, fixed (now 5735 addresses throughout).=20

I appreciate your review!  Posted -04 in response to these changes.

Attached is the -04 version and html diffs for 03 to 04.


--Apple-Mail=_0CFF713C-A48B-42C0-A5AC-275612E32ABC
Content-Disposition: attachment;
	filename=draft-ietf-interworking-03-to-04-diffs.html
Content-Type: text/html;
	name="draft-ietf-interworking-03-to-04-diffs.html"
Content-Transfer-Encoding: 7bit

<html><head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"><title>wdiff draft-ietf-lisp-interworking-03.txt draft-ietf-lisp-interworking-04.txt</title></head><body>
<pre>
Network Working Group                                           D. Lewis
Internet-Draft                                                  D. Meyer
Intended status: Experimental                               D. Farinacci
Expires: August <strike><font color="red">12,</font></strike> <strong><font color="green">20,</font></strong> 2012                                       V. Fuller
                                                     Cisco Systems, Inc.
                                                       February <strike><font color="red">9,</font></strike> <strong><font color="green">17,</font></strong> 2012

                  Interworking LISP with IPv4 and IPv6
                  <strike><font color="red">draft-ietf-lisp-interworking-03.txt</font></strike>
                  <strong><font color="green">draft-ietf-lisp-interworking-04.txt</font></strong>

Abstract

   This document describes techniques for allowing sites running the
   Locator/ID Separation Protocol (LISP) to interoperate with Internet
   sites (which may be using either IPv4, IPv6, or both) but which are
   not running LISP.  A fundamental property of LISP speaking sites is
   that they use Endpoint Identifiers (EIDs), rather than traditional IP
   addresses, in the source and destination fields of all traffic they
   emit or receive.  While EIDs are syntactically identical to IPv4 or
   IPv6 addresses, normally routes to them are not carried in the global
   routing system so an interoperability mechanism is needed for non-
   LISP-speaking sites to exchange traffic with LISP-speaking sites.
   This document introduces three such mechanisms.  The first uses a new
   network element, the LISP Proxy Ingress Tunnel Routers (PITR)
   (Section 5) to act as a intermediate LISP Ingress Tunnel Router (ITR)
   for non-LISP-speaking hosts.  Second the document adds Network
   Address Translation (NAT) functionality to LISP Ingress and LISP
   Egress Tunnel Routers (xTRs) to substitute routable IP addresses for
   non-routable EIDs.  Finally, this document introduces a Proxy Egress
   Tunnel Router (PETR) to handle cases where a LISP ITR cannot send
   packets to non-LISP sites without encapsulation.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."
   This Internet-Draft will expire on August <strike><font color="red">12,</font></strike> <strong><font color="green">20,</font></strong> 2012.

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  LISP Interworking Models . . . . . . . . . . . . . . . . . . .  6
   3.  Definition of Terms  . . . . . . . . . . . . . . . . . . . . .  7
   4.  Routable EIDs  . . . . . . . . . . . . . . . . . . . . . . . .  8
     4.1.  Impact on Routing Table  . . . . . . . . . . . . . . . . .  8
     4.2.  Requirement for using BGP  . . . . . . . . . . . . . . . .  8
     4.3.  Limiting the Impact of Routable EIDs . . . . . . . . . . .  8
     4.4.  Use of Routable EIDs for sites transitioning to LISP . . .  8
   5.  Proxy Ingress Tunnel Routers . . . . . . . . . . . . . . . . . 10
     5.1.  PITR EID announcements . . . . . . . . . . . . . . . . . . 10
     5.2.  Packet Flow with PITRs . . . . . . . . . . . . . . . . . . 10
     5.3.  Scaling PITRs  . . . . . . . . . . . . . . . . . . . . . . 11
     5.4.  Impact of the PITRs placement in the network . . . . . . . 12
     5.5.  Benefit to Networks Deploying PITRs  . . . . . . . . . . . 12
   6.  LISP-NAT . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
     6.1.  Using LISP-NAT with LISP-NR EIDs . . . . . . . . . . . . . 13
     6.2.  LISP Sites with Hosts using RFC 1918 Addresses Sending
           to non-LISP Sites  . . . . . . . . . . . . . . . . . . . . 14
     6.3.  LISP Sites with Hosts using RFC 1918 Addresses
           Sending Packets to Other LISP Sites  . . . . . . . . . . . 14
     6.4.  LISP-NAT and multiple EIDs . . . . . . . . . . . . . . . . 15
   7.  Proxy Egress Tunnel Routers  . . . . . . . . . . . . . . . . . 16
     7.1.  Packet Flow with Proxy Egress Tunnel Routers . . . . . . . 16
   8.  Discussion of Proxy ITRs (PITRs), LISP-NAT, and Proxy-ETRs
       (PETRs)  . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
     8.1.  How Proxy-ITRs and Proxy-ETRs Interact . . . . . . . . . . 18
   9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 19
   10. Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 20
   11. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 21
   12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 22
     12.1. Normative References . . . . . . . . . . . . . . . . . . . 22
     12.2. Informative References . . . . . . . . . . . . . . . . . . 22
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 24

1.  Introduction

   This document describes interoperation between LISP [LISP] sites
   which use non-globally-routed EIDs, and non-LISP sites.  The first is
   the use of Proxy Ingress Tunnel router (PITRs), which originate
   highly-aggregated routes to EID prefixes for non-LISP sites to use.
   It also describes the use of NAT by LISP ITRs when sending packets to
   non-LISP hosts.  Finally, it describes Proxy Egress Tunnel routers
   (PETRs) LISP for sites relying on PITRs, and which are faced with
   certain restrictions.

   A key behavior of the separation of Locators and End-Point-IDs is
   that EID prefixes are normally not advertised into the Internet's
   Default Free Zone (DFZ).  Specifically, only <strike><font color="red">RLOCs</font></strike> <strong><font color="green">Routing Locators (RLOCs)</font></strong>
   are carried in the Internet's DFZ.  Existing Internet sites (and
   their hosts) which do not run in the LISP protocol must still be able
   to reach sites numbered from LISP EID space.  This draft describes
   three mechanisms that can be used to provide reachability between
   sites that are <strike><font color="red">LISP-
   capable</font></strike> <strong><font color="green">LISP-capable</font></strong> and those that are not.

   The first mechanism uses a new network element, the LISP Proxy
   Ingress Tunnel Router (PITR) to act as a intermediate LISP Ingress
   Tunnel Router (ITR) for non-LISP-speaking hosts.  The second
   mechanism adds a form of Network Address Translation (NAT)
   functionality to Tunnel Routers (xTRs), to substitute routable IP
   addresses for non-routable EIDs.  The final network element is the
   LISP Proxy Egress Tunnel Routers (PETR), which act as an intermediate
   Egress Tunnel Router (ETR) for LISP sites which need to encapsulate
   packets LISP packets destined to non-LISP sites.

   More detailed descriptions of these mechanisms and the network
   elements involved may be found in the following sections:

   - Section 2 describes the different cases where interworking
   mechanisms are needed

   - Section 3 defines terms used throughout the document

   - Section 4 describes the relationship between the new EID prefix
   space and the IP address space used by the current Internet

   - Section 5 introduces and describes the operation of Proxy-ITRs

   - Section 6 defines how NAT is used by ETRs to translate non-routable
   EIDs into routable IP addresses.

   - Section 7 introduces and describes the operations of Proxy-ETRs
   - Section 8 describes the relationship between asymmetric and
   Symmetric interworking mechanisms (Proxy-ITRs and Proxy-ETRs vs LISP-
   NAT)

   Note that any successful interworking model should be independent of
   any particular EID-to-RLOC mapping algorithm.  This document does not
   comment on the value of any of the particular LISP mapping systems.

   Several areas concerning the Interworking of LISP and non-LISP sites
   remain open for further study.  These areas include an examination
   the impact of LISP-NAT on internet traffic and applications,
   understanding the deployment motivations for the deployment and
   operation of Proxy Tunnel Routers, the impact of EID routes
   originated into the Internet's Default Free Zone,and the effects of
   Proxy Tunnel Routers or LISP-NAT on internet traffic and
   applications.  Until these issues are fully understood, it is
   possible that the interworking mechanisms described in this document
   are hard to deploy, or may have unintended consequences to
   applications.

2.  LISP Interworking Models

   There are 4 unicast connectivity cases which describe how sites can
   send packets to each other:

   1.  Non-LISP site to Non-LISP site

   2.  LISP site to LISP site

   3.  LISP site to Non-LISP site

   4.  Non-LISP site to LISP site

   Note that while Cases 3 and 4 seem similar, there are subtle
   differences due to the way packets are originated.

   The first case is the Internet as we know it today and as such will
   not be discussed further here.  The second case is documented in
   [LISP] and there are no new interworking requirements because there
   are no new protocol requirements placed on intermediate non- LISP
   routers.

   In case 3, LISP site to Non-LISP site, a LISP site can (in most
   cases) send packets to a non-LISP site because the non-LISP site
   prefixes are routable.  The non-LISP site need not do anything new to
   receive packets.  The only action the LISP site needs to take is to
   know when not to LISP-encapsulate packets.  An ITR knows explicitly
   that the destination is non-LISP if the destination IP address of an
   IP packet matches a (negative) Map-Cache entry which has the action
   'Natively-Forward'.

   There could be some situations where (unencapsulated) packets
   originated by a LISP site may not be forwarded to a non-LISP site.
   These cases are reviewed in section 7, (Proxy-Egress Tunnel Routers).

   Case 4, typically the most challenging, occurs when a host at a non-
   LISP site wishes to send traffic to a host at a LISP site.  If the
   source host uses a (non-globally-routable) EID as the destination IP
   address, the packet is forwarded inside the source site until it
   reaches a router which cannot forward it (due to lack of a default
   route), at which point the traffic is dropped.  For traffic not to be
   dropped, either some mechanism to make this destination EID routable
   must be in place.  Section 5 (PITRs) and Section 6 (LISP-NAT)
   describe two such mechanisms.

   Case 4 also applies to packets returning to the LISP site, in Case 3.

3.  Definition of Terms

   <strong><font color="green">Default Free Zone:  The Default-Free Zone (DFZ) refers to the
      collection of all Internet autonomous systems that do not require
      a default route to route a packet to any destination.</font></strong>

   LISP Routable (LISP-R) Site:  A LISP site whose addresses are used as
      both globally routable IP addresses and LISP EIDs.

   LISP Non-Routable (LISP-NR) Site:  A LISP site whose addresses are
      EIDs only, these EIDs are not found in the legacy Internet routing
      table.

   LISP Proxy Ingress Tunnel Router (PITR):  PITRs are used to provide
      interconnectivity between sites which use LISP EIDs and those
      which do not.  They act as gateways between those parts of the
      Internet which are not using LISP (the legacy Internet) A given
      PITR advertises one or more highly aggregated EID prefixes into
      the public Internet and acts as the ITR for traffic received from
      the public Internet.  LISP Proxy Ingress Tunnel Routers are
      described in Section 5.

   LISP Network Address Translation (LISP-NAT):  Network Address
      Translation between EID space assigned to a site and RLOC space
      also assigned to that site.  LISP Network Address Translation is
      described in Section 6.

   LISP Proxy Egress Tunnel Router (PETR):  PETRs provide a LISP
      (Routable or Non-Routable EID) site's ITRs the ability to send
      packets to non-LISP sites in cases where unencapsualted packets
      (the default mechanism) would fail to be delivered.  PETRs are
      function by having an ITR encapsulate all non-LISP destined
      traffic to a pre-configured PETR.  LISP Proxy Egress Tunnel
      Routers are described in Section 7.

    EID Sub Namespace:  A power-of-two block of aggregatable locators
      set aside for LISP interworking.

   For definitions of other terms, notably Map-Request, Map-Reply,
   Ingress Tunnel Router (ITR), and Egress Tunnel Router (ETR), please
   consult the LISP specification [LISP].

4.  Routable EIDs

   An obvious way to achieve interworking between LISP and non-LISP
   hosts is for a LISP site to simply announce EID prefixes into the
   DFZ, much like the current routing system, effectively treating them
   as "Provider Independent (PI)" prefixes.  Having a site do this is
   undesirable as it defeats one of the primary goals of LISP - to
   reduce global routing system state.

4.1.  Impact on Routing Table

   If EID prefixes are announced into the DFZ, the impact is similar to
   the case in which LISP has not been deployed, because these EID
   prefixes will be no more aggregatable than existing PI addressing.
   Such a mechanism is not viewed as a viable long term solution, but
   may be a viable short term way for a site to transition a portion of
   its address space to EID space without changing its existing routing
   policy.

4.2.  Requirement for using BGP

   Non-LISP sites today use BGP to, among other things, enable ingress
   traffic engineering.  Relaxing this requirement is another primary
   design goal of LISP.

4.3.  Limiting the Impact of Routable EIDs

   Two schemes are proposed to limit the impact of having EIDs announced
   in the current global Internet routing table:

   1.  Section 5 discusses the LISP Proxy Tunnel Router, an approach
       that provides ITR functionality to bridge LISP-capable and non-
       LISP-capable sites.

   2.  Section 6 discusses another approach, LISP-NAT, in which NAT
       [RFC2993] is combined with ITR functionality to limit the impact
       of routable EIDs on the Internet routing infrastructure.

4.4.  Use of Routable EIDs for sites transitioning to LISP

   A primary design goal for LISP (and other Locator/ID separation
   proposals) is to facilitate topological aggregation of namespace used
   by the path computation, and, thus, decrease global routing system
   overhead.  Another goal is to achieve the benefits of improved
   aggregation as soon as possible.  Individual sites advertising their
   own routes for LISP EID prefixes into the global routing system is
   therefore not recommended.

   That being said, single homed sites (or multi-homed sites that are
   not leaking more specific exceptions) and that are already using
   provider-aggregated prefixes can use these prefixes as LISP EIDs
   without adding state to the routing system.  In other words, such
   sites do not cause additional prefixes to be advertised.  For such
   sites, connectivity to a non-LISP sites does not require interworking
   machinery because the "PA" EIDs are already routable (they are
   effectively LISP-R type sites).  Their EIDs are found in the LISP
   mapping system, and their (aggregate) PA prefix(es) are found in the
   DFZ Internet.

   The continued announcements of an existing site's Provider
   Independent (or "PI") prefix(es) is of course under control of that
   site.  Some period of transition, where a site is found both in the
   LISP mapping system, and as a discrete prefix in the Internet routing
   system, may be a viable transition strategy.  Care should be taken
   not to advertise additional more specific LISP EID prefixes into the
   DFZ.

5.  Proxy Ingress Tunnel Routers

   Proxy Ingress Tunnel Routers (PITRs) allow for non-LISP sites to send
   packets to LISP-NR sites.  A PITR is a new network element that
   shares many characteristics with the LISP ITR.  PITRs allow non-LISP
   sites to send packets to LISP-NR sites without any changes to
   protocols or equipment at the non-LISP site.  PITRs have two primary
   functions:

   Originating EID Advertisements:  PITRs advertise highly aggregated
      EID-prefix space on behalf of LISP sites to so that non-LISP sites
      can reach them.

   Encapsulating Legacy Internet Traffic:  PITRs also encapsulate non-
      LISP Internet traffic into LISP packets and route them towards
      their destination RLOCs.

5.1.  PITR EID announcements

   A key part of PITR functionality is to advertise routes for highly-
   aggregated EID prefixes into part of the global routing system.
   Aggressive aggregation is performed to minimize the number of new
   announced routes.  In addition, careful placement of PITRs can
   greatly reduce the advertised scope of these new routes.  To this
   end, PITRs should be deployed close to non-LISP-speaking rather than
   close to LISP sites.  Such deployment not only limits the scope of
   EID-prefix route advertisements, it also allows traffic forwarding
   load to be spread among many PITRs.

5.2.  Packet Flow with PITRs

   What follows is an example of the path a packet would take when using
   a PITR.  In this example, the LISP-NR site is given the EID prefix
   192.0.2.0/24.  For the purposes of this example, neither this prefix
   or any covering aggregate are present in the global routing system.
   In other words, without the Proxy-ITR announcing 192.0.2.0/24, a
   packet with this destination were to reach a router in the "Default
   Free Zone", it would be dropped.

   A full protocol exchange example follows:

   1.  The source host makes a DNS lookup EID for destination, and gets
       192.0.2.1 in return.

   2.  The source host has a default route to customer Edge (CE) router
       and forwards the packet to the CE.

   3.  The CE has a default route to its Provider Edge (PE) router, and
       forwards the packet to the PE.

   4.  The PE has route to 192.0.2.0/24 and the next hop is the PITR.

   5.  The PITR has or acquires a mapping for 192.0.2.1 and LISP
       encapsulates the packet.  The outer IP header now has a
       destination address of one of the destination EID's RLOCs.  The
       outer source address of this encapsulated packet is the PITR's
       RLOC.

   6.  The PITR looks up the RLOC, and forwards LISP packet to the next
       hop, after which, it is forwarded by other routers to the ETR's
       RLOC.

   7.  The ETR decapsulates the packet and delivers the packet to the
       192.0.2.1 host in the destination LISP site.

   8.  Packets from host 192.0.2.1 will flow back through the LISP
       site's ITR.  Such packets are not encapsulated because the ITR
       knows that the destination (the original source) is a non-LISP
       site.  The ITR knows this because it can check the LISP mapping
       database for the destination EID, and on a failure determine that
       the destination site is not LISP enabled.

   9.  Packets are then routed natively and directly to the destination
       (original source) site.

   Note that in this example the return path is asymmetric, so return
   traffic will not go back through the PITR.  This is because the
   LISP-NR site's ITR will discover that the originating site is not a
   LISP site, and not encapsulate the returning packet (see [LISP] for
   details of ITR behavior).

   The asymmetric nature of traffic flows allows the PITR to be
   relatively simple - it will only have to encapsulate LISP packets.

5.3.  Scaling PITRs

   PITRs attract traffic by announcing the LISP EID namespace into parts
   of the non-LISP-speaking global routing system.  There are several
   ways that a network could control how traffic reaches a particular
   PITR to prevent it from receiving more traffic than it can handle:

   1.  The PITR's aggregate routes might be selectively announced,
       giving a coarse way to control the quantity of traffic attracted
       by that PITR.  For example, some of the routes being announced
       might be tagged with a BGP community and their scope of
       announcement limited by the routing policy of the provider.

   2.  The same address might be announced by multiple PITRs in order to
       share the traffic using IP Anycast.  The asymmetric nature of
       traffic flows through the Proxy ITR means that operationally,
       deploying a set PITRs would be very similar to existing Anycasted
       services like DNS caches.  Multiple Proxy ITRs could advertise
       the same BGP Next Hop IP address as their RLOC, and traffic would
       be attracted to the nearest Next Hop according to the network's
       IGP.

5.4.  Impact of the PITRs placement in the network

   There are several approaches that a network could take in placing
   PITRs.  Placing the PITR near the source of traffic allows for the
   communication between the non-LISP site and the LISP site to have the
   least "stretch" (i.e. the least number of forwarding hops when
   compared to an optimal path between the sites).

   Some proposals, for example <strike><font color="red">CRIO</font></strike> <strong><font color="green">Core Router-Integrated Overlay</font></strong> [CRIO],
   have suggested grouping PITRs near an arbitrary subset of ETRs and
   announcing a 'local' subset of EID space.  This model cannot
   guarantee minimum stretch if the EID prefix route advertisement
   points are changed (such a change might occur if a site adds,
   removes, or replaces one or more of its ISP connections).

5.5.  Benefit to Networks Deploying PITRs

   When packets destined for LISP-NR sites arrive and are encapsulated
   at a Proxy-ITR, a new LISP packet header is pre-pended.  This causes
   the packet's destination to be set to the destination ETRs RLOC.
   Because packets are thus routed towards RLOCs, it can potentially
   better follow the Proxy-ITR network's traffic engineering policies
   (such as closest exit routing).  This also means that providers which
   are not default-free and do not deploy Proxy-ITRs end up sending more
   traffic to expensive transit links (assuming their upstreams have
   deployed Proxy-ITRs) rather than to the ETR's RLOC addresses, to
   which they may well have cheaper and closer connectivity to (via, for
   example, settlement-free peering).  A corollary to this would be that
   large transit providers, deploying PITRs may attract more traffic,
   and therefore more revenue, from their customers.

6.  LISP-NAT

   LISP Network Address Translation (LISP-NAT) is a limited form of NAT
   [RFC2993].  LISP-NAT is designed to enable the interworking of non-
   LISP sites and LISP-NR sites by ensuring that the LISP-NR's site
   addresses are always routable.  LISP-NAT accomplishes this by
   translating a host's source address from an 'inner' (LISP-NR EID)
   value to an 'outer' (LISP-R) value and keeping this translation in a
   table that it can reference for subsequent packets.

   In addition, existing RFC 1918 [RFC1918] sites can use LISP-NAT to
   talk to both LISP or non-LISP sites.

   The basic concept of LISP-NAT is that when transmitting a packet, the
   ITR replaces a non-routable EID source address with a routable source
   address, which enables packets to return to the site.

   There are two main cases that involve LISP-NAT:

   1.  Hosts at LISP sites that use non-routable global EIDs speaking to
       non-LISP sites using global addresses.

   2.  Hosts at LISP sites that use RFC 1918 private EIDs speaking to
       other sites, who may be either LISP or non-LISP.

   Note that LISP-NAT is not needed in the case of LISP-R (routable
   global EIDs) sources.  This case occurs when a site is announcing its
   prefix into both the LISP mapping system as well as the Internet DFZ.
   This is because the LISP-R source's address is routable, and return
   packets will be able to natively reach the site.

6.1.  Using LISP-NAT with LISP-NR EIDs

   LISP-NAT allows a host with a LISP-NR EID to send packets to non-LISP
   hosts by translating the LISP-NR EID to a globally unique address (a
   LISP-R EID).  This globally unique address may be a either a PI or PA
   address.

   An example of this translation follows.  For this example, a site has
   been assigned a LISP-NR EID of <strike><font color="red">220.1.1.0/24.</font></strike> <strong><font color="green">203.0.113.0/24.</font></strong>  In order to utilize
   LISP-NAT, the site has also been provided the PA EID of
   <strike><font color="red">128.200.1.0/24,</font></strike> <strong><font color="green">192.0.2.0/24,</font></strong>
   and uses the first address <strike><font color="red">(128.200.1.1)</font></strike> <strong><font color="green">(192.0.2.1)</font></strong> as the site's RLOC.  The rest
   of this PA space <strike><font color="red">(128.200.1.2</font></strike> <strong><font color="green">(192.0.2.2</font></strong> to
   <strike><font color="red">128.200.1.254)</font></strike> <strong><font color="green">192.0.2.254)</font></strong> is used as a translation
   pool for this site's hosts who need to send packets to non-LISP
   hosts.

   The translation table might look like the following:

          Site NR-EID     Site R-EID     Site's RLOC    Translation Pool
          ==============================================================
          <strike><font color="red">220.1.1.0/24   128.200.1.0/24  128.200.1.1    128.200.1.2-254</font></strike>
          <strong><font color="green">203.0.113.0/24  192.0.2.0/24    192.0.2.1      192.0.2.2-254</font></strong>

                    Figure 1: Example Translation Table

   The Host <strike><font color="red">220.1.1.2</font></strike> <strong><font color="green">203.0.113.2</font></strong> sends a packet (which, for the purposes of this
   example is destined for a non-LISP site) to its default route (the
   ITR).  The ITR receives the packet, and determines that the
   destination is not a LISP site.  How the ITR makes this determination
   is up to the ITRs implementation of the EID-to-RLOC mapping system
   used (see, for example [LISP-ALT]).

   The ITR then rewrites the source address of the packet from <strike><font color="red">220.1.1.2</font></strike>
   <strong><font color="green">203.0.113.2</font></strong> to <strike><font color="red">128.200.1.2,</font></strike> <strong><font color="green">192.0.2.2,</font></strong> which is the first available address in the
   LISP-R EID space available to it.  The ITR keeps this translation in
   a table in order to reverse this process when receiving packets
   destined to
   <strike><font color="red">128.200.1.2.</font></strike> <strong><font color="green">192.0.2.2.</font></strong>

   Finally, when the ITR forwards this packet without encapsulating it,
   it uses the entry in its LISP-NAT table to translate the returning
   packets' destination IPs to the proper host.

6.2.  LISP Sites with Hosts using RFC 1918 Addresses Sending to non-LISP
      Sites

   In the case where hosts using RFC 1918 addresses desire to send
   packets to non-LISP hosts, the LISP-NAT implementation acts much like
   an existing IPv4 NAT device.  The ITR providing the NAT service must
   use LISP-R EIDs for its global address pool as well as providing all
   the standard NAT functions required today.

   The source of the packet must be translated to a LISP-R EID in a
   manner similar to Section 6, and this packet must be forwarded to the
   ITR's next hop for the destination, without LISP encapsulation.

6.3.  LISP Sites with Hosts using RFC 1918 Addresses   Sending Packets
      to Other LISP Sites

   LISP-NAT allows a host with an RFC 1918 address to send packets to
   LISP hosts by translating the RFC 1918 address to a LISP EID.  After
   translation, the communication between source and destination ITR and
   ETRs continues as described in [LISP].

   An example of this translation and encapsulation follows.  For this
   example, a host has been assigned a RFC 1918 address of 192.168.1.2.
   In order to utilize LISP-NAT, the site also has been provided the
   LISP-R EID prefix of 192.0.2.0/24, and uses the first address
   (192.0.2.1) as the site's RLOC.  The rest of this PA space (192.0.2.2
   to 192.0.2.254) is used as a translation pool for this site's hosts
   who need to send packets to both non-LISP and LISP hosts.

   The Host 192.168.1.2 sends a packet destined for a non-LISP site to
   its default route (the ITR).  The ITR receives the packet and
   determines that the destination is a LISP site.  How the ITR makes
   this determination is up to the ITRs implementation of the EID/RLOC
   mapping system.

   The ITR then rewrites the source address of the packet from
   192.168.1.2 to 192.0.2.2, which is the first available address in the
   LISP EID space available to it.  The ITR keeps this translation in a
   table in order to reverse this process when receiving packets
   destined to 192.0.2.2.

   The ITR then LISP encapsulates this packet (see [LISP] for details).
   The ITR uses the site's RLOC as the LISP outer header's source and
   the translation address as the LISP inner header's source.  Once it
   decapsulates returning traffic, it uses the entry in its LISP-NAT
   table to translate the returning packet's destination IP address and
   then forward to the proper host.

6.4.  LISP-NAT and multiple EIDs

   With LISP-NAT, there are two EIDs possible for a given host, the
   LISP-R EID and the LISP-NR EID.  When a site has two addresses that a
   host might use for global reachability, name-to-address directories
   may need to be modified.

   This problem, global vs. local addressability, exists for NAT in
   general, but the specific issue described above is unique to
   location/identity separation schemes.  Some of these have suggested
   running a separate DNS instance for new types of EIDs.  This solves
   the problem but introduces complexity for the site.  Alternatively,
   using PITRs can mitigate this problem, because the LISP-NR EID can be
   reached in all cases.

7.  Proxy Egress Tunnel Routers

   Proxy Egress Tunnel Routers (PETRs) allow for LISP sites to send
   packets to non-LISP sites in the case where the access network does
   not allow for the LISP site send packets with the source address of
   the site's EID(s).  A PETR is a new network element that,
   conceptually, acts as an ETR for traffic destined to non-LISP sites.
   This also has the effect of allowing an ITR avoid having to decide
   whether to encapsulate packets or not - it can always encapsulate
   packets.  An ITR would encapsulate packets destined for LISP sites
   (no change here) and these would be routed directly to the
   corespondent site's ETR.  All other packets (those destined to non-
   LISP sites) will be sent to the originating site's PETR.

   There are two primary reasons why sites would want to utilize a PETR:

   Avoiding strict uRPF failures:  Some provider's access networks
      require the source of the packets emitted to be within the
      addressing scope of the access networks. (see section 9)

   Traversing a different IP Protocol:  A LISP site may want to transmit
      packets to a non-LISP site where some of the intermediate network
      does not support the particular IP protocol desired (v4 or v6).
      PETRs can allow this LISP site's data to 'hop over' this by
      utilizing LISP's support for mixed protocol encapsulation.

7.1.  Packet Flow with Proxy Egress Tunnel Routers

   Packets from a LISP site can reach a non-LISP site with the aid of a
   Proxy-ETR (or PETR).  An ITR is simply configured to send all non-
   LISP traffic, which it normally would have forwarded natively (non-
   encapsulated), to a PETR.  In the case where the ITR uses a Map-
   Resolver(s), the ITR will encapsulate packets that match the received
   Negative Map-Cache to the configured Proxy-ETR(s).  In the case where
   the ITR is connected to the mapping system directly it would
   encapsulate all packets to the configured Proxy-ETR that are cache
   misses.  Note that this outer encapsulation to the Proxy-ETR may be
   in an IP protocol other than the (inner) encapsulated data.  Routers
   then use the LISP (outer) header's destination address to route the
   packets toward the configured Proxy-ETR.

   A PETR should verify the (inner) source EID of the packet at time of
   decapsulation in order to verify that this is from a configured LISP
   site.  This is to prevent spoofed inner sources from being
   encapsulated through the Proxy-ETR.

   What follows is an example of the path a packet would take when using
   a PETR.  In this example, the LISP-NR (or LISP-R) site is given the
   EID prefix 192.0.2.0/24, and it is trying to reach host at a non-LISP
   site with the IP prefix of 198.51.100.0/24.  For the purposes of this
   example, the destination (198.51.100.0/24) is found in the Internet's
   routing system.

   A full protocol exchange example follows:

   1.  The source host makes a DNS lookup for the destination, and gets
       198.51.100.100 (a Ip address of a host in the non-LISP site) in
       return.

   2.  The source host has a default route to customer Edge (CE) router
       and forwards the packet towards the CE.

   3.  The CE is a LISP ITR, and is configured to encapsulate traffic
       destined for non-LISP sites to a Proxy-ETR.

   4.  The Proxy ETR decapsulates the LISP packet and forwards the
       original packet to its next hop.

   5.  The packet is then routed natively and directly to the
       destination (non-LISP) site 198.51.100.0/24.

   Note that in this example the return path is asymmetric, so return
   traffic will not go back through the Proxy-ETR.  This means that in
   order to reach LISP-NR sites, non-LISP sites must still use Proxy
   ITRs.

8.  Discussion of Proxy ITRs (PITRs), LISP-NAT, and Proxy-ETRs (PETRs)

   In summary, there are three mechanisms for interworking LISP with
   non-LISP Sites (for both IPv4 and IPv6).  In the LISP-NAT option the
   LISP site can manage and control the interworking on its own.  In the
   PITR case, the site is not required to manage the advertisement of
   it's EID prefix into the DFZ, with the cost of potentially adding
   stretch to the connections of non-LISP sites sending packets to the
   LISP site.  The third option is Proxy-ETRs, which are optionally used
   by sites relying on PITRs case to mitigate two caveats for LISP sites
   sending packets to non-LISP sites.  This means Proxy-ETRs are not
   usually expected to be deployed by themselves, rather they will be
   used to assist LISP-NR sites which are already using PITRs.

8.1.  How Proxy-ITRs and Proxy-ETRs Interact

   There is a subtle difference between Symmetrical (LISP-NAT) vs
   Asymmetrical (Proxy-ITR and Proxy-ETR) Interworking techniques.
   Operationally, Proxy-ITRs (PITRs) and Proxy-ETRs (PETRs) can (and
   likely should) be decoupled since Proxy-ITRs are best deployed
   closest to non-LISP sites, and Proxy-ETRs are best located close to
   the LISP sites they are decapsulating for.  This asymmetric placement
   of the two network elements minimizes the stretch imposed on each
   direction of the packet flow, while still allowing for coarsely
   aggregated announcements of EIDs into the Internet's routing table.

9.  Security Considerations

   Like any router or LISP ITR, Proxy ITRs will have the opportunity to
   inspect traffic at the time that they encapsulate.  The location of
   these devices in the network can have implications for discarding
   malicious traffic on behalf of ETRs which request this behavior (via
   the drop action bit in Map-Reply packets for an EID or EID prefix).
   This is an area that would benefit from further experimentation and
   analysis.

   LISP-Interworking via Proxy-ITRs should have no impact on the
   existing network beyond what LISP ITRs and ETRs introduce when
   multihoming.  That is, if a site multi-homes today (with LISP or BGP)
   there is a possibility of asymmetric flows.

   Proxy-ITRs and Proxy-ETRs will likely be operated by organizations
   other than those of the end site receiving or sending traffic.  Care
   should be taken, then, in selecting a Proxy-ITR/Proxy-ETR provider to
   insure the quality of service meets the site's expectations.

   Proxy-ITRs and Proxy ETRs share many of the same security issues
   discussed of ITRs and ETRs.  For further information, see the
   security considerations section of [LISP].

   As with traditional NAT, LISP-NAT will obscure the actual host
   LISP-NR EID behind the LISP-R addresses used as the NAT pool.

   When LISP sites send packets to non-LISP sites (these non-LISP sites
   rely on PITRs to enable Interworking), packets will have the Site's
   EID as its source IP address.  These EIDs may not be recognized by
   their Internet Service Provider's Unicast Reverse Path Forwarding
   (uRPF) rules enabled on the Provider Edge Router.  Several options
   are available to the service provider.  For example they could enable
   a less strict version of uRPF, where they only look for the existence
   of the EID prefix in the routing table.  Another, more secure, option
   is to add a static route for the customer on the PE router, but not
   redistribute this route into the provider's routing table.  Finally,
   Proxy-ETRs can enable LISP sites to bypass this uRPF check by
   encapsulating all of their egressing traffic destined to non-LISP
   sites to the Proxy-ETR (thus ensuring the outer IP source address is
   the site's RLOC).

10.  Acknowledgments

   Thanks goes to Christian Vogt, Lixia Zhang, Robin Whittle, Michael
   Menth, and Xuewei Wang, and Noel Chiappa who have made insightful
   comments with respect to LISP Interworking and transition mechanisms.

   A special thanks goes to Scott Brim for his initial brainstorming of
   these ideas and also for his careful review.

11.  IANA Considerations

   This document creates no new requirements on IANA namespaces
   <strike><font color="red">[RFC2434].</font></strike>
   <strong><font color="green">[RFC5226].</font></strong>

12.  References

12.1.  Normative References

   [LISP]     Farinacci, D., Fuller, V., Meyer, D., and D. Lewis,
              "Locator/ID Separation Protocol (LISP)",
              draft-ietf-lisp-20 (work in progress), January 2012.

   [LISP-ALT]
              Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "LISP
              Alternative Topology (LISP+ALT)",
              draft-ietf-lisp-alt-10.txt (work in progress),
              December 2011.

   [LISP-MS]  Farinacci, D. and V. Fuller, "LISP Map Server",
              draft-ietf-lisp-ms-15.txt (work in progress),
              January 2012.

   [RFC1918]  Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and
              E. Lear, "Address Allocation for Private Internets",
              BCP 5, RFC 1918, February 1996.

   [RFC4632]  Fuller, V. and T. Li, "Classless Inter-domain Routing
              (CIDR): The Internet Address Assignment and Aggregation
              Plan", BCP 122, RFC 4632, August 2006.

12.2.  Informative References

   [CRIO]     Zhang, X., Francis, P., Wang, J., and K. Yoshida, "CRIO:
              Scaling IP Routing with the Core Router-Integrated
              Overlay", January 2006.

   [LISP-DEPLOY]
              Jakab, L., Cabellos-Aparicio, A., Coras, F., Domingo-
              Pascual, J., and D. Lewis, "LISP Network Element
              Deployment Considerations",
              draft-ietf-lisp-deployment-02.txt (work in progress),
              November 2011.

   <strike><font color="red">[RFC2434]  Narten, T. and H. Alvestrand, "Guidelines for Writing an
              IANA Considerations Section in RFCs", BCP 26, RFC 2434,
              October 1998.</font></strike>

   [RFC2993]  Hain, T., "Architectural Implications of NAT", RFC 2993,
              November 2000.

   [RFC4787]  Audet, F. and C. Jennings, "Network Address Translation
              (NAT) Behavioral Requirements for Unicast UDP", BCP 127,
              RFC 4787, January 2007.

   <strong><font color="green">[RFC5226]  Narten, T. and H. Alvestrand, "Guidelines for Writing an
              IANA Considerations Section in RFCs", BCP 26, RFC 5226,
              May 2008.</font></strong>

   [RFC5382]  Guha, S., Biswas, K., Ford, B., Sivakumar, S., and P.
              Srisuresh, "NAT Behavioral Requirements for TCP", BCP 142,
              RFC 5382, October 2008.

Authors' Addresses

   Darrel Lewis
   Cisco Systems, Inc.

   Email: darlewis@cisco.com

   David Meyer
   Cisco Systems, Inc.

   Email: dmm@cisco.com

   Dino Farinacci
   Cisco Systems, Inc.

   Email: dino@cisco.com

   Vince Fuller
   Cisco Systems, Inc.

   Email: vaf@cisco.com
</pre>

</body></html>
--Apple-Mail=_0CFF713C-A48B-42C0-A5AC-275612E32ABC
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=iso-8859-1




--Apple-Mail=_0CFF713C-A48B-42C0-A5AC-275612E32ABC
Content-Disposition: attachment;
	filename=draft-ietf-lisp-interworking-04.txt
Content-Type: text/plain;
	x-unix-mode=0644;
	name="draft-ietf-lisp-interworking-04.txt"
Content-Transfer-Encoding: quoted-printable



Network Working Group                                           D. Lewis
Internet-Draft                                                  D. Meyer
Intended status: Experimental                               D. Farinacci
Expires: August 20, 2012                                       V. Fuller
                                                     Cisco Systems, Inc.
                                                       February 17, 2012


                  Interworking LISP with IPv4 and IPv6
                  draft-ietf-lisp-interworking-04.txt

Abstract

   This document describes techniques for allowing sites running the
   Locator/ID Separation Protocol (LISP) to interoperate with Internet
   sites (which may be using either IPv4, IPv6, or both) but which are
   not running LISP.  A fundamental property of LISP speaking sites is
   that they use Endpoint Identifiers (EIDs), rather than traditional IP
   addresses, in the source and destination fields of all traffic they
   emit or receive.  While EIDs are syntactically identical to IPv4 or
   IPv6 addresses, normally routes to them are not carried in the global
   routing system so an interoperability mechanism is needed for non-
   LISP-speaking sites to exchange traffic with LISP-speaking sites.
   This document introduces three such mechanisms.  The first uses a new
   network element, the LISP Proxy Ingress Tunnel Routers (PITR)
   (Section 5) to act as a intermediate LISP Ingress Tunnel Router (ITR)
   for non-LISP-speaking hosts.  Second the document adds Network
   Address Translation (NAT) functionality to LISP Ingress and LISP
   Egress Tunnel Routers (xTRs) to substitute routable IP addresses for
   non-routable EIDs.  Finally, this document introduces a Proxy Egress
   Tunnel Router (PETR) to handle cases where a LISP ITR cannot send
   packets to non-LISP sites without encapsulation.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."




Lewis, et al.            Expires August 20, 2012                [Page 1]
=0C
Internet-Draft    Interworking LISP with IPv4 and IPv6     February 2012


   This Internet-Draft will expire on August 20, 2012.

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.



































Lewis, et al.            Expires August 20, 2012                [Page 2]
=0C
Internet-Draft    Interworking LISP with IPv4 and IPv6     February 2012


Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  LISP Interworking Models . . . . . . . . . . . . . . . . . . .  6
   3.  Definition of Terms  . . . . . . . . . . . . . . . . . . . . .  7
   4.  Routable EIDs  . . . . . . . . . . . . . . . . . . . . . . . .  8
     4.1.  Impact on Routing Table  . . . . . . . . . . . . . . . . .  8
     4.2.  Requirement for using BGP  . . . . . . . . . . . . . . . .  8
     4.3.  Limiting the Impact of Routable EIDs . . . . . . . . . . .  8
     4.4.  Use of Routable EIDs for sites transitioning to LISP . . .  8
   5.  Proxy Ingress Tunnel Routers . . . . . . . . . . . . . . . . . 10
     5.1.  PITR EID announcements . . . . . . . . . . . . . . . . . . 10
     5.2.  Packet Flow with PITRs . . . . . . . . . . . . . . . . . . 10
     5.3.  Scaling PITRs  . . . . . . . . . . . . . . . . . . . . . . 11
     5.4.  Impact of the PITRs placement in the network . . . . . . . 12
     5.5.  Benefit to Networks Deploying PITRs  . . . . . . . . . . . 12
   6.  LISP-NAT . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
     6.1.  Using LISP-NAT with LISP-NR EIDs . . . . . . . . . . . . . 13
     6.2.  LISP Sites with Hosts using RFC 1918 Addresses Sending
           to non-LISP Sites  . . . . . . . . . . . . . . . . . . . . 14
     6.3.  LISP Sites with Hosts using RFC 1918 Addresses
           Sending Packets to Other LISP Sites  . . . . . . . . . . . 14
     6.4.  LISP-NAT and multiple EIDs . . . . . . . . . . . . . . . . 15
   7.  Proxy Egress Tunnel Routers  . . . . . . . . . . . . . . . . . 16
     7.1.  Packet Flow with Proxy Egress Tunnel Routers . . . . . . . 16
   8.  Discussion of Proxy ITRs (PITRs), LISP-NAT, and Proxy-ETRs
       (PETRs)  . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
     8.1.  How Proxy-ITRs and Proxy-ETRs Interact . . . . . . . . . . 18
   9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 19
   10. Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 20
   11. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 21
   12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 22
     12.1. Normative References . . . . . . . . . . . . . . . . . . . 22
     12.2. Informative References . . . . . . . . . . . . . . . . . . 22
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 24
















Lewis, et al.            Expires August 20, 2012                [Page 3]
=0C
Internet-Draft    Interworking LISP with IPv4 and IPv6     February 2012


1.  Introduction

   This document describes interoperation between LISP [LISP] sites
   which use non-globally-routed EIDs, and non-LISP sites.  The first is
   the use of Proxy Ingress Tunnel router (PITRs), which originate
   highly-aggregated routes to EID prefixes for non-LISP sites to use.
   It also describes the use of NAT by LISP ITRs when sending packets to
   non-LISP hosts.  Finally, it describes Proxy Egress Tunnel routers
   (PETRs) LISP for sites relying on PITRs, and which are faced with
   certain restrictions.

   A key behavior of the separation of Locators and End-Point-IDs is
   that EID prefixes are normally not advertised into the Internet's
   Default Free Zone (DFZ).  Specifically, only Routing Locators (RLOCs)
   are carried in the Internet's DFZ.  Existing Internet sites (and
   their hosts) which do not run in the LISP protocol must still be able
   to reach sites numbered from LISP EID space.  This draft describes
   three mechanisms that can be used to provide reachability between
   sites that are LISP-capable and those that are not.

   The first mechanism uses a new network element, the LISP Proxy
   Ingress Tunnel Router (PITR) to act as a intermediate LISP Ingress
   Tunnel Router (ITR) for non-LISP-speaking hosts.  The second
   mechanism adds a form of Network Address Translation (NAT)
   functionality to Tunnel Routers (xTRs), to substitute routable IP
   addresses for non-routable EIDs.  The final network element is the
   LISP Proxy Egress Tunnel Routers (PETR), which act as an intermediate
   Egress Tunnel Router (ETR) for LISP sites which need to encapsulate
   packets LISP packets destined to non-LISP sites.

   More detailed descriptions of these mechanisms and the network
   elements involved may be found in the following sections:

   - Section 2 describes the different cases where interworking
   mechanisms are needed

   - Section 3 defines terms used throughout the document

   - Section 4 describes the relationship between the new EID prefix
   space and the IP address space used by the current Internet

   - Section 5 introduces and describes the operation of Proxy-ITRs

   - Section 6 defines how NAT is used by ETRs to translate non-routable
   EIDs into routable IP addresses.

   - Section 7 introduces and describes the operations of Proxy-ETRs




Lewis, et al.            Expires August 20, 2012                [Page 4]
=0C
Internet-Draft    Interworking LISP with IPv4 and IPv6     February 2012


   - Section 8 describes the relationship between asymmetric and
   Symmetric interworking mechanisms (Proxy-ITRs and Proxy-ETRs vs LISP-
   NAT)

   Note that any successful interworking model should be independent of
   any particular EID-to-RLOC mapping algorithm.  This document does not
   comment on the value of any of the particular LISP mapping systems.

   Several areas concerning the Interworking of LISP and non-LISP sites
   remain open for further study.  These areas include an examination
   the impact of LISP-NAT on internet traffic and applications,
   understanding the deployment motivations for the deployment and
   operation of Proxy Tunnel Routers, the impact of EID routes
   originated into the Internet's Default Free Zone,and the effects of
   Proxy Tunnel Routers or LISP-NAT on internet traffic and
   applications.  Until these issues are fully understood, it is
   possible that the interworking mechanisms described in this document
   are hard to deploy, or may have unintended consequences to
   applications.
































Lewis, et al.            Expires August 20, 2012                [Page 5]
=0C
Internet-Draft    Interworking LISP with IPv4 and IPv6     February 2012


2.  LISP Interworking Models

   There are 4 unicast connectivity cases which describe how sites can
   send packets to each other:

   1.  Non-LISP site to Non-LISP site

   2.  LISP site to LISP site

   3.  LISP site to Non-LISP site

   4.  Non-LISP site to LISP site

   Note that while Cases 3 and 4 seem similar, there are subtle
   differences due to the way packets are originated.

   The first case is the Internet as we know it today and as such will
   not be discussed further here.  The second case is documented in
   [LISP] and there are no new interworking requirements because there
   are no new protocol requirements placed on intermediate non- LISP
   routers.

   In case 3, LISP site to Non-LISP site, a LISP site can (in most
   cases) send packets to a non-LISP site because the non-LISP site
   prefixes are routable.  The non-LISP site need not do anything new to
   receive packets.  The only action the LISP site needs to take is to
   know when not to LISP-encapsulate packets.  An ITR knows explicitly
   that the destination is non-LISP if the destination IP address of an
   IP packet matches a (negative) Map-Cache entry which has the action
   'Natively-Forward'.

   There could be some situations where (unencapsulated) packets
   originated by a LISP site may not be forwarded to a non-LISP site.
   These cases are reviewed in section 7, (Proxy-Egress Tunnel Routers).

   Case 4, typically the most challenging, occurs when a host at a non-
   LISP site wishes to send traffic to a host at a LISP site.  If the
   source host uses a (non-globally-routable) EID as the destination IP
   address, the packet is forwarded inside the source site until it
   reaches a router which cannot forward it (due to lack of a default
   route), at which point the traffic is dropped.  For traffic not to be
   dropped, either some mechanism to make this destination EID routable
   must be in place.  Section 5 (PITRs) and Section 6 (LISP-NAT)
   describe two such mechanisms.

   Case 4 also applies to packets returning to the LISP site, in Case 3.





Lewis, et al.            Expires August 20, 2012                [Page 6]
=0C
Internet-Draft    Interworking LISP with IPv4 and IPv6     February 2012


3.  Definition of Terms

   Default Free Zone:  The Default-Free Zone (DFZ) refers to the
      collection of all Internet autonomous systems that do not require
      a default route to route a packet to any destination.

   LISP Routable (LISP-R) Site:  A LISP site whose addresses are used as
      both globally routable IP addresses and LISP EIDs.

   LISP Non-Routable (LISP-NR) Site:  A LISP site whose addresses are
      EIDs only, these EIDs are not found in the legacy Internet routing
      table.

   LISP Proxy Ingress Tunnel Router (PITR):  PITRs are used to provide
      interconnectivity between sites which use LISP EIDs and those
      which do not.  They act as gateways between those parts of the
      Internet which are not using LISP (the legacy Internet) A given
      PITR advertises one or more highly aggregated EID prefixes into
      the public Internet and acts as the ITR for traffic received from
      the public Internet.  LISP Proxy Ingress Tunnel Routers are
      described in Section 5.

   LISP Network Address Translation (LISP-NAT):  Network Address
      Translation between EID space assigned to a site and RLOC space
      also assigned to that site.  LISP Network Address Translation is
      described in Section 6.

   LISP Proxy Egress Tunnel Router (PETR):  PETRs provide a LISP
      (Routable or Non-Routable EID) site's ITRs the ability to send
      packets to non-LISP sites in cases where unencapsualted packets
      (the default mechanism) would fail to be delivered.  PETRs are
      function by having an ITR encapsulate all non-LISP destined
      traffic to a pre-configured PETR.  LISP Proxy Egress Tunnel
      Routers are described in Section 7.

    EID Sub Namespace:  A power-of-two block of aggregatable locators
      set aside for LISP interworking.

   For definitions of other terms, notably Map-Request, Map-Reply,
   Ingress Tunnel Router (ITR), and Egress Tunnel Router (ETR), please
   consult the LISP specification [LISP].










Lewis, et al.            Expires August 20, 2012                [Page 7]
=0C
Internet-Draft    Interworking LISP with IPv4 and IPv6     February 2012


4.  Routable EIDs

   An obvious way to achieve interworking between LISP and non-LISP
   hosts is for a LISP site to simply announce EID prefixes into the
   DFZ, much like the current routing system, effectively treating them
   as "Provider Independent (PI)" prefixes.  Having a site do this is
   undesirable as it defeats one of the primary goals of LISP - to
   reduce global routing system state.

4.1.  Impact on Routing Table

   If EID prefixes are announced into the DFZ, the impact is similar to
   the case in which LISP has not been deployed, because these EID
   prefixes will be no more aggregatable than existing PI addressing.
   Such a mechanism is not viewed as a viable long term solution, but
   may be a viable short term way for a site to transition a portion of
   its address space to EID space without changing its existing routing
   policy.

4.2.  Requirement for using BGP

   Non-LISP sites today use BGP to, among other things, enable ingress
   traffic engineering.  Relaxing this requirement is another primary
   design goal of LISP.

4.3.  Limiting the Impact of Routable EIDs

   Two schemes are proposed to limit the impact of having EIDs announced
   in the current global Internet routing table:

   1.  Section 5 discusses the LISP Proxy Tunnel Router, an approach
       that provides ITR functionality to bridge LISP-capable and non-
       LISP-capable sites.

   2.  Section 6 discusses another approach, LISP-NAT, in which NAT
       [RFC2993] is combined with ITR functionality to limit the impact
       of routable EIDs on the Internet routing infrastructure.

4.4.  Use of Routable EIDs for sites transitioning to LISP

   A primary design goal for LISP (and other Locator/ID separation
   proposals) is to facilitate topological aggregation of namespace used
   by the path computation, and, thus, decrease global routing system
   overhead.  Another goal is to achieve the benefits of improved
   aggregation as soon as possible.  Individual sites advertising their
   own routes for LISP EID prefixes into the global routing system is
   therefore not recommended.




Lewis, et al.            Expires August 20, 2012                [Page 8]
=0C
Internet-Draft    Interworking LISP with IPv4 and IPv6     February 2012


   That being said, single homed sites (or multi-homed sites that are
   not leaking more specific exceptions) and that are already using
   provider-aggregated prefixes can use these prefixes as LISP EIDs
   without adding state to the routing system.  In other words, such
   sites do not cause additional prefixes to be advertised.  For such
   sites, connectivity to a non-LISP sites does not require interworking
   machinery because the "PA" EIDs are already routable (they are
   effectively LISP-R type sites).  Their EIDs are found in the LISP
   mapping system, and their (aggregate) PA prefix(es) are found in the
   DFZ Internet.

   The continued announcements of an existing site's Provider
   Independent (or "PI") prefix(es) is of course under control of that
   site.  Some period of transition, where a site is found both in the
   LISP mapping system, and as a discrete prefix in the Internet routing
   system, may be a viable transition strategy.  Care should be taken
   not to advertise additional more specific LISP EID prefixes into the
   DFZ.

































Lewis, et al.            Expires August 20, 2012                [Page 9]
=0C
Internet-Draft    Interworking LISP with IPv4 and IPv6     February 2012


5.  Proxy Ingress Tunnel Routers

   Proxy Ingress Tunnel Routers (PITRs) allow for non-LISP sites to send
   packets to LISP-NR sites.  A PITR is a new network element that
   shares many characteristics with the LISP ITR.  PITRs allow non-LISP
   sites to send packets to LISP-NR sites without any changes to
   protocols or equipment at the non-LISP site.  PITRs have two primary
   functions:

   Originating EID Advertisements:  PITRs advertise highly aggregated
      EID-prefix space on behalf of LISP sites to so that non-LISP sites
      can reach them.

   Encapsulating Legacy Internet Traffic:  PITRs also encapsulate non-
      LISP Internet traffic into LISP packets and route them towards
      their destination RLOCs.

5.1.  PITR EID announcements

   A key part of PITR functionality is to advertise routes for highly-
   aggregated EID prefixes into part of the global routing system.
   Aggressive aggregation is performed to minimize the number of new
   announced routes.  In addition, careful placement of PITRs can
   greatly reduce the advertised scope of these new routes.  To this
   end, PITRs should be deployed close to non-LISP-speaking rather than
   close to LISP sites.  Such deployment not only limits the scope of
   EID-prefix route advertisements, it also allows traffic forwarding
   load to be spread among many PITRs.

5.2.  Packet Flow with PITRs

   What follows is an example of the path a packet would take when using
   a PITR.  In this example, the LISP-NR site is given the EID prefix
   192.0.2.0/24.  For the purposes of this example, neither this prefix
   or any covering aggregate are present in the global routing system.
   In other words, without the Proxy-ITR announcing 192.0.2.0/24, a
   packet with this destination were to reach a router in the "Default
   Free Zone", it would be dropped.

   A full protocol exchange example follows:

   1.  The source host makes a DNS lookup EID for destination, and gets
       192.0.2.1 in return.

   2.  The source host has a default route to customer Edge (CE) router
       and forwards the packet to the CE.





Lewis, et al.            Expires August 20, 2012               [Page 10]
=0C
Internet-Draft    Interworking LISP with IPv4 and IPv6     February 2012


   3.  The CE has a default route to its Provider Edge (PE) router, and
       forwards the packet to the PE.

   4.  The PE has route to 192.0.2.0/24 and the next hop is the PITR.

   5.  The PITR has or acquires a mapping for 192.0.2.1 and LISP
       encapsulates the packet.  The outer IP header now has a
       destination address of one of the destination EID's RLOCs.  The
       outer source address of this encapsulated packet is the PITR's
       RLOC.

   6.  The PITR looks up the RLOC, and forwards LISP packet to the next
       hop, after which, it is forwarded by other routers to the ETR's
       RLOC.

   7.  The ETR decapsulates the packet and delivers the packet to the
       192.0.2.1 host in the destination LISP site.

   8.  Packets from host 192.0.2.1 will flow back through the LISP
       site's ITR.  Such packets are not encapsulated because the ITR
       knows that the destination (the original source) is a non-LISP
       site.  The ITR knows this because it can check the LISP mapping
       database for the destination EID, and on a failure determine that
       the destination site is not LISP enabled.

   9.  Packets are then routed natively and directly to the destination
       (original source) site.

   Note that in this example the return path is asymmetric, so return
   traffic will not go back through the PITR.  This is because the
   LISP-NR site's ITR will discover that the originating site is not a
   LISP site, and not encapsulate the returning packet (see [LISP] for
   details of ITR behavior).

   The asymmetric nature of traffic flows allows the PITR to be
   relatively simple - it will only have to encapsulate LISP packets.

5.3.  Scaling PITRs

   PITRs attract traffic by announcing the LISP EID namespace into parts
   of the non-LISP-speaking global routing system.  There are several
   ways that a network could control how traffic reaches a particular
   PITR to prevent it from receiving more traffic than it can handle:

   1.  The PITR's aggregate routes might be selectively announced,
       giving a coarse way to control the quantity of traffic attracted
       by that PITR.  For example, some of the routes being announced
       might be tagged with a BGP community and their scope of



Lewis, et al.            Expires August 20, 2012               [Page 11]
=0C
Internet-Draft    Interworking LISP with IPv4 and IPv6     February 2012


       announcement limited by the routing policy of the provider.

   2.  The same address might be announced by multiple PITRs in order to
       share the traffic using IP Anycast.  The asymmetric nature of
       traffic flows through the Proxy ITR means that operationally,
       deploying a set PITRs would be very similar to existing Anycasted
       services like DNS caches.  Multiple Proxy ITRs could advertise
       the same BGP Next Hop IP address as their RLOC, and traffic would
       be attracted to the nearest Next Hop according to the network's
       IGP.

5.4.  Impact of the PITRs placement in the network

   There are several approaches that a network could take in placing
   PITRs.  Placing the PITR near the source of traffic allows for the
   communication between the non-LISP site and the LISP site to have the
   least "stretch" (i.e. the least number of forwarding hops when
   compared to an optimal path between the sites).

   Some proposals, for example Core Router-Integrated Overlay [CRIO],
   have suggested grouping PITRs near an arbitrary subset of ETRs and
   announcing a 'local' subset of EID space.  This model cannot
   guarantee minimum stretch if the EID prefix route advertisement
   points are changed (such a change might occur if a site adds,
   removes, or replaces one or more of its ISP connections).

5.5.  Benefit to Networks Deploying PITRs

   When packets destined for LISP-NR sites arrive and are encapsulated
   at a Proxy-ITR, a new LISP packet header is pre-pended.  This causes
   the packet's destination to be set to the destination ETRs RLOC.
   Because packets are thus routed towards RLOCs, it can potentially
   better follow the Proxy-ITR network's traffic engineering policies
   (such as closest exit routing).  This also means that providers which
   are not default-free and do not deploy Proxy-ITRs end up sending more
   traffic to expensive transit links (assuming their upstreams have
   deployed Proxy-ITRs) rather than to the ETR's RLOC addresses, to
   which they may well have cheaper and closer connectivity to (via, for
   example, settlement-free peering).  A corollary to this would be that
   large transit providers, deploying PITRs may attract more traffic,
   and therefore more revenue, from their customers.










Lewis, et al.            Expires August 20, 2012               [Page 12]
=0C
Internet-Draft    Interworking LISP with IPv4 and IPv6     February 2012


6.  LISP-NAT

   LISP Network Address Translation (LISP-NAT) is a limited form of NAT
   [RFC2993].  LISP-NAT is designed to enable the interworking of non-
   LISP sites and LISP-NR sites by ensuring that the LISP-NR's site
   addresses are always routable.  LISP-NAT accomplishes this by
   translating a host's source address from an 'inner' (LISP-NR EID)
   value to an 'outer' (LISP-R) value and keeping this translation in a
   table that it can reference for subsequent packets.

   In addition, existing RFC 1918 [RFC1918] sites can use LISP-NAT to
   talk to both LISP or non-LISP sites.

   The basic concept of LISP-NAT is that when transmitting a packet, the
   ITR replaces a non-routable EID source address with a routable source
   address, which enables packets to return to the site.

   There are two main cases that involve LISP-NAT:

   1.  Hosts at LISP sites that use non-routable global EIDs speaking to
       non-LISP sites using global addresses.

   2.  Hosts at LISP sites that use RFC 1918 private EIDs speaking to
       other sites, who may be either LISP or non-LISP.

   Note that LISP-NAT is not needed in the case of LISP-R (routable
   global EIDs) sources.  This case occurs when a site is announcing its
   prefix into both the LISP mapping system as well as the Internet DFZ.
   This is because the LISP-R source's address is routable, and return
   packets will be able to natively reach the site.

6.1.  Using LISP-NAT with LISP-NR EIDs

   LISP-NAT allows a host with a LISP-NR EID to send packets to non-LISP
   hosts by translating the LISP-NR EID to a globally unique address (a
   LISP-R EID).  This globally unique address may be a either a PI or PA
   address.

   An example of this translation follows.  For this example, a site has
   been assigned a LISP-NR EID of 203.0.113.0/24.  In order to utilize
   LISP-NAT, the site has also been provided the PA EID of 192.0.2.0/24,
   and uses the first address (192.0.2.1) as the site's RLOC.  The rest
   of this PA space (192.0.2.2 to 192.0.2.254) is used as a translation
   pool for this site's hosts who need to send packets to non-LISP
   hosts.

   The translation table might look like the following:




Lewis, et al.            Expires August 20, 2012               [Page 13]
=0C
Internet-Draft    Interworking LISP with IPv4 and IPv6     February 2012


          Site NR-EID     Site R-EID     Site's RLOC    Translation Pool
          =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
          203.0.113.0/24  192.0.2.0/24    192.0.2.1      192.0.2.2-254

                    Figure 1: Example Translation Table

   The Host 203.0.113.2 sends a packet (which, for the purposes of this
   example is destined for a non-LISP site) to its default route (the
   ITR).  The ITR receives the packet, and determines that the
   destination is not a LISP site.  How the ITR makes this determination
   is up to the ITRs implementation of the EID-to-RLOC mapping system
   used (see, for example [LISP-ALT]).

   The ITR then rewrites the source address of the packet from
   203.0.113.2 to 192.0.2.2, which is the first available address in the
   LISP-R EID space available to it.  The ITR keeps this translation in
   a table in order to reverse this process when receiving packets
   destined to 192.0.2.2.

   Finally, when the ITR forwards this packet without encapsulating it,
   it uses the entry in its LISP-NAT table to translate the returning
   packets' destination IPs to the proper host.

6.2.  LISP Sites with Hosts using RFC 1918 Addresses Sending to non-LISP
      Sites

   In the case where hosts using RFC 1918 addresses desire to send
   packets to non-LISP hosts, the LISP-NAT implementation acts much like
   an existing IPv4 NAT device.  The ITR providing the NAT service must
   use LISP-R EIDs for its global address pool as well as providing all
   the standard NAT functions required today.

   The source of the packet must be translated to a LISP-R EID in a
   manner similar to Section 6, and this packet must be forwarded to the
   ITR's next hop for the destination, without LISP encapsulation.

6.3.  LISP Sites with Hosts using RFC 1918 Addresses   Sending Packets
      to Other LISP Sites

   LISP-NAT allows a host with an RFC 1918 address to send packets to
   LISP hosts by translating the RFC 1918 address to a LISP EID.  After
   translation, the communication between source and destination ITR and
   ETRs continues as described in [LISP].

   An example of this translation and encapsulation follows.  For this
   example, a host has been assigned a RFC 1918 address of 192.168.1.2.
   In order to utilize LISP-NAT, the site also has been provided the
   LISP-R EID prefix of 192.0.2.0/24, and uses the first address



Lewis, et al.            Expires August 20, 2012               [Page 14]
=0C
Internet-Draft    Interworking LISP with IPv4 and IPv6     February 2012


   (192.0.2.1) as the site's RLOC.  The rest of this PA space (192.0.2.2
   to 192.0.2.254) is used as a translation pool for this site's hosts
   who need to send packets to both non-LISP and LISP hosts.

   The Host 192.168.1.2 sends a packet destined for a non-LISP site to
   its default route (the ITR).  The ITR receives the packet and
   determines that the destination is a LISP site.  How the ITR makes
   this determination is up to the ITRs implementation of the EID/RLOC
   mapping system.

   The ITR then rewrites the source address of the packet from
   192.168.1.2 to 192.0.2.2, which is the first available address in the
   LISP EID space available to it.  The ITR keeps this translation in a
   table in order to reverse this process when receiving packets
   destined to 192.0.2.2.

   The ITR then LISP encapsulates this packet (see [LISP] for details).
   The ITR uses the site's RLOC as the LISP outer header's source and
   the translation address as the LISP inner header's source.  Once it
   decapsulates returning traffic, it uses the entry in its LISP-NAT
   table to translate the returning packet's destination IP address and
   then forward to the proper host.

6.4.  LISP-NAT and multiple EIDs

   With LISP-NAT, there are two EIDs possible for a given host, the
   LISP-R EID and the LISP-NR EID.  When a site has two addresses that a
   host might use for global reachability, name-to-address directories
   may need to be modified.

   This problem, global vs. local addressability, exists for NAT in
   general, but the specific issue described above is unique to
   location/identity separation schemes.  Some of these have suggested
   running a separate DNS instance for new types of EIDs.  This solves
   the problem but introduces complexity for the site.  Alternatively,
   using PITRs can mitigate this problem, because the LISP-NR EID can be
   reached in all cases.














Lewis, et al.            Expires August 20, 2012               [Page 15]
=0C
Internet-Draft    Interworking LISP with IPv4 and IPv6     February 2012


7.  Proxy Egress Tunnel Routers

   Proxy Egress Tunnel Routers (PETRs) allow for LISP sites to send
   packets to non-LISP sites in the case where the access network does
   not allow for the LISP site send packets with the source address of
   the site's EID(s).  A PETR is a new network element that,
   conceptually, acts as an ETR for traffic destined to non-LISP sites.
   This also has the effect of allowing an ITR avoid having to decide
   whether to encapsulate packets or not - it can always encapsulate
   packets.  An ITR would encapsulate packets destined for LISP sites
   (no change here) and these would be routed directly to the
   corespondent site's ETR.  All other packets (those destined to non-
   LISP sites) will be sent to the originating site's PETR.

   There are two primary reasons why sites would want to utilize a PETR:

   Avoiding strict uRPF failures:  Some provider's access networks
      require the source of the packets emitted to be within the
      addressing scope of the access networks. (see section 9)

   Traversing a different IP Protocol:  A LISP site may want to transmit
      packets to a non-LISP site where some of the intermediate network
      does not support the particular IP protocol desired (v4 or v6).
      PETRs can allow this LISP site's data to 'hop over' this by
      utilizing LISP's support for mixed protocol encapsulation.

7.1.  Packet Flow with Proxy Egress Tunnel Routers

   Packets from a LISP site can reach a non-LISP site with the aid of a
   Proxy-ETR (or PETR).  An ITR is simply configured to send all non-
   LISP traffic, which it normally would have forwarded natively (non-
   encapsulated), to a PETR.  In the case where the ITR uses a Map-
   Resolver(s), the ITR will encapsulate packets that match the received
   Negative Map-Cache to the configured Proxy-ETR(s).  In the case where
   the ITR is connected to the mapping system directly it would
   encapsulate all packets to the configured Proxy-ETR that are cache
   misses.  Note that this outer encapsulation to the Proxy-ETR may be
   in an IP protocol other than the (inner) encapsulated data.  Routers
   then use the LISP (outer) header's destination address to route the
   packets toward the configured Proxy-ETR.

   A PETR should verify the (inner) source EID of the packet at time of
   decapsulation in order to verify that this is from a configured LISP
   site.  This is to prevent spoofed inner sources from being
   encapsulated through the Proxy-ETR.

   What follows is an example of the path a packet would take when using
   a PETR.  In this example, the LISP-NR (or LISP-R) site is given the



Lewis, et al.            Expires August 20, 2012               [Page 16]
=0C
Internet-Draft    Interworking LISP with IPv4 and IPv6     February 2012


   EID prefix 192.0.2.0/24, and it is trying to reach host at a non-LISP
   site with the IP prefix of 198.51.100.0/24.  For the purposes of this
   example, the destination (198.51.100.0/24) is found in the Internet's
   routing system.

   A full protocol exchange example follows:

   1.  The source host makes a DNS lookup for the destination, and gets
       198.51.100.100 (a Ip address of a host in the non-LISP site) in
       return.

   2.  The source host has a default route to customer Edge (CE) router
       and forwards the packet towards the CE.

   3.  The CE is a LISP ITR, and is configured to encapsulate traffic
       destined for non-LISP sites to a Proxy-ETR.

   4.  The Proxy ETR decapsulates the LISP packet and forwards the
       original packet to its next hop.

   5.  The packet is then routed natively and directly to the
       destination (non-LISP) site 198.51.100.0/24.

   Note that in this example the return path is asymmetric, so return
   traffic will not go back through the Proxy-ETR.  This means that in
   order to reach LISP-NR sites, non-LISP sites must still use Proxy
   ITRs.
























Lewis, et al.            Expires August 20, 2012               [Page 17]
=0C
Internet-Draft    Interworking LISP with IPv4 and IPv6     February 2012


8.  Discussion of Proxy ITRs (PITRs), LISP-NAT, and Proxy-ETRs (PETRs)

   In summary, there are three mechanisms for interworking LISP with
   non-LISP Sites (for both IPv4 and IPv6).  In the LISP-NAT option the
   LISP site can manage and control the interworking on its own.  In the
   PITR case, the site is not required to manage the advertisement of
   it's EID prefix into the DFZ, with the cost of potentially adding
   stretch to the connections of non-LISP sites sending packets to the
   LISP site.  The third option is Proxy-ETRs, which are optionally used
   by sites relying on PITRs case to mitigate two caveats for LISP sites
   sending packets to non-LISP sites.  This means Proxy-ETRs are not
   usually expected to be deployed by themselves, rather they will be
   used to assist LISP-NR sites which are already using PITRs.

8.1.  How Proxy-ITRs and Proxy-ETRs Interact

   There is a subtle difference between Symmetrical (LISP-NAT) vs
   Asymmetrical (Proxy-ITR and Proxy-ETR) Interworking techniques.
   Operationally, Proxy-ITRs (PITRs) and Proxy-ETRs (PETRs) can (and
   likely should) be decoupled since Proxy-ITRs are best deployed
   closest to non-LISP sites, and Proxy-ETRs are best located close to
   the LISP sites they are decapsulating for.  This asymmetric placement
   of the two network elements minimizes the stretch imposed on each
   direction of the packet flow, while still allowing for coarsely
   aggregated announcements of EIDs into the Internet's routing table.


























Lewis, et al.            Expires August 20, 2012               [Page 18]
=0C
Internet-Draft    Interworking LISP with IPv4 and IPv6     February 2012


9.  Security Considerations

   Like any router or LISP ITR, Proxy ITRs will have the opportunity to
   inspect traffic at the time that they encapsulate.  The location of
   these devices in the network can have implications for discarding
   malicious traffic on behalf of ETRs which request this behavior (via
   the drop action bit in Map-Reply packets for an EID or EID prefix).
   This is an area that would benefit from further experimentation and
   analysis.

   LISP-Interworking via Proxy-ITRs should have no impact on the
   existing network beyond what LISP ITRs and ETRs introduce when
   multihoming.  That is, if a site multi-homes today (with LISP or BGP)
   there is a possibility of asymmetric flows.

   Proxy-ITRs and Proxy-ETRs will likely be operated by organizations
   other than those of the end site receiving or sending traffic.  Care
   should be taken, then, in selecting a Proxy-ITR/Proxy-ETR provider to
   insure the quality of service meets the site's expectations.

   Proxy-ITRs and Proxy ETRs share many of the same security issues
   discussed of ITRs and ETRs.  For further information, see the
   security considerations section of [LISP].

   As with traditional NAT, LISP-NAT will obscure the actual host
   LISP-NR EID behind the LISP-R addresses used as the NAT pool.

   When LISP sites send packets to non-LISP sites (these non-LISP sites
   rely on PITRs to enable Interworking), packets will have the Site's
   EID as its source IP address.  These EIDs may not be recognized by
   their Internet Service Provider's Unicast Reverse Path Forwarding
   (uRPF) rules enabled on the Provider Edge Router.  Several options
   are available to the service provider.  For example they could enable
   a less strict version of uRPF, where they only look for the existence
   of the EID prefix in the routing table.  Another, more secure, option
   is to add a static route for the customer on the PE router, but not
   redistribute this route into the provider's routing table.  Finally,
   Proxy-ETRs can enable LISP sites to bypass this uRPF check by
   encapsulating all of their egressing traffic destined to non-LISP
   sites to the Proxy-ETR (thus ensuring the outer IP source address is
   the site's RLOC).










Lewis, et al.            Expires August 20, 2012               [Page 19]
=0C
Internet-Draft    Interworking LISP with IPv4 and IPv6     February 2012


10.  Acknowledgments

   Thanks goes to Christian Vogt, Lixia Zhang, Robin Whittle, Michael
   Menth, and Xuewei Wang, and Noel Chiappa who have made insightful
   comments with respect to LISP Interworking and transition mechanisms.

   A special thanks goes to Scott Brim for his initial brainstorming of
   these ideas and also for his careful review.











































Lewis, et al.            Expires August 20, 2012               [Page 20]
=0C
Internet-Draft    Interworking LISP with IPv4 and IPv6     February 2012


11.  IANA Considerations

   This document creates no new requirements on IANA namespaces
   [RFC5226].















































Lewis, et al.            Expires August 20, 2012               [Page 21]
=0C
Internet-Draft    Interworking LISP with IPv4 and IPv6     February 2012


12.  References

12.1.  Normative References

   [LISP]     Farinacci, D., Fuller, V., Meyer, D., and D. Lewis,
              "Locator/ID Separation Protocol (LISP)",
              draft-ietf-lisp-20 (work in progress), January 2012.

   [LISP-ALT]
              Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "LISP
              Alternative Topology (LISP+ALT)",
              draft-ietf-lisp-alt-10.txt (work in progress),
              December 2011.

   [LISP-MS]  Farinacci, D. and V. Fuller, "LISP Map Server",
              draft-ietf-lisp-ms-15.txt (work in progress),
              January 2012.

   [RFC1918]  Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and
              E. Lear, "Address Allocation for Private Internets",
              BCP 5, RFC 1918, February 1996.

   [RFC4632]  Fuller, V. and T. Li, "Classless Inter-domain Routing
              (CIDR): The Internet Address Assignment and Aggregation
              Plan", BCP 122, RFC 4632, August 2006.

12.2.  Informative References

   [CRIO]     Zhang, X., Francis, P., Wang, J., and K. Yoshida, "CRIO:
              Scaling IP Routing with the Core Router-Integrated
              Overlay", January 2006.

   [LISP-DEPLOY]
              Jakab, L., Cabellos-Aparicio, A., Coras, F., Domingo-
              Pascual, J., and D. Lewis, "LISP Network Element
              Deployment Considerations",
              draft-ietf-lisp-deployment-02.txt (work in progress),
              November 2011.

   [RFC2993]  Hain, T., "Architectural Implications of NAT", RFC 2993,
              November 2000.

   [RFC4787]  Audet, F. and C. Jennings, "Network Address Translation
              (NAT) Behavioral Requirements for Unicast UDP", BCP 127,
              RFC 4787, January 2007.

   [RFC5226]  Narten, T. and H. Alvestrand, "Guidelines for Writing an
              IANA Considerations Section in RFCs", BCP 26, RFC 5226,



Lewis, et al.            Expires August 20, 2012               [Page 22]
=0C
Internet-Draft    Interworking LISP with IPv4 and IPv6     February 2012


              May 2008.

   [RFC5382]  Guha, S., Biswas, K., Ford, B., Sivakumar, S., and P.
              Srisuresh, "NAT Behavioral Requirements for TCP", BCP 142,
              RFC 5382, October 2008.














































Lewis, et al.            Expires August 20, 2012               [Page 23]
=0C
Internet-Draft    Interworking LISP with IPv4 and IPv6     February 2012


Authors' Addresses

   Darrel Lewis
   Cisco Systems, Inc.

   Email: darlewis@cisco.com


   David Meyer
   Cisco Systems, Inc.

   Email: dmm@cisco.com


   Dino Farinacci
   Cisco Systems, Inc.

   Email: dino@cisco.com


   Vince Fuller
   Cisco Systems, Inc.

   Email: vaf@cisco.com



























Lewis, et al.            Expires August 20, 2012               [Page 24]
=0C

--Apple-Mail=_0CFF713C-A48B-42C0-A5AC-275612E32ABC
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=iso-8859-1



-Darrel



--Apple-Mail=_0CFF713C-A48B-42C0-A5AC-275612E32ABC--

From jmh@joelhalpern.com  Sat Feb 18 11:25:14 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 69A7021F8573; Sat, 18 Feb 2012 11:25:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y1bKk0LDdgQn; Sat, 18 Feb 2012 11:25:14 -0800 (PST)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id EBA6E21F856D; Sat, 18 Feb 2012 11:25:13 -0800 (PST)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by morbo.tigertech.net (Postfix) with ESMTP id C736ECD0F3; Sat, 18 Feb 2012 11:25:13 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 42E221BC907D; Sat, 18 Feb 2012 11:25:13 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [172.17.114.244] (207.47.24.2.static.nextweb.net [207.47.24.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 082801BC9079; Sat, 18 Feb 2012 11:25:13 -0800 (PST)
Message-ID: <4F3FFB16.6030502@joelhalpern.com>
Date: Sat, 18 Feb 2012 14:25:10 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: gen-art@ietf.org
References: <4F3D931C.1000101@nostrum.com>
In-Reply-To: <4F3D931C.1000101@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: cabo@tsi.org, Peter Saint-Andre <stpeter@stpeter.im>, core@ietf.org
Subject: [Gen-art]  Review: draft-ietf-core-link-format-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: Sat, 18 Feb 2012 19:25:14 -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-core-link-format-11
     CoRE Link Format
Reviewer: Joel M. Halpern
Review Date: 18-Feb 2012
IETF LC End Date: 28-Feb-2012
IESG Telechat date: N/A

Summary: This document is almost ready for publication as a proposed 
standard.

Major issues:
     What is the registration / collision avoidance strategy for 
resource type (rt) and interface description (if) values?  They are both 
defined as opaque strings which can happen to be URIs.  So there seems 
to be potential for collision.

Minor issues:
     Would it be sensible, in the introduction, when the well-known URI 
is first introduced, to refer to it as a "well-known relative URI"?
     Should this document register a resource type (rt) and interface 
description (if) for the server resource manager itself?  The text 
refers to using multicast to find resources, with filtering based on rt 
and if.  (This would, I think, be defined in section 4, and registered 
in the IANA considerations section?)  Presumably all devices would 
support the interface, which is why a resource type for the master 
server would seem useful.

Nits/editorial comments:

From jmh@joelhalpern.com  Sat Feb 18 12:12:58 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 2331F21F847A for <gen-art@ietfa.amsl.com>; Sat, 18 Feb 2012 12:12:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KspymFQPa9vA for <gen-art@ietfa.amsl.com>; Sat, 18 Feb 2012 12:12:57 -0800 (PST)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 9D22321F8473 for <gen-art@ietf.org>; Sat, 18 Feb 2012 12:12:57 -0800 (PST)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by morbo.tigertech.net (Postfix) with ESMTP id 8F8FACD011 for <gen-art@ietf.org>; Sat, 18 Feb 2012 12:12:57 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 72F071BC78FE; Sat, 18 Feb 2012 12:12:57 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [172.17.114.244] (207.47.24.2.static.nextweb.net [207.47.24.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 3B7341BC78FB; Sat, 18 Feb 2012 12:12:57 -0800 (PST)
Message-ID: <4F400646.60906@joelhalpern.com>
Date: Sat, 18 Feb 2012 15:12:54 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: gen-art@ietf.org
References: <4F3D931C.1000101@nostrum.com>
In-Reply-To: <4F3D931C.1000101@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Jari Arkko <jari.arkko@piuha.net>, draft-garcia-shim6-applicability@tools.ietf.org
Subject: [Gen-art]  Review: draft-garcia-shim6-applicability-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: Sat, 18 Feb 2012 20:12:58 -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-garcia-shim6-applicability-03
     Applicability Statement for the Level 3 Multihoming Shim Protocol
                                 (Shim6)
Reviewer: Joel M. Halpern
Review Date: 18-Feb-2012
IETF LC End Date: 14-March-2012
IESG Telechat date: N/A

Summary: This document is almost ready for publication as an information rfc

Major issues:
     The third paragraph of the introduction makes assertions about PI 
based multihoming being "not generally available to end sites due to a 
strict policy of route aggregation in the DFZ."  As far as I know, this 
is simply not the case.  RIRs sell IPv6 PI for reasonable fees.  Most 
operators accept PI advertisements from customers.  And those 
advertisements are passed on to other ISP, and accepted.  I would 
recommend removal of the first sentence of this paragraph.  Instead, it 
needs to be noted that PI based multihoming can be done with IPv6, and 
then point to the scaling concerns.


Moderate Issues:
     I am unable to understand the sentence "Shim6 has no means to 
enforce neither host nor network forwarding for a given locator to be 
used as source address."  I presume that what it is intended to 
communicate is simply a fact about shim6.  Please rewrite.

     If I am reading section 7.1.1 on MobileIPv6/Shim6 interaction, it 
looks like you are describing a scenario in which the mobile node uses 
multiple HOAs as locators with a correspondent node.  I would suggest 
that this section would be clearer if the communicating parties were 
identified.  I suspect that the intended behavioral assumption is that 
the mobile node will register its CoA multiple times, once with each 
home address.  But this does not seem to be stated explicitly.


Minor issues:
     In th long comparative paragraph in the introduction, "The Shim6 
approach is thought to have better scaling properties with respect to 
the state held in the DFZ than the IPv approach." Could "IPv 4 approach 
be replaced with "PI approach"?

     In section 7.7 on the interaction with NPT66, I think it would be 
helped by a bit more discussion of when certain shim6 messages are 
exchanged, and which fields are validated.  Specifically, I can not tell 
if it is ever possible to get a shim6 ULID-pair option through an NPT66 
which is rewriting the one of the addresses prefixes in the packet.  I 
suspect not.  If indeed it just won't work, this needs to be stated MUCH 
more clearly.

Yours,
Joel M. Halpern


Nits/editorial comments:

From brian.e.carpenter@gmail.com  Sat Feb 18 17:10: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 CFD8A21E8011 for <gen-art@ietfa.amsl.com>; Sat, 18 Feb 2012 17:10:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.505
X-Spam-Level: 
X-Spam-Status: No, score=-103.505 tagged_above=-999 required=5 tests=[AWL=0.094, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yjb9jvfcC8j3 for <gen-art@ietfa.amsl.com>; Sat, 18 Feb 2012 17:10:15 -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 A1B7221F8545 for <gen-art@ietf.org>; Sat, 18 Feb 2012 17:10:14 -0800 (PST)
Received: by eekc41 with SMTP id c41so1802616eek.31 for <gen-art@ietf.org>; Sat, 18 Feb 2012 17:10:13 -0800 (PST)
Received-SPF: pass (google.com: domain of brian.e.carpenter@gmail.com designates 10.213.9.8 as permitted sender) client-ip=10.213.9.8;
Authentication-Results: mr.google.com; spf=pass (google.com: domain of brian.e.carpenter@gmail.com designates 10.213.9.8 as permitted sender) smtp.mail=brian.e.carpenter@gmail.com; dkim=pass header.i=brian.e.carpenter@gmail.com
Received: from mr.google.com ([10.213.9.8]) by 10.213.9.8 with SMTP id j8mr974411ebj.27.1329613813881 (num_hops = 1); Sat, 18 Feb 2012 17:10:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Ia4yqVYf/RnPtN/T8w/512kXgr0gLtKVJ20A+pqmHpg=; b=iux64phJ/H1EftqK1ZZA2923B/Jtf56OAZMtglMPa4gR5IkhD8pdf0c0kaLHj4K26T el9kjWGsPzMTxiZrKjjZTLBEdU3686LwhVU3lJvuc9l+2DPeiD0YOPMP0Cs6O8QM1mK2 i9stT1oSd+GMieFVcUf4g0JFTZH5hBB0gyCHY=
Received: by 10.213.9.8 with SMTP id j8mr772030ebj.27.1329613812092; Sat, 18 Feb 2012 17:10:12 -0800 (PST)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id w60sm58248006eeb.4.2012.02.18.17.10.07 (version=SSLv3 cipher=OTHER); Sat, 18 Feb 2012 17:10:11 -0800 (PST)
Message-ID: <4F404BE9.5070108@gmail.com>
Date: Sun, 19 Feb 2012 14:10:01 +1300
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: "Joel M. Halpern" <jmh@joelhalpern.com>
References: <4F3D931C.1000101@nostrum.com> <4F400646.60906@joelhalpern.com>
In-Reply-To: <4F400646.60906@joelhalpern.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, Jari Arkko <jari.arkko@piuha.net>, draft-garcia-shim6-applicability@tools.ietf.org
Subject: Re: [Gen-art] Review: draft-garcia-shim6-applicability-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: Sun, 19 Feb 2012 01:10:22 -0000

Joel,

Writing as an interested party, not a reviewer:


On 2012-02-19 09:12, Joel M. Halpern 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-garcia-shim6-applicability-03
>     Applicability Statement for the Level 3 Multihoming Shim Protocol
>                                 (Shim6)
> Reviewer: Joel M. Halpern
> Review Date: 18-Feb-2012
> IETF LC End Date: 14-March-2012
> IESG Telechat date: N/A
> 
> Summary: This document is almost ready for publication as an information
> rfc
> 
> Major issues:
>     The third paragraph of the introduction makes assertions about PI
> based multihoming being "not generally available to end sites due to a
> strict policy of route aggregation in the DFZ."  As far as I know, this
> is simply not the case.  RIRs sell IPv6 PI for reasonable fees.  Most
> operators accept PI advertisements from customers.  And those
> advertisements are passed on to other ISP, and accepted.  I would
> recommend removal of the first sentence of this paragraph.  Instead, it
> needs to be noted that PI based multihoming can be done with IPv6, and
> then point to the scaling concerns.

Yes, the point is that PI doesn't scale to ten million sites,
but shim6 does. That should be clarified.

> 
> 
> Moderate Issues:
>     I am unable to understand the sentence "Shim6 has no means to
> enforce neither host nor network forwarding for a given locator to be
> used as source address."  I presume that what it is intended to
> communicate is simply a fact about shim6.  Please rewrite.

It's a fact. In fact, it's a fact that seriously impacts shim6
deployability, according to the experience of a student of mine.
Getting the appropriate locator pair out of a host, through the
appropriate edge router and ISP link, and through the firewall
at the far end, and doing the whole thing again in the reverse
direction, is a significant configuration challenge.

   Brian

> 
>     If I am reading section 7.1.1 on MobileIPv6/Shim6 interaction, it
> looks like you are describing a scenario in which the mobile node uses
> multiple HOAs as locators with a correspondent node.  I would suggest
> that this section would be clearer if the communicating parties were
> identified.  I suspect that the intended behavioral assumption is that
> the mobile node will register its CoA multiple times, once with each
> home address.  But this does not seem to be stated explicitly.
> 
> 
> Minor issues:
>     In th long comparative paragraph in the introduction, "The Shim6
> approach is thought to have better scaling properties with respect to
> the state held in the DFZ than the IPv approach." Could "IPv 4 approach
> be replaced with "PI approach"?
> 
>     In section 7.7 on the interaction with NPT66, I think it would be
> helped by a bit more discussion of when certain shim6 messages are
> exchanged, and which fields are validated.  Specifically, I can not tell
> if it is ever possible to get a shim6 ULID-pair option through an NPT66
> which is rewriting the one of the addresses prefixes in the packet.  I
> suspect not.  If indeed it just won't work, this needs to be stated MUCH
> more clearly.
> 
> Yours,
> Joel M. Halpern
> 
> 
> Nits/editorial comments:
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art
> 

From suresh.krishnan@ericsson.com  Mon Feb 20 07:03:37 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 CFD7E21F8790 for <gen-art@ietfa.amsl.com>; Mon, 20 Feb 2012 07:03:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.17
X-Spam-Level: 
X-Spam-Status: No, score=-106.17 tagged_above=-999 required=5 tests=[AWL=0.429, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MAVOqiSWDLAN for <gen-art@ietfa.amsl.com>; Mon, 20 Feb 2012 07:03:33 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id C31A821F878E for <gen-art@ietf.org>; Mon, 20 Feb 2012 07:03:33 -0800 (PST)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q1KF2wfb013946; Mon, 20 Feb 2012 09:03:33 -0600
Received: from [142.133.180.108] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.31) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 20 Feb 2012 10:03:23 -0500
Message-ID: <4F42609D.3020300@ericsson.com>
Date: Mon, 20 Feb 2012 10:02:53 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20111229 Thunderbird/9.0
MIME-Version: 1.0
To: General Area Review Team <gen-art@ietf.org>, <draft-ietf-simple-chat.all@tools.ietf.org>
X-Enigmail-Version: 1.3.4
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: [Gen-art] Gen-ART review of draft-ietf-simple-chat-13.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: Mon, 20 Feb 2012 15:03:37 -0000

I am the assigned Gen-ART reviewer for
draft-ietf-simple-chat-13.txt

For background on Gen-ART, please see the FAQ at
<http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html>.

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

Summary: This draft is ready for publication as a Proposed Standard but
I have a few comments.

Section 3:

REQ-3: It is unclear why this is separate from REQ-2. In my reading,
REQ-2 already covers REQ-3.

Section 6.1

This sentence is not clear. Can you clarify/reword.

"Having the header of the Message/CPIM wrapper only in the first chunk,
the MSRP switch MUST track the Message-Id until the last chunk of the
message has been distributed."

Thanks
Suresh











From gonzalo.camarillo@ericsson.com  Tue Feb 21 00:36:17 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 44BD821F8545 for <gen-art@ietfa.amsl.com>; Tue, 21 Feb 2012 00:36:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.142
X-Spam-Level: 
X-Spam-Status: No, score=-110.142 tagged_above=-999 required=5 tests=[AWL=0.457, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LlB54xyyqzEM for <gen-art@ietfa.amsl.com>; Tue, 21 Feb 2012 00:36:13 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id AA9B821F8555 for <gen-art@ietf.org>; Tue, 21 Feb 2012 00:36:12 -0800 (PST)
X-AuditID: c1b4fb3d-b7bb7ae0000007b2-0f-4f43577aa458
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 6C.13.01970.A77534F4; Tue, 21 Feb 2012 09:36:11 +0100 (CET)
Received: from [131.160.36.93] (153.88.115.8) by esessmw0237.eemea.ericsson.se (153.88.115.91) with Microsoft SMTP Server id 8.3.213.0; Tue, 21 Feb 2012 09:36:07 +0100
Message-ID: <4F435777.8080407@ericsson.com>
Date: Tue, 21 Feb 2012 10:36:07 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
References: <4F42609D.3020300@ericsson.com>
In-Reply-To: <4F42609D.3020300@ericsson.com>
X-Enigmail-Version: 1.3.4
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Cc: "draft-ietf-simple-chat.all@tools.ietf.org" <draft-ietf-simple-chat.all@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-simple-chat-13.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, 21 Feb 2012 08:36:17 -0000

Hi Suresh,

thanks for your review. The authors will take care of these comments in
the next revision of the draft.

Cheers,

Gonzalo

On 20/02/2012 5:02 PM, Suresh Krishnan wrote:
> I am the assigned Gen-ART reviewer for
> draft-ietf-simple-chat-13.txt
> 
> For background on Gen-ART, please see the FAQ at
> <http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html>.
> 
> Please resolve these comments along with any other Last Call comments
> you may receive.
> 
> Summary: This draft is ready for publication as a Proposed Standard but
> I have a few comments.
> 
> Section 3:
> 
> REQ-3: It is unclear why this is separate from REQ-2. In my reading,
> REQ-2 already covers REQ-3.
> 
> Section 6.1
> 
> This sentence is not clear. Can you clarify/reword.
> 
> "Having the header of the Message/CPIM wrapper only in the first chunk,
> the MSRP switch MUST track the Message-Id until the last chunk of the
> message has been distributed."
> 
> Thanks
> Suresh
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 


From miguel.a.garcia@ericsson.com  Tue Feb 21 03:19:40 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 7903321F8712 for <gen-art@ietfa.amsl.com>; Tue, 21 Feb 2012 03:19:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.346
X-Spam-Level: 
X-Spam-Status: No, score=-10.346 tagged_above=-999 required=5 tests=[AWL=0.253, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oL6k5KbN4Asl for <gen-art@ietfa.amsl.com>; Tue, 21 Feb 2012 03:19:36 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id 907FE21F871D for <gen-art@ietf.org>; Tue, 21 Feb 2012 03:19:31 -0800 (PST)
X-AuditID: c1b4fb39-b7bf2ae0000069a1-b9-4f437dc2d575
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id FF.8C.27041.2CD734F4; Tue, 21 Feb 2012 12:19:30 +0100 (CET)
Received: from [159.107.24.228] (153.88.115.8) by esessmw0184.eemea.ericsson.se (153.88.115.82) with Microsoft SMTP Server id 8.3.213.0; Tue, 21 Feb 2012 12:19:29 +0100
Message-ID: <4F437DC0.6090707@ericsson.com>
Date: Tue, 21 Feb 2012 12:19:28 +0100
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
References: <4F42609D.3020300@ericsson.com>
In-Reply-To: <4F42609D.3020300@ericsson.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Cc: Geir Arne Sandbakken <geirsand@cisco.com>, General Area Review Team <gen-art@ietf.org>, "aki.niemi@nokia.com" <aki.niemi@nokia.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-simple-chat-13.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, 21 Feb 2012 11:19:40 -0000

Hi Suresh,

Thanks for your review. Please see inline answers.

On 20/02/2012 16:02, Suresh Krishnan wrote:
> I am the assigned Gen-ART reviewer for
> draft-ietf-simple-chat-13.txt
>
> For background on Gen-ART, please see the FAQ at
> <http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html>.
>
> Please resolve these comments along with any other Last Call comments
> you may receive.
>
> Summary: This draft is ready for publication as a Proposed Standard but
> I have a few comments.
>
> Section 3:
>
> REQ-3: It is unclear why this is separate from REQ-2. In my reading,
> REQ-2 already covers REQ-3.

OK, makes sense. We can merge these requirements.

>
> Section 6.1
>
> This sentence is not clear. Can you clarify/reword.
>
> "Having the header of the Message/CPIM wrapper only in the first chunk,
> the MSRP switch MUST track the Message-Id until the last chunk of the
> message has been distributed."

Ok, we will clarify it.

Thanks,

        Miguel

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

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

From tom.taylor.stds@gmail.com  Wed Feb 22 11:54:57 2012
Return-Path: <tom.taylor.stds@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 1DA0A21E800E; Wed, 22 Feb 2012 11:54:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.556
X-Spam-Level: 
X-Spam-Status: No, score=-3.556 tagged_above=-999 required=5 tests=[AWL=0.043,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4ZEcfss9H-bu; Wed, 22 Feb 2012 11:54:56 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 952A821E8010; Wed, 22 Feb 2012 11:54:51 -0800 (PST)
Received: by yenm3 with SMTP id m3so299365yen.31 for <multiple recipients>; Wed, 22 Feb 2012 11:54:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding:x-antivirus :x-antivirus-status; bh=f29WNWi/gKEU9HsPx+6o3wlXumTPODmRfwjGhl5/8rI=; b=LSDKwb7pCv4sp4OSA6V2MrURPTbK33JdpW4MmBaNJr5skrFsJ+ayz69fTF98t2i38c j6b++dqTnOYw3cWSwRvULZ98QIrCL9ALpkCIydZpR7itgZtr+kU200mvBubWEff6+IkA UuADu4P4tkbfkDcXav0DXc3I5cWH9W1unGORc=
Received: by 10.236.76.234 with SMTP id b70mr35071663yhe.125.1329940491184; Wed, 22 Feb 2012 11:54:51 -0800 (PST)
Received: from [127.0.0.1] ([216.254.195.91]) by mx.google.com with ESMTPS id n12sm65161722yhe.10.2012.02.22.11.54.49 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 22 Feb 2012 11:54:50 -0800 (PST)
Message-ID: <4F454808.7000106@gmail.com>
Date: Wed, 22 Feb 2012 14:54:48 -0500
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: pcn <pcn@ietf.org>, Fortune Huang <fqhuang@huawei.com>,  Anna Charny <anna@mwsm.com>, Michael Menth <menth@informatik.uni-wuerzburg.de>,  Georgios Karagiannis <karagian@cs.utwente.nl>, "Joel M. Halpern" <jmh@joelhalpern.com>,  'Brian Carpenter' <brian@cs.auckland.ac.nz>, gen-art@ietf.org, David Harrington <ietfdbh@comcast.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 120222-0, 22/02/2012), Outbound message
X-Antivirus-Status: Clean
Subject: [Gen-art] draft-ietf-pcn-cl-edge-behaviour-12.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, 22 Feb 2012 19:54:57 -0000

I have just submitted draft-ietf-pcn-cl-edge-behaviour-12.txt, 
incorporating responses to the Genart reviews by Joel Halpern and Brian 
Carpenter. Thanks to both of them for their suggestions. The set of 
changes to the CL edge behaviour draft is as follows:

1. Introduction
===============

Added the following paragraph in response to a concern expressed by 
Brian. Further related text is described later.

    Note that the terms "block" or "terminate" actually translate to
    one or more of several possible courses of action, as discussed
    in Section 3.6 of RFC5559. The choice of which action to take
    for blocked or terminated flows is a matter of local policy.

Deleted the following text from the RFC Editor's note, on Brian's 
recommendation:

    You may choose to delete the following paragraph and the
    "[CL-specific]" tags throughout this document when publishing
    it, since they are present primarily to aid reviewers.

3. Node Behaviours
==================

Added the following paragraph at the end of the introductory text to 
this section:

    Section 5.1.2 describes how to derive the filters by means of
    which PCN-ingress-nodes and PCN-egress-nodes are able to classify
    incoming packets into ingress-egress-aggregates.

3.3.3. Decision Point Action For Missing PCN-Boundary-Node Reports
==================================================================

Changed the paragraph dealing with egress node reporting timeouts:

OLD

    If timer t-recvFail expires for a given PCN-egress-node, the
    Decision Point SHOULD notify management. A Decision Point
    collocated with a PCN-ingress-node SHOULD cease to admit
    PCN-flows to the ingress-egress-aggregate associated with the
    given PCN-egress-node, until it again receives a report from
    that node. A centralized Decision Point MAY cease to admit
    PCN-flows to all ingress-egress-aggregates destined to the
    PCN-egress-node concerned, until it again receives a report
    from that node.

NEW

    If timer t-recvFail expires for a given PCN-egress-node, the
    Decision Point SHOULD notify management. A log format is
    defined for that purpose in Section 5.2.1.1. Other actions
    depend on local policy, but MAY include blocking of new flows
    destined for the PCN-egress-node concerned until another report
    is received from it. Termination of already-admitted flows is
    also possible, but could be triggered by the receipt of
    "Destination unreachable" messages at the PCN-ingress-node.

5.1.2. Specification of Node- and Link-Specific Parameters
==========================================================

Replaced the first three paragraphs of this section:

OLD

    Each PCN-ingress-node needs filters to classify incoming PCN packets
    according to ingress-egress-aggregate, both to satisfy Decision Point
    requests for sent traffic rates and, if applicable, to support
    encapsulation.  If PCN packets are being tunneled to the PCN-egress-
    nodes (encapsulation), the PCN-ingress-node also needs the address of
    the PCN-egress-node for each ingress-egress-aggregate.

    Each PCN-egress-node needs filters to classify incoming PCN packets
    by ingress-egress-aggregate, in order to gather measurements on a
    per-aggregate basis.  The PCN-egress-node also needs to know the
    address of the Decision Point to which it sends reports for each
    ingress-egress-aggregate.

    If [I-D.tsvwg-rsvp-pcn] is deployed and the Decision Points are
    collocated with the PCN-ingress-nodes, this information can be built
    up dynamically from the contents of the end-to-end RSVP signalling
    and does not have to be pre-configured.  Otherwise the filters have
    to be derived from the routing tables in use in the domain, and the
    address of the peer at the other end of each ingress-egress-aggregate
    has to be tabulated for each PCN-edge-node.

NEW

    Filters are required at both the PCN-ingress-node and the PCN-egress-
    node to classify incoming PCN packets by ingress-egress-aggregate.
    Because of the potential use of multi-path routing in domains
    upstream of the PCN-domain, it is impossible to do such
    classification reliably at the PCN-egress-node based on the packet
    header contents as originally received at the PCN-ingress-node.
    (Packets with the same header contents could enter the PCN-domain at
    multiple PCN-ingress-nodes.)  As a result, the only way to construct
    such filters reliably is to tunnel the packets from the PCN-ingress-
    node to the PCN-egress-node.

    The PCN-ingress-node needs filters in order to place PCN packets into
    the right tunnel in the first instance, and also to satisfy requests
    from the Decision Point for admission rates into specific ingress-
    egress-aggregates.  These filters select the PCN-egress-node, but not
    necessarily a specific path through the network to that node.  As a
    result, they are likely to be stable even in the face of failures in
    the network, except when the PCN-egress-node itself becomes
    unreachable.  The primary basis for their derivation will be routing
    policy given the packet's original origin and destination.  Since all
    PCN packets will be tunneled, the PCN-ingress-node also needs to know
    the address of the peer PCN-egress-node associated with each filter.

    Operators may wish to give some thought to the provisioning of
    alternate egress points for some or all ingress-egress aggregates in
    case of failure of the PCN-egress-node.  This could require the
    setting up of standby tunnels to these alternate egress points.

    Each PCN-egress-node needs filters to classify incoming PCN packets
    by ingress-egress-aggregate, in order to gather measurements on a
    per-aggregate basis.  These filters are constructed on the basis of
    the identifier of the tunnel from which the incoming packet has
    emerged (e.g. the source address in the outer header if IP
    encapsulation is used).  The PCN-egress-node also needs to know the
    address of the Decision Point to which it sends reports for each
    ingress-egress-aggregate.

5.2.1.  Event Logging In the PCN Domain
=======================================

Added the following paragraph:

    The field names (e.g., HOSTNAME, STRUCTURED-DATA) used in the
    following subsections are defined in [RFC5424].	
			

From tom.taylor.stds@gmail.com  Wed Feb 22 12:52:48 2012
Return-Path: <tom.taylor.stds@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 CB60E21F8646; Wed, 22 Feb 2012 12:52:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.562
X-Spam-Level: 
X-Spam-Status: No, score=-3.562 tagged_above=-999 required=5 tests=[AWL=0.038,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AWmI4MR6-IKe; Wed, 22 Feb 2012 12:52:42 -0800 (PST)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id BCC1421F8645; Wed, 22 Feb 2012 12:52:41 -0800 (PST)
Received: by ghbg16 with SMTP id g16so337221ghb.31 for <multiple recipients>; Wed, 22 Feb 2012 12:52:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding:x-antivirus :x-antivirus-status; bh=4NdT7uxsATCb6hXu58jf3v5IEv65hBtYGbZ0t+fnn6k=; b=ql4agwQMiHkYjBNgm2O+VaxqwYLOXScmz6SA1Z8GcYKtd4s9mwBT4F7tXt6M/gypvE HK27mDM0K3eJRWflEQ3+CfqSuZm0A6pXp4JZ4jyTZ0hUR5niowbAJlW//Aw4blHHuCGc 03/xl2bM+nTAgpGgT7IxcuDKwpjpigY4ucjtI=
Received: by 10.236.37.132 with SMTP id y4mr36695182yha.10.1329943960827; Wed, 22 Feb 2012 12:52:40 -0800 (PST)
Received: from [127.0.0.1] ([216.254.195.91]) by mx.google.com with ESMTPS id s10sm11821512anl.17.2012.02.22.12.52.39 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 22 Feb 2012 12:52:40 -0800 (PST)
Message-ID: <4F455597.2060104@gmail.com>
Date: Wed, 22 Feb 2012 15:52:39 -0500
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: pcn <pcn@ietf.org>, Anna Charny <anna@mwsm.com>,  Georgios Karagiannis <karagian@cs.utwente.nl>, Michael Menth <menth@informatik.uni-wuerzburg.de>,  "Joel M. Halpern" <jmh@joelhalpern.com>, 'Brian Carpenter' <brian@cs.auckland.ac.nz>,  David Harrington <ietfdbh@comcast.net>, Gen Art <gen-art@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 120222-0, 22/02/2012), Outbound message
X-Antivirus-Status: Clean
Subject: [Gen-art] draft-ietf-pcn-sm-edge-behaviour-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: Wed, 22 Feb 2012 20:52:49 -0000

I have now posted draft-ietf-pcn-sm-edge-behaviour-09 with similar 
changes to the CL edge behaviour draft. I forgot to mention deletion of 
the following bullet from Section 2:

    o the PCN-domain satisfies the conditions specified in [RFC5696];

I apologize to Joel and Brian that I forgot to add them to the 
Acknowledgements section in the CL draft. I'll fix that in AUTH48, if it 
ever comes. I did fix add them in the SM draft.

Tom Taylor

From ron.even.tlv@gmail.com  Wed Feb 22 15:40:06 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 C9EA121E8050; Wed, 22 Feb 2012 15:40:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.367
X-Spam-Level: 
X-Spam-Status: No, score=-3.367 tagged_above=-999 required=5 tests=[AWL=0.231,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wpwZvZ4wAJrx; Wed, 22 Feb 2012 15:40:06 -0800 (PST)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 02BC721F8531; Wed, 22 Feb 2012 15:40:01 -0800 (PST)
Received: by eaal12 with SMTP id l12so261733eaa.31 for <multiple recipients>; Wed, 22 Feb 2012 15:40:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; bh=KQhhBURyITiGAXIL35LoeX3T1R6+AZ/hnxt2aQ046Lo=; b=KF2bj7yKPea0I2gp4E5Y20jHp/bUQs1/FQaiSlto7jJuAc3OTotNJAGjB/bSPvVFsb zV0d9cty+SHGuiUNLl5vd/5t7bbCnRr1dR0joda/FdUed/Db0g1MGZ/Ox1eWe57SNjlF W7f2aGXNxNJriWhPMj66+M8r3N3e585QWMNMk=
Received: by 10.14.28.140 with SMTP id g12mr13150906eea.85.1329954001101; Wed, 22 Feb 2012 15:40:01 -0800 (PST)
Received: from windows8d787f9 ([109.67.208.29]) by mx.google.com with ESMTPS id n52sm108120844eea.5.2012.02.22.15.39.59 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 22 Feb 2012 15:40:00 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-pcn-3-in-1-encoding.all@tools.ietf.org>
Date: Thu, 23 Feb 2012 01:39:35 +0200
Message-ID: <4f457cd0.4c200e0a.1409.2ad9@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0177_01CCF1CC.00BE5DC0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AczxuzunxXMMWgy+R726JyrlFSsFTw==
Content-Language: en-us
Cc: gen-art@ietf.org, 'IETF-Discussion list' <ietf@ietf.org>
Subject: [Gen-art] Gen-ART LC review of draft-ietf-pcn-3-in-1-encoding-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, 22 Feb 2012 23:40:07 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0177_01CCF1CC.00BE5DC0
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-pcn-3-in-1-encoding-08

Reviewer: Roni Even

Review Date:2012-2-23

IETF LC End Date: 2012-2-23

IESG Telechat date:

 

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

 

Major issues:

 

Minor issues:

 

Nits/editorial comments:

 

Section 1 4th paragraph "tunnelling"

 

 


------=_NextPart_000_0177_01CCF1CC.00BE5DC0
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 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@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;}
@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>I am the =
assigned Gen-ART reviewer for this draft. For background on Gen-ART, =
please see the FAQ at &lt;<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-=
pcn-3-in-1-encoding-08<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;2&#8211;23<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;2&#8211;23<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 a </span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Standards =
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"'>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=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Nits/editor=
ial comments:<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"'>Section 1 =
4<sup>th</sup> paragraph &#8220;</span><span =
style=3D'font-family:"Courier =
New"'>tunnelling&#8221;<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><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0177_01CCF1CC.00BE5DC0--


From jmh@joelhalpern.com  Wed Feb 22 20:40:34 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 E05F021E8027; Wed, 22 Feb 2012 20:40:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f9JlJQghXcVg; Wed, 22 Feb 2012 20:40:33 -0800 (PST)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id C30DD21E8013; Wed, 22 Feb 2012 20:40:33 -0800 (PST)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by morbo.tigertech.net (Postfix) with ESMTP id 6A469A3ED4; Wed, 22 Feb 2012 20:40:33 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 416AB1BD9285; Wed, 22 Feb 2012 20:40:31 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [172.17.114.244] (207.47.24.2.static.nextweb.net [207.47.24.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 062691BD8C9D; Wed, 22 Feb 2012 20:40:31 -0800 (PST)
Message-ID: <4F45C340.3@joelhalpern.com>
Date: Wed, 22 Feb 2012 23:40:32 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Tom Taylor <tom.taylor.stds@gmail.com>
References: <4F455597.2060104@gmail.com>
In-Reply-To: <4F455597.2060104@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Anna Charny <anna@mwsm.com>, Georgios Karagiannis <karagian@cs.utwente.nl>, 'Brian Carpenter' <brian@cs.auckland.ac.nz>, Michael Menth <menth@informatik.uni-wuerzburg.de>, pcn <pcn@ietf.org>, David Harrington <ietfdbh@comcast.net>, Gen Art <gen-art@ietf.org>
Subject: Re: [Gen-art] draft-ietf-pcn-sm-edge-behaviour-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, 23 Feb 2012 04:40:35 -0000

Thank you for your responsiveness and effectiveness in resolving these 
issues.
Yours,
Joel

On 2/22/2012 3:52 PM, Tom Taylor wrote:
> I have now posted draft-ietf-pcn-sm-edge-behaviour-09 with similar
> changes to the CL edge behaviour draft. I forgot to mention deletion of
> the following bullet from Section 2:
>
> o the PCN-domain satisfies the conditions specified in [RFC5696];
>
> I apologize to Joel and Brian that I forgot to add them to the
> Acknowledgements section in the CL draft. I'll fix that in AUTH48, if it
> ever comes. I did fix add them in the SM draft.
>
> Tom Taylor
>

From slblake@petri-meat.com  Wed Feb 22 21:28:59 2012
Return-Path: <slblake@petri-meat.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 A206521E803A; Wed, 22 Feb 2012 21:28:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.999
X-Spam-Level: 
X-Spam-Status: No, score=-100.999 tagged_above=-999 required=5 tests=[AWL=1.600, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oSYAaE3wLOld; Wed, 22 Feb 2012 21:28:58 -0800 (PST)
Received: from elom.tchmachines.com (elom.tchmachines.com [208.76.80.198]) by ietfa.amsl.com (Postfix) with ESMTP id 9434121E803B; Wed, 22 Feb 2012 21:28:58 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=petri-meat.com;  h=Received:Subject:From:To:Cc:Date:In-Reply-To:References:Content-Type:X-Mailer:Content-Transfer-Encoding:Message-ID:Mime-Version; b=qkrE9obIEZZ8TVjvWrgGC/SGHeNCFLvHGQnG16V/I7xHjHv7UPOtpCC2Op3sYpkaQyPJRWfCJRThwkW5Kgb6eI3aCOaskLr7ZWa1d2eSDXuj/0Cxvs3nDX/SW/Le4yOg;
Received: from cpe-071-065-237-221.nc.res.rr.com ([71.65.237.221]) by elom.tchmachines.com with esmtpa (Exim 4.69) (envelope-from <slblake@petri-meat.com>) id 1S0REc-00034a-Ja; Thu, 23 Feb 2012 00:28:54 -0500
From: Steven Blake <slblake@petri-meat.com>
To: Tom Taylor <tom.taylor.stds@gmail.com>
Date: Thu, 23 Feb 2012 00:28:54 -0500
In-Reply-To: <4F455597.2060104@gmail.com>
References: <4F455597.2060104@gmail.com>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.0.3 (3.0.3-1.fc15) 
Content-Transfer-Encoding: 7bit
Message-ID: <1329974935.18234.3.camel@tachyon>
Mime-Version: 1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - elom.tchmachines.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - petri-meat.com
X-Mailman-Approved-At: Thu, 23 Feb 2012 04:11:49 -0800
Cc: Anna Charny <anna@mwsm.com>, Georgios Karagiannis <karagian@cs.utwente.nl>, 'Brian Carpenter' <brian@cs.auckland.ac.nz>, Michael Menth <menth@informatik.uni-wuerzburg.de>, pcn <pcn@ietf.org>, David Harrington <ietfdbh@comcast.net>, Gen Art <gen-art@ietf.org>
Subject: Re: [Gen-art] [PCN] draft-ietf-pcn-sm-edge-behaviour-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, 23 Feb 2012 05:29:00 -0000

On Wed, 2012-02-22 at 15:52 -0500, Tom Taylor wrote:

> I have now posted draft-ietf-pcn-sm-edge-behaviour-09 with similar 
> changes to the CL edge behaviour draft. I forgot to mention deletion of 
> the following bullet from Section 2:
> 
>     o the PCN-domain satisfies the conditions specified in [RFC5696];
> 
> I apologize to Joel and Brian that I forgot to add them to the 
> Acknowledgements section in the CL draft. I'll fix that in AUTH48, if it 
> ever comes. I did fix add them in the SM draft.

Thanks Tom!  (for this and CL).

// Steve


From alberto@it.uc3m.es  Thu Feb 23 03:00:14 2012
Return-Path: <alberto@it.uc3m.es>
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 D06AB21F859E for <gen-art@ietfa.amsl.com>; Thu, 23 Feb 2012 03:00:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.149
X-Spam-Level: 
X-Spam-Status: No, score=-5.149 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, MANGLED_NAIL=2.3, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k7PWirz-id+X for <gen-art@ietfa.amsl.com>; Thu, 23 Feb 2012 03:00:13 -0800 (PST)
Received: from smtp01.uc3m.es (smtp01.uc3m.es [163.117.176.131]) by ietfa.amsl.com (Postfix) with ESMTP id CCB4121F85D5 for <gen-art@ietf.org>; Thu, 23 Feb 2012 03:00:12 -0800 (PST)
X-uc3m-safe: yes
Received: from BOMBO (unknown [163.117.139.56]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp01.uc3m.es (Postfix) with ESMTP id DEF64C28D18; Thu, 23 Feb 2012 12:00:10 +0100 (CET)
From: =?UTF-8?Q?Alberto_Garc=C3=ADa?= <alberto@it.uc3m.es>
To: "'Brian E Carpenter'" <brian.e.carpenter@gmail.com>, "'Joel M. Halpern'" <jmh@joelhalpern.com>
References: <4F3D931C.1000101@nostrum.com> <4F400646.60906@joelhalpern.com> <4F404BE9.5070108@gmail.com>
In-Reply-To: <4F404BE9.5070108@gmail.com>
Date: Thu, 23 Feb 2012 12:00:16 +0100
Message-ID: <004901ccf21a$5366cfa0$fa346ee0$@it.uc3m.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Content-language: es
Thread-index: AQE9XQAx7DAG8QtPL+5cnCcWlVEXCwJjBpPAAkgkwxKXQO9cAA==
X-TM-AS-Product-Ver: IMSS-7.0.0.3116-6.8.0.1017-18728.006
X-Mailman-Approved-At: Thu, 23 Feb 2012 04:11:47 -0800
Cc: gen-art@ietf.org, 'Jari Arkko' <jari.arkko@piuha.net>, draft-garcia-shim6-applicability@tools.ietf.org
Subject: Re: [Gen-art] Review: draft-garcia-shim6-applicability-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, 23 Feb 2012 11:00:14 -0000

Hi,
Thanks for your review, Joel, and to Brian for its comments.

First of all, I'm not generating a new version with the changes =
suggested below until Jari requested it, as recommended in the Gen-ART =
faq. Of course, if you prefer reading the -04-candidate-version file, =
let me know.

|  -----Mensaje original-----
|  De: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]
|  Enviado el: domingo, 19 de febrero de 2012 2:10
|  Para: Joel M. Halpern
|  CC: gen-art@ietf.org; Jari Arkko; draft-garcia-shim6-
|  applicability@tools.ietf.org
|  Asunto: Re: [Gen-art] Review: draft-garcia-shim6-applicability-03
| =20
|  Joel,
| =20
|  Writing as an interested party, not a reviewer:
| =20
| =20
|  On 2012-02-19 09:12, Joel M. Halpern 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-garcia-shim6-applicability-03
|  >     Applicability Statement for the Level 3 Multihoming Shim =
Protocol
|  >                                 (Shim6)
|  > Reviewer: Joel M. Halpern
|  > Review Date: 18-Feb-2012
|  > IETF LC End Date: 14-March-2012
|  > IESG Telechat date: N/A
|  >
|  > Summary: This document is almost ready for publication as an
|  > information rfc
|  >
|  > Major issues:
|  >     The third paragraph of the introduction makes assertions about =
PI
|  > based multihoming being "not generally available to end sites due =
to a
|  > strict policy of route aggregation in the DFZ."  As far as I know,
|  > this is simply not the case.  RIRs sell IPv6 PI for reasonable =
fees.
|  > Most operators accept PI advertisements from customers.  And those
|  > advertisements are passed on to other ISP, and accepted.  I would
|  > recommend removal of the first sentence of this paragraph.  =
Instead,
|  > it needs to be noted that PI based multihoming can be done with =
IPv6,
|  > and then point to the scaling concerns.
| =20
|  Yes, the point is that PI doesn't scale to ten million sites, but =
shim6 does.
|  That should be clarified.

I've made the following change, which I hope addresses the concerns =
raised:

OLD ---->
  In IPv6, site multihoming in the style of IPv4 is not generally
   available to end sites due to a strict policy of route aggregation in
   the DFZ.  Site multihoming for sites without provider-independent
   (PI) addresses is achieved by assigning multiple addresses to each
   host, one or more from each provider.  This multihoming approach
   provides no transport-layer stability across re-homing events.
<--- END OLD text

NEW text ---->
Site multihoming in IPv6 can be achieved as in IPv4, thus facing similar =
scalability concerns. However, the large address space of IPv6 enables a =
different solution for site multihoming in IPv6: to assign multiple =
addresses  to each host, one or more from each provider. Deploying site =
multihoming in this way does not impact in the routing system, so such a =
site multihoming strategy may be extended to a large number of sites, =
and may be applied to small sites which would not be eligible for site =
multihoming based on the injection of routes to PI prefixes. A drawback =
of this multihoming approach is that it does not provide transport-layer =
stability across re-homing events.
<--- END NEW text

| =20
|  >
|  >
|  > Moderate Issues:
|  >     I am unable to understand the sentence "Shim6 has no means to
|  > enforce neither host nor network forwarding for a given locator to =
be
|  > used as source address."  I presume that what it is intended to
|  > communicate is simply a fact about shim6.  Please rewrite.

What I wanted to say was:
'When a locator has been selected by a host to be used as source address =
for a Shim6 session, Shim6 has no means to enforce an appropriate path =
for that source address neither in the host nor in the network.'

That is, there is no specific mechanism to do this in Shim6, so the =
solutions to this must be those of IPv6 (some solutions are commented in =
the same paragraph).

| =20
|  It's a fact. In fact, it's a fact that seriously impacts shim6 =
deployability,
|  according to the experience of a student of mine.
|  Getting the appropriate locator pair out of a host, through the =
appropriate
|  edge router and ISP link, and through the firewall at the far end, =
and doing
|  the whole thing again in the reverse direction, is a significant =
configuration
|  challenge.

Yes. Most of the problem is common to IPv6 using multiple addresses. The =
possibility that the reverse path is different to the forward path, and =
the impact in the firewalls is commented in section 7.6 (Shim6 and =
firewalls).

| =20
|     Brian
| =20
|  >
|  >     If I am reading section 7.1.1 on MobileIPv6/Shim6 interaction, =
it
|  > looks like you are describing a scenario in which the mobile node =
uses
|  > multiple HOAs as locators with a correspondent node. =20

Sure:=20
" Two Shim6  entities will exchange their own available HoAs as =
locators. [...]The CoAs are not presented to the Shim6 layer and are not
   included in the local locator set in this case."
|  > I would suggest
|  > that this section would be clearer if the communicating parties =
were
|  > identified.  I suspect that the intended behavioral assumption is =
that
|  > the mobile node will register its CoA multiple times, once with =
each
|  > home address.  But this does not seem to be stated explicitly.
Well, it says=20
" The CoAs are managed by the MIPv6 layer, which binds each HoA to a =
CoA."
To describe the most general case, we assume that they may be many CoAs =
for the MN, and it could bind
HoA1 to CoA3
HoA2 to CoA2
Etc.=20
I can add the following text to the previous sentence: "For example, is =
a single CoA, CoA1, is available for the MN in the foreign link to which =
it is attached, every HoA should have a bind to CoA1."

However, regarding to the clarity... For me it is very clear - and I =
must say I was not the writer of this part of the text, so I'm not =
taking it personally :-)
Besides, just to understand your comment, when you say that 'it be =
clearer if the communicating parties were identified'... to which =
communication parties are you referring?

|  >
|  >
|  > Minor issues:
|  >     In th long comparative paragraph in the introduction, "The =
Shim6
|  > approach is thought to have better scaling properties with respect =
to
|  > the state held in the DFZ than the IPv approach." Could "IPv 4
|  > approach be replaced with "PI approach"?

Sure, changed.

|  >
|  >     In section 7.7 on the interaction with NPT66, I think it would =
be
|  > helped by a bit more discussion of when certain shim6 messages are
|  > exchanged, and which fields are validated.  Specifically, I can not
|  > tell if it is ever possible to get a shim6 ULID-pair option through =
an
|  > NPT66 which is rewriting the one of the addresses prefixes in the
|  > packet.  I suspect not.  If indeed it just won't work, this needs =
to
|  > be stated MUCH more clearly.

Definitely, after reading this part again, it needs to be MUCH more =
clear, as you say. Therefore, I've rewritten almost completely. I have =
gave up from trying to be exhaustive in the possible cases, since there =
are too many cases (R1bis, I2bis, options that may or may not =
appear...). Covering all the cases would be unfeasible, unreadable, and =
also useless. So the section is a warning of the kind of things that may =
appear.
Do you think the new text is ok?

"7.7.  Shim6 and IPv6 NAT

   Address translation techniques such as Network Prefix Translation
   [RFC6296] may be used until workable solutions to avoid renumbering
   or facilitate multihoming are developed [RFC5902].  We now consider
   the impact of IPv6 NATs in Shim6 operation.

   The main purpose of Shim6 is to provide locator agility below
   transport protocols.  To prevent the risk of redirection attacks by
   abusing on the locator exchange facilities provided by Shim6, the
   protocol is built upon the cryptographic properties of CGA and HBA
   addresses.  When a CGA address of a node is used as the local ULID,
   the locators configured in the node can be signed with the private
   key associated to the CGA.  A peer receiving a Shim6 message performs
   a hash of the CGA Parameter Data Structure information received,
   including a public key, to assure that this key is bound to the CGA
   address, and then checks the signature protecting the locators.  When
   an HBA address of a node is used as the local ULID, the HBA address
   securely chains the ULID and other locators of the node by means of a
   hash.  For both the CGA and the HBA, the locators can be exchanged at
   the four-way handshake used to establish the Shim6 context, or once
   the context has been established by means of an Update Request
   message.

   When a node behind an IPv6 NAT communicates, the NAT device
   translates the address assigned to this internal node to an address
   of its address pool.  This operation results in a mismatch between
   the address seen by external hosts and the address configured in the
   internal node, which is the locator that would be conveyed in a Shim6
   locator exchange and is also the address for which the security
   defined in the CGA and HBA specifications are provided.  Then, the
   validation processes performed by an external node may prevent the
   creation of the Shim6 context, or may allow the context to be created
   but render the alternative locator of the internal host unusable.

   However, note that the failure in creating a Shim6 context, or in
   using the alternative locators, does not impact in the communication
   between the nodes as long as the path between them defined by the
   initial locator pair remains available.  Data packets flow between
   the communicating nodes as for any non-Shim6 communication.  Not
   creating the Shim6 context or not being able to convey the local
   locators to the peer node affect to the added value provided by
   Shim6, i.e. to the ability of preserving the communication in case
   any of the locators fail.  Therefore, using Shim6 with IPv6 NAT does
   not provide less functionality than using IPv6 in the same scenario.

   We now illustrate some cases that may occur when combining Shim6 and
   IPv6 NAT.  The following discussion does not aim to be exhaustive in
   the cases that may arise, but just aims to provide some examples of
   possible situations.  We assume a scenario in which host A is located
   behind a NAT for its locator IP_A1, but it is connected to the public
   IPv6 internet for its locator IP_A2.  Once translated, locator IP_A1
   appears to external nodes as IP_T. Node A communicates with node B,
   with public addresses IP_B1 and IP_B2.


                 +-----+
                 |  A  |
                 +-----+
            IP_A1 |  | IP_A2
                  |  |
                  |  +-----+
                  |        |
               +------+    |
               | NAT  |    |
               +------+    |
             IP_T |        |
                  |        |
         +--------------------------+
         |         Internet         |
         +--------------------------+
                   |  |
             IP_B1 |  | IP_B2
                 +-----+
                 |  B  |
                 +-----+

                                 Figure 4

   We first discuss some issues related with the four-way handshake used
   to establish the Shim6 context.  When the locator information is
   included in the Shim6 exchange, either in the I2 or R2 messages, the
   receiver is required to validate the ULID of the peer node by
   performing the CGA or HBA address validation procedure.  In case the
   validation fails, the message containing the information is silently
   discarded.  In the scenario depicted in Figure 4, some of the cases
   which may occur are:
   o  Node A initiates the exchange, with IP_B1 as destination address
      and IP_A1 as source address, which is a CGA.  Node A includes
      IP_A2 as an alternative locator in the I2 message.  Node B sees
      IP_T as the ULID for A, so when it validates the CGA with the
      information contained in I2, the validation fails because the CGA
      Parameter Data Structure contains information bound to IP_A1.
      Therefore, B silently discards the received I2 message.  Without
      receiving a valid I2 message, B does not create the Shim6 context.
      Without receiving the R2 message, A does not create either the
      Shim6 context.  However, data communication can proceed as long as
      the path between IP_A1 and IP_B1 is valid.  A similar case occur
      if IP_A1 and IP_A2 form a HBA, instead of using CGAs for securing
      the communication.
   o  Node A initiates the exchange with IP_B1 as destination address
      and IP_A2, its public address, as source address, which is a CGA.
      Node A includes IP_A1 as an alternative locator in the I2 message.
      In this case, B can successfully validate IP_A2 as a CGA.
      Regarding to the validation of IP_A1 as an alternative locator for
      A, the Shim6 specification [RFC5533] indicates that it should
      perform this check when the I2 message is received, but it may
      perform it later on, provided that the check is performed before
      using it as a locator.  In case the validation is performed when
      I2 is received, the I2 message would be silently discarded, with
      the same result as for the previous case.  In case the validation
      is performed later, the Shim6 context would be established in both
      nodes A and B, but B could not send to IP_A1, and packets sent by
      A from IP_A1 will not be received by B. Note that in this case
      both IP_B1 and IP_B2 could be used by A and B, as long as the
      locator for A is IP_A2, so limited locator agility may be
      achieved.
   o  Node B initiates the exchange with IP_B1 as source address, and
      IP_A2 as destination address, which is a CGA.  This case is
      similar to the previous one, although it is the R2 message sent by
      A the one that cannot be validated.  While A can create a context
      with B, B cannot do the same for A. Data communication using IP_B1
      and IP_A2 can proceed.  However, A may try to use IP_B2 as
      alternative locator but the data packets sent, carrying the Shim6
      Extension Header, will not be associated by B to any established
      context, so they will be discarded.  The same occurs for packets
      sent by A with IP_A1 as source address.

   We can also consider the case in which node A do not exchange its own
   locators in the Shim6 establishment exchange.  For example, a Shim6
   context can be established between CGA IP_A2, and IP_B1.  B can
   convey locator IP_B2 in the four-way handshake without, and
   validation will be correctly done by A. Later on, A may send an
   Update Request message to inform B about its locator IP_A1.
   Validation for this message will fail in B, and B will send a Shim6
   Error message to A. Neither A nor B will use IP_A1 as locator.
   However, in IP_A2, IP_B1 and IP_B2 can still be used as valid
   locators for the communication.

   Finally, note that an Application Level Gateway designed to modify
   the Shim6 control packets would not be able to generate a valid
   signature, in case a CGA is being used, or a Parameter Data Structure
   binding the translated locator to the other locators of a node, in
   case a HBA is being used.  Therefore, the same failure cases
   described before would remain."


|  >
|  > Yours,
|  > Joel M. Halpern
|  >
|  >
|  > Nits/editorial comments:

Don't know if you have any comment here, or this is just part of the =
template

Regards,
Alberto

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


From brian.e.carpenter@gmail.com  Thu Feb 23 11:48:40 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 D511B21F8888; Thu, 23 Feb 2012 11:48:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.506
X-Spam-Level: 
X-Spam-Status: No, score=-103.506 tagged_above=-999 required=5 tests=[AWL=0.093, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XOo3LNRE2qt5; Thu, 23 Feb 2012 11:48:39 -0800 (PST)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1594A21F8872; Thu, 23 Feb 2012 11:48:38 -0800 (PST)
Received: by eaal12 with SMTP id l12so661252eaa.31 for <multiple recipients>; Thu, 23 Feb 2012 11:48:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=ZjmEpiS3ntA5U5CLG+hIPYMW8ULzNp7Wj+X0uMlvG+s=; b=sSUvL0eVL0kxJQIWxzD4yy1sH4uKL6PgucTgsCBmc2bXegEBwn7BChgFKiBZQU38Gl WmQfs2RHget0n/dBFXKxUQhwQjKHbDOQtc5U8kFttLg6dTbQHCgk6NBnl8LM0FGGMN1S Vd9icT1sOg07XDhMWjAVN9Kc5itOxVnWve/Oc=
Received: by 10.14.48.8 with SMTP id u8mr1333619eeb.37.1330026518144; Thu, 23 Feb 2012 11:48:38 -0800 (PST)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id u9sm8750164eem.11.2012.02.23.11.48.31 (version=SSLv3 cipher=OTHER); Thu, 23 Feb 2012 11:48:37 -0800 (PST)
Message-ID: <4F469809.50206@gmail.com>
Date: Fri, 24 Feb 2012 08:48:25 +1300
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: Tom Taylor <tom.taylor.stds@gmail.com>
References: <4F454808.7000106@gmail.com>
In-Reply-To: <4F454808.7000106@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Anna Charny <anna@mwsm.com>, Michael Menth <menth@informatik.uni-wuerzburg.de>, Fortune Huang <fqhuang@huawei.com>, 'Brian Carpenter' <brian@cs.auckland.ac.nz>, Georgios Karagiannis <karagian@cs.utwente.nl>, pcn <pcn@ietf.org>, David Harrington <ietfdbh@comcast.net>, gen-art@ietf.org
Subject: Re: [Gen-art] draft-ietf-pcn-cl-edge-behaviour-12.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, 23 Feb 2012 19:48:40 -0000

Thanks! That seems to fix my comments.

Regards
   Brian Carpenter

On 2012-02-23 08:54, Tom Taylor wrote:
> I have just submitted draft-ietf-pcn-cl-edge-behaviour-12.txt,
> incorporating responses to the Genart reviews by Joel Halpern and Brian
> Carpenter. Thanks to both of them for their suggestions. The set of
> changes to the CL edge behaviour draft is as follows:
> 
> 1. Introduction
> ===============
> 
> Added the following paragraph in response to a concern expressed by
> Brian. Further related text is described later.
> 
>    Note that the terms "block" or "terminate" actually translate to
>    one or more of several possible courses of action, as discussed
>    in Section 3.6 of RFC5559. The choice of which action to take
>    for blocked or terminated flows is a matter of local policy.
> 
> Deleted the following text from the RFC Editor's note, on Brian's
> recommendation:
> 
>    You may choose to delete the following paragraph and the
>    "[CL-specific]" tags throughout this document when publishing
>    it, since they are present primarily to aid reviewers.
> 
> 3. Node Behaviours
> ==================
> 
> Added the following paragraph at the end of the introductory text to
> this section:
> 
>    Section 5.1.2 describes how to derive the filters by means of
>    which PCN-ingress-nodes and PCN-egress-nodes are able to classify
>    incoming packets into ingress-egress-aggregates.
> 
> 3.3.3. Decision Point Action For Missing PCN-Boundary-Node Reports
> ==================================================================
> 
> Changed the paragraph dealing with egress node reporting timeouts:
> 
> OLD
> 
>    If timer t-recvFail expires for a given PCN-egress-node, the
>    Decision Point SHOULD notify management. A Decision Point
>    collocated with a PCN-ingress-node SHOULD cease to admit
>    PCN-flows to the ingress-egress-aggregate associated with the
>    given PCN-egress-node, until it again receives a report from
>    that node. A centralized Decision Point MAY cease to admit
>    PCN-flows to all ingress-egress-aggregates destined to the
>    PCN-egress-node concerned, until it again receives a report
>    from that node.
> 
> NEW
> 
>    If timer t-recvFail expires for a given PCN-egress-node, the
>    Decision Point SHOULD notify management. A log format is
>    defined for that purpose in Section 5.2.1.1. Other actions
>    depend on local policy, but MAY include blocking of new flows
>    destined for the PCN-egress-node concerned until another report
>    is received from it. Termination of already-admitted flows is
>    also possible, but could be triggered by the receipt of
>    "Destination unreachable" messages at the PCN-ingress-node.
> 
> 5.1.2. Specification of Node- and Link-Specific Parameters
> ==========================================================
> 
> Replaced the first three paragraphs of this section:
> 
> OLD
> 
>    Each PCN-ingress-node needs filters to classify incoming PCN packets
>    according to ingress-egress-aggregate, both to satisfy Decision Point
>    requests for sent traffic rates and, if applicable, to support
>    encapsulation.  If PCN packets are being tunneled to the PCN-egress-
>    nodes (encapsulation), the PCN-ingress-node also needs the address of
>    the PCN-egress-node for each ingress-egress-aggregate.
> 
>    Each PCN-egress-node needs filters to classify incoming PCN packets
>    by ingress-egress-aggregate, in order to gather measurements on a
>    per-aggregate basis.  The PCN-egress-node also needs to know the
>    address of the Decision Point to which it sends reports for each
>    ingress-egress-aggregate.
> 
>    If [I-D.tsvwg-rsvp-pcn] is deployed and the Decision Points are
>    collocated with the PCN-ingress-nodes, this information can be built
>    up dynamically from the contents of the end-to-end RSVP signalling
>    and does not have to be pre-configured.  Otherwise the filters have
>    to be derived from the routing tables in use in the domain, and the
>    address of the peer at the other end of each ingress-egress-aggregate
>    has to be tabulated for each PCN-edge-node.
> 
> NEW
> 
>    Filters are required at both the PCN-ingress-node and the PCN-egress-
>    node to classify incoming PCN packets by ingress-egress-aggregate.
>    Because of the potential use of multi-path routing in domains
>    upstream of the PCN-domain, it is impossible to do such
>    classification reliably at the PCN-egress-node based on the packet
>    header contents as originally received at the PCN-ingress-node.
>    (Packets with the same header contents could enter the PCN-domain at
>    multiple PCN-ingress-nodes.)  As a result, the only way to construct
>    such filters reliably is to tunnel the packets from the PCN-ingress-
>    node to the PCN-egress-node.
> 
>    The PCN-ingress-node needs filters in order to place PCN packets into
>    the right tunnel in the first instance, and also to satisfy requests
>    from the Decision Point for admission rates into specific ingress-
>    egress-aggregates.  These filters select the PCN-egress-node, but not
>    necessarily a specific path through the network to that node.  As a
>    result, they are likely to be stable even in the face of failures in
>    the network, except when the PCN-egress-node itself becomes
>    unreachable.  The primary basis for their derivation will be routing
>    policy given the packet's original origin and destination.  Since all
>    PCN packets will be tunneled, the PCN-ingress-node also needs to know
>    the address of the peer PCN-egress-node associated with each filter.
> 
>    Operators may wish to give some thought to the provisioning of
>    alternate egress points for some or all ingress-egress aggregates in
>    case of failure of the PCN-egress-node.  This could require the
>    setting up of standby tunnels to these alternate egress points.
> 
>    Each PCN-egress-node needs filters to classify incoming PCN packets
>    by ingress-egress-aggregate, in order to gather measurements on a
>    per-aggregate basis.  These filters are constructed on the basis of
>    the identifier of the tunnel from which the incoming packet has
>    emerged (e.g. the source address in the outer header if IP
>    encapsulation is used).  The PCN-egress-node also needs to know the
>    address of the Decision Point to which it sends reports for each
>    ingress-egress-aggregate.
> 
> 5.2.1.  Event Logging In the PCN Domain
> =======================================
> 
> Added the following paragraph:
> 
>    The field names (e.g., HOSTNAME, STRUCTURED-DATA) used in the
>    following subsections are defined in [RFC5424].   
>            
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art
> 

From mahoney@nostrum.com  Thu Feb 23 14:50:38 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 87D1921F8750 for <gen-art@ietfa.amsl.com>; Thu, 23 Feb 2012 14:50:38 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pPx3iY-0ejkZ for <gen-art@ietfa.amsl.com>; Thu, 23 Feb 2012 14:50:37 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 2BB8C21F861F for <gen-art@ietf.org>; Thu, 23 Feb 2012 14:50:11 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-71-170-125-181.dllstx.fios.verizon.net [71.170.125.181]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q1NMoABh060511 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 23 Feb 2012 16:50:10 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <4F46C2A2.2050901@nostrum.com>
Date: Thu, 23 Feb 2012 16:50:10 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.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: 71.170.125.181 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2012-02-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: Thu, 23 Feb 2012 22:50:38 -0000

Hi all,

Here's the link to the new LC assignments:
http://wiki.tools.ietf.org/dav/genart/reviewers-120223-lc.html

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


And 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 mahoney@nostrum.com  Thu Feb 23 14:53:22 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 D96BA21F8839 for <gen-art@ietfa.amsl.com>; Thu, 23 Feb 2012 14:53:21 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9p+EnX4BWIBh for <gen-art@ietfa.amsl.com>; Thu, 23 Feb 2012 14:53:21 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id CA00621F87C5 for <gen-art@ietf.org>; Thu, 23 Feb 2012 14:53:20 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-71-170-125-181.dllstx.fios.verizon.net [71.170.125.181]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q1NMrKnv060876 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 23 Feb 2012 16:53:20 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <4F46C360.4000102@nostrum.com>
Date: Thu, 23 Feb 2012 16:53:20 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.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: 71.170.125.181 is authenticated by a trusted mechanism)
Subject: [Gen-art] Assignments for the 2012-03-01 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, 23 Feb 2012 22:53:22 -0000

Hi all,

Assignments for the telechat can be found here:
http://wiki.tools.ietf.org/dav/genart/reviewers-120301-telechat.html

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

I've also updated the review tool:
http://art.tools.ietf.org/tools/art/genart/

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 Feb 23 17:27:05 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 CD9C621E8026 for <gen-art@ietfa.amsl.com>; Thu, 23 Feb 2012 17:27:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.253
X-Spam-Level: 
X-Spam-Status: No, score=-102.253 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bSHvc5ci9x5h for <gen-art@ietfa.amsl.com>; Thu, 23 Feb 2012 17:27:05 -0800 (PST)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 70DE921E8018 for <gen-art@ietf.org>; Thu, 23 Feb 2012 17:27:05 -0800 (PST)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by morbo.tigertech.net (Postfix) with ESMTP id 5A519103F13 for <gen-art@ietf.org>; Thu, 23 Feb 2012 17:27:05 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 3E78F322332; Thu, 23 Feb 2012 17:27:05 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [172.17.114.244] (207.47.24.2.static.nextweb.net [207.47.24.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 18D74322330; Thu, 23 Feb 2012 17:27:05 -0800 (PST)
Message-ID: <4F46E769.1030401@joelhalpern.com>
Date: Thu, 23 Feb 2012 20:27:05 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>
References: <4F46C2A2.2050901@nostrum.com>
In-Reply-To: <4F46C2A2.2050901@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>, gen-art@ietf.org, draft-ietf-ipfix-rfc5815bis@tools.ietf.org, Quittek@neclab.eu
Subject: [Gen-art]  Review: draft-ietf-ipfix-rfc5815bis-01.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, 24 Feb 2012 01:27:05 -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-ipfix-rfc5815bis-01.txt
     Definitions of Managed Objects for IP Flow Information Export
Reviewer: Joel M. Halpern
Review Date: 23-Feb-2012
IETF LC End Date: 8-March-2012
IESG Telechat date: 15-March-2012

Summary: This document is nearly ready for publication as a Proposed 
Standard.  While each individual item below is minor, the collection is 
sufficiently confusing that I would like to see them resolved before 
publication.

Major issues:

Minor issues:
     The description in the first paragraph of 5.2 on the Template table 
is written in such a way as to lead the reader to think the Observation 
Domain is somehow associated with the Transport Session (which table 
provides the device mode which is discussed in that text.)  Could you 
split the Observation Domain reference out to a separate sentence 
(possibly before the reference to the Transport Session)?

     In the example of the export table in section 5.4, there are two 
blocks of export entries, on with ipfixExportIndex 7, and one with 8. 
They are mirrors of each other except that they reverse which transport 
session is primary, and which is secondary.  There is no explanation of 
why both are present.  And there is no explanation of why the settings 
in index 7 are used, rather than those in index 8.

     If you define an Observation Point with 0 for both Physical Entity 
and Physical Interface, what is it observing?  Similarly, what is a 
metering process metering if its Observation Point Group Ref is 0?

From miguel.a.garcia@ericsson.com  Fri Feb 24 02:02:56 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 76A1C21F88FA for <gen-art@ietfa.amsl.com>; Fri, 24 Feb 2012 02:02:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.3
X-Spam-Level: 
X-Spam-Status: No, score=-10.3 tagged_above=-999 required=5 tests=[AWL=0.299,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eyLILDzSCSDT for <gen-art@ietfa.amsl.com>; Fri, 24 Feb 2012 02:02:55 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id 473BC21F8902 for <gen-art@ietf.org>; Fri, 24 Feb 2012 02:02:55 -0800 (PST)
X-AuditID: c1b4fb39-b7bf2ae0000069a1-ba-4f47604e5ed3
Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 9E.AF.27041.E40674F4; Fri, 24 Feb 2012 11:02:54 +0100 (CET)
Received: from [159.107.51.96] (153.88.115.8) by esessmw0191.eemea.ericsson.se (153.88.115.85) with Microsoft SMTP Server id 8.3.213.0; Fri, 24 Feb 2012 11:02:53 +0100
Message-ID: <4F47604C.70306@ericsson.com>
Date: Fri, 24 Feb 2012 11:02:52 +0100
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: edward.beili@actelis.com, moti.morgenstern@ecitele.com,  Menachem.Dodge@ecitele.com, Dan Romascanu <dromasca@avaya.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Cc: General Area Review Team <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-adslmib-gbond-mib-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: Fri, 24 Feb 2012 10:02:56 -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-adslmib-gbond-mib-09.txt
Reviewer: Miguel Garcia <miguel.a.garcia@ericsson.com>
Review Date: 2012-02-24
IETF LC End Date: 2012-02-28

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

Major issues: none

Minor issues: none

Nits/editorial comments:

- I have not reviewed Section 6 of this document, which is the actual MIB 
structure, because there is nothing I can comment on it. Considering that 
this draft has been produced in the ADSLMIB working group, I believe the 
expertise lies in the WG.

- I've noticed in the data tracker that IANA has requested a 
clarification with respect to the IANA Considerations section. The 
resolution of this discussion should be documented in the IANA 
Considerations section.

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

From vkg@bell-labs.com  Fri Feb 24 12:44:34 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 C640321F84C3 for <gen-art@ietfa.amsl.com>; Fri, 24 Feb 2012 12:44:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.901
X-Spam-Level: 
X-Spam-Status: No, score=-106.901 tagged_above=-999 required=5 tests=[AWL=-0.302, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ORLgz7Om8LEu for <gen-art@ietfa.amsl.com>; Fri, 24 Feb 2012 12:44:33 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 8F6A021F84C4 for <gen-art@ietf.org>; Fri, 24 Feb 2012 12:44:28 -0800 (PST)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id q1OKiQjK004326 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 24 Feb 2012 14:44:26 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q1OKiPSE011238 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 24 Feb 2012 14:44:25 -0600
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.238.235]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q1OKiPi0011853; Fri, 24 Feb 2012 14:44:25 -0600 (CST)
Message-ID: <4F47F7B4.4080407@bell-labs.com>
Date: Fri, 24 Feb 2012 14:48:52 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0) Gecko/20120131 Thunderbird/10.0
MIME-Version: 1.0
To: draft-shin-augmented-pake@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.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Cc: General Area Review Team <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-shin-augmented-pake-12
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, 24 Feb 2012 20:44:34 -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-shin-augmented-pake-12
Reviewer: Vijay K. Gurbani
Review Date: Feb-24-2012
IETF LC End Date: Not known
IESG Telechat date: March-15-2012

Summary: This draft is ready as an Experimental.

Some minor comments and nits follow.

Major issues: 0
Minor issues: 3
Nits/editorial comments: 2

Minor:

1. Section 1 (S1), first paragraph:
  s/session key would be used/session key is used/

2. S1, second paragraph: "...The AugPAKE protocol described in
  this document is an augmented PAKE which also achieves measurable
  efficiency over some previous works."

  For sake of completeness, it may help to provide references to
  the "previous works".

3. S1, second paragraph: "We believe the followings [SKI10]:" ---
  s/followings/following/
  but besides this, I am not sure what you are trying to say
  here.  Maybe a matter of expressing it in alternate English?

Nits:

1. S1, second paragraph: s/one and 1.17/1 and 1.17/
  This makes it congruent with "2 and 2.17" that appears a
  few lines above.

2. Email for author Kazukuni Kobara is missing.

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 mary.ietf.barnes@gmail.com  Fri Feb 24 13:42:51 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 851AA21F86D9 for <gen-art@ietfa.amsl.com>; Fri, 24 Feb 2012 13:42:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.476
X-Spam-Level: 
X-Spam-Status: No, score=-102.476 tagged_above=-999 required=5 tests=[AWL=-1.178, BAYES_00=-2.599, HTML_MESSAGE=0.001, MANGLED_LIST=2.3, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H0BEy+kyIqZm for <gen-art@ietfa.amsl.com>; Fri, 24 Feb 2012 13:42:50 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9C50F21F865F for <gen-art@ietf.org>; Fri, 24 Feb 2012 13:42:50 -0800 (PST)
Received: by vcbfk14 with SMTP id fk14so2156698vcb.31 for <gen-art@ietf.org>; Fri, 24 Feb 2012 13:42:50 -0800 (PST)
Received-SPF: pass (google.com: domain of mary.ietf.barnes@gmail.com designates 10.52.29.40 as permitted sender) client-ip=10.52.29.40; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of mary.ietf.barnes@gmail.com designates 10.52.29.40 as permitted sender) smtp.mail=mary.ietf.barnes@gmail.com; dkim=pass header.i=mary.ietf.barnes@gmail.com
Received: from mr.google.com ([10.52.29.40]) by 10.52.29.40 with SMTP id g8mr2275501vdh.38.1330119770219 (num_hops = 1); Fri, 24 Feb 2012 13:42:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=zaphI5YU37/bGM5p0u+sCy9NZcyXAO6Aoyg0lofjHw8=; b=QndvE9jOXVBFq46CFTblsLjTInr1SRb5OvjqLdOY2YYRblPQVJm6Ep+avt0WO1GIVA yKnHDySedP490lc8IhILyg8310AQmnWo8S9w+0q2/1MbI8KIqOZ7o8Maxr+bO/Ie5pm7 l+uN1f+XUm9EQehnWdiTRIXTiwgG5z9m/ESyQ=
MIME-Version: 1.0
Received: by 10.52.29.40 with SMTP id g8mr1802111vdh.38.1330119770163; Fri, 24 Feb 2012 13:42:50 -0800 (PST)
Received: by 10.52.114.200 with HTTP; Fri, 24 Feb 2012 13:42:50 -0800 (PST)
Date: Fri, 24 Feb 2012 15:42:50 -0600
Message-ID: <CAHBDyN7azfTJnNa3uuTHSrss49q2TdosRAu3xw8baBHdfjHW7Q@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: draft-ietf-netext-pmip-lr.all@tools.ietf.org
Content-Type: multipart/alternative; boundary=20cf307ca41868c88804b9bca460
Cc: gen-art@ietf.org
Subject: [Gen-art] Gen-ART review:draft-ietf-netext-pmip-lr-08.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, 24 Feb 2012 21:42:51 -0000

--20cf307ca41868c88804b9bca460
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

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-netext-pmip-lr-08.txt
Reviewer:  Mary Barnes
Review Date:  24 Feb 2012
IETF LC End Date: 21 Feb 2012
IESG Telechat Date: 01 March 2012

Summary:  Almost ready.

Minor issues:

1) General: There is an inconsistent usage and lack of normative language
in parts of the document.  The following summarizes the majority of the
cases that I encountered:
- Section 4:
-- Text after Figure 2 (before section 4.1).  There is no normative
language in these paragraphs.
--- For example in the first paragraph, I would expect that the elements
that ought to be included in the messages should be specified as "MUST
contain=85". And, rather than "The LMA sends=85", I would think it would be
"The LMA MUST send=85"
--- 2nd paragraph: I would expect to see "=85MUST send an LRA with status
code=85" , "MUST then create Localized Routing Entries=85" .  There's also =
a
"should contain" that I think ought to be "SHOULD contain"
--- 5th paragraph:  First sentence:
"and responds with.."  -> "MUST respond with"
and it seems that there is some other normative language that could be
added throughout that paragraph.

- Section 4.1:
-- 1st para, 1st sentence:  "needs to be" -> "MUST be"

- Section 5:
-- Paragraph after Figure 3.  Similar comments as above.  There's only one
normative statement in that paragraph.
-- Section 5.1:  "needs to be" ->  "MUST be", "It will hence initiate" ->
 "It MUST initiate LR.

- Section 6:
-- First paragraph after Figure 5:  "routing has to be initialized" ->
"routing MUST be initialized"
-- 2nd paragraph:  It would seem that somewhere it should be stated that
the Status value MUST be set to zero.  Also, I don't the the last MUST in
that paragraph is normative.  I would think it could be a "can" and maybe
the "it can provide" is where the MUST should be.

- Section 6.1:
-- "needs to be" -> "MUST be"

- Section 7:
-- last sentence: should the recommended be upper case?

- Section 8: shouldn't  the "must add the IPv4 HOAs" be a "MUST"

- Section 9.1: "The LMA sends.." -> "The LMA MUST send", "The MAG may=85" -=
>
"The MAG MAY=85"

- Section 9.2: "The MAG sends=85" -> "The MAG MUST send", "An LMA may send"
-> "An LMA MAY send"

- Section 11:  "using IPSEC is required" -> "using IPSEC is REQUIRED"



2) Section 4: last sentence of paragraph after Figure 1.   The use of the
EnableMAGLocalRouting flag seems key to whether this functionality is
applied in some of the cases. It's first introduced as a "Please note",
although, it is clearly (but not normatively) specified in the 2nd
paragraph after Figure 2.

I would think it would be helpful to introduce this functionality in
section 2, specifically in Section 2.1 by adding something like the
following after the first sentence of that paragraph:
  The MAG MUST set the EnableMAGLocalRouting to a value of 1.

3) IANA Considerations: My understanding is that IANA wants a list of the
necessary registrations in the same form as they would appear in the
registries (per RFC 5226)  - i.e., something like:

Value      Description                                      Reference
-----          -----------
 -----------------
TBD1       Localized Routing Initiation             [RFCXXXX]
TBD2       Localized Routing Acknowledgment [RFCXXXX]

--20cf307ca41868c88804b9bca460
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div>I am the assigned Gen-ART reviewer for this draft. For background on G=
en-ART, please see the FAQ at &lt;<a href=3D"http://wiki.tools.ietf.org/are=
a/gen/trac/wiki/GenArtfaq">http://wiki.tools.ietf.org/area/gen/trac/wiki/Ge=
nArtfaq</a>&gt;.</div>
<div><br></div><div>Document: draft-ietf-netext-pmip-lr-08.txt</div><div>Re=
viewer: =A0Mary Barnes=A0</div><div>Review Date: =A024 Feb 2012</div><div>I=
ETF LC End Date: 21 Feb 2012</div><div>IESG Telechat Date: 01 March 2012</d=
iv>
<div><br></div><div>Summary: =A0Almost ready.</div><div><br></div><div>Mino=
r issues:=A0</div><div><br></div><div>1) General: There is an inconsistent =
usage and lack of normative language in parts of the document. =A0The follo=
wing summarizes the majority of the cases that I encountered:</div>
<div>- Section 4:=A0</div><div>-- Text after Figure 2 (before section 4.1).=
 =A0There is no normative language in these paragraphs. =A0</div><div>--- F=
or example in the first paragraph, I would expect that the elements that ou=
ght to be included in the messages should be specified as &quot;MUST contai=
n=85&quot;. And, rather than &quot;The LMA sends=85&quot;, I would think it=
 would be &quot;The LMA MUST send=85&quot;</div>
<div>--- 2nd paragraph: I would expect to see &quot;=85MUST send an LRA wit=
h status code=85&quot; , &quot;MUST then create Localized Routing Entries=
=85&quot; . =A0There&#39;s also a &quot;should contain&quot; that I think o=
ught to be &quot;SHOULD contain&quot;</div>
<div>--- 5th paragraph: =A0First sentence:</div><div>&quot;and responds wit=
h..&quot; =A0-&gt; &quot;MUST respond with&quot;=A0</div><div>and it seems =
that there is some other normative language that could be added throughout =
that paragraph.=A0</div>
<div><br></div><div>- Section 4.1: =A0</div><div>-- 1st para, 1st sentence:=
 =A0&quot;needs to be&quot; -&gt; &quot;MUST be&quot;=A0</div><div><br></di=
v><div>- Section 5:=A0</div><div>-- Paragraph after Figure 3. =A0Similar co=
mments as above. =A0There&#39;s only one normative statement in that paragr=
aph.=A0</div>
<div>-- Section 5.1: =A0&quot;needs to be&quot; -&gt; =A0&quot;MUST be&quot=
;, &quot;It will hence initiate&quot; -&gt; =A0&quot;It MUST initiate LR.=
=A0</div><div><br></div><div>- Section 6:=A0</div><div>-- First paragraph a=
fter Figure 5: =A0&quot;routing has to be initialized&quot; -&gt; &quot;rou=
ting MUST be initialized&quot;</div>
<div>-- 2nd paragraph: =A0It would seem that somewhere it should be stated =
that the Status value MUST be set to zero. =A0Also, I don&#39;t the the las=
t MUST in that paragraph is normative. =A0I would think it could be a &quot=
;can&quot; and maybe the &quot;it can provide&quot; is where the MUST shoul=
d be.=A0</div>
<div><br></div><div>- Section 6.1:=A0</div><div>-- &quot;needs to be&quot; =
-&gt; &quot;MUST be&quot;=A0</div><div><br></div><div>- Section 7:</div><di=
v>-- last sentence: should the recommended be upper case?=A0</div><div><br>=
</div>
<div>- Section 8: shouldn&#39;t =A0the &quot;must add the IPv4 HOAs&quot; b=
e a &quot;MUST&quot;</div><div><br></div><div>- Section 9.1: &quot;The LMA =
sends..&quot; -&gt; &quot;The LMA MUST send&quot;, &quot;The MAG may=85&quo=
t; -&gt;=A0</div>
<div>&quot;The MAG MAY=85&quot;</div><div><br></div><div>- Section 9.2: &qu=
ot;The MAG sends=85&quot; -&gt; &quot;The MAG MUST send&quot;, &quot;An LMA=
 may send&quot;=A0</div><div>-&gt; &quot;An LMA MAY send&quot;</div><div><b=
r>
</div><div>- Section 11: =A0&quot;using IPSEC is required&quot; -&gt; &quot=
;using IPSEC is REQUIRED&quot;</div><div><br></div><div><br></div><div><br>=
</div><div>2) Section 4: last sentence of paragraph after Figure 1. =A0 The=
 use of the EnableMAGLocalRouting flag seems key to whether this functional=
ity is applied in some of the cases. It&#39;s first introduced as a &quot;P=
lease note&quot;, although, it is clearly (but not normatively) specified i=
n the 2nd paragraph after Figure 2.=A0</div>
<div><br></div><div>I would think it would be helpful to introduce this fun=
ctionality in section 2, specifically in Section 2.1 by adding something li=
ke the following after the first sentence of that paragraph:</div><div>
=A0 The MAG MUST set the EnableMAGLocalRouting to a value of 1.</div><div><=
br></div><div>3) IANA Considerations: My understanding is that IANA wants a=
 list of the necessary registrations in the same form as they would appear =
in the registries (per RFC 5226) =A0- i.e., something like:</div>
<div><br></div><div>Value =A0 =A0 =A0Description =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Reference</div><div>----=
- =A0 =A0 =A0 =A0 =A0----------- =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0-----------------</div><div>TBD1=
 =A0 =A0 =A0 Localized Routing Initiation =A0 =A0 =A0 =A0 =A0 =A0 [RFCXXXX]=
</div>
<div>TBD2 =A0 =A0 =A0 Localized Routing Acknowledgment [RFCXXXX]</div><div>=
<br></div>

--20cf307ca41868c88804b9bca460--

From Francis.Dupont@fdupont.fr  Sun Feb 26 09:17:17 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 82DBD21F857A for <gen-art@ietfa.amsl.com>; Sun, 26 Feb 2012 09:17:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.585
X-Spam-Level: 
X-Spam-Status: No, score=-2.585 tagged_above=-999 required=5 tests=[AWL=0.014,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V4XhnK0pk884 for <gen-art@ietfa.amsl.com>; Sun, 26 Feb 2012 09:17:16 -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 4FD3D21F856A for <gen-art@ietf.org>; Sun, 26 Feb 2012 09:17:16 -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 q1QHHE0r072883; Sun, 26 Feb 2012 18:17:14 +0100 (CET) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201202261717.q1QHHE0r072883@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: gen-art@ietf.org
Date: Sun, 26 Feb 2012 18:17:14 +0100
Sender: Francis.Dupont@fdupont.fr
Cc: draft-ietf-decade-problem-statement.all@tools.ietf.org
Subject: [Gen-art] review of draft-ietf-decade-problem-statement-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, 26 Feb 2012 17:17:17 -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-decade-problem-statement-05.txt
Reviewer: Francis Dupont
Review Date: 20120224
IETF LC End Date: 20120306
IESG Telechat date: unknown

Summary: Ready

Major issues: None


Minor issues: None

Nits/editorial comments:
 - 1 page 3: P2P and CDN are not in the list of well known abbrevs
  (IMHO for the first one because P2P means Point-to-Point too)
  so should be introduced at the first use in the body (and for CDN
  IMHO as soon as possible, this is why I put this in 1)

 - 1 page 3: in the networks. -> in networks. ?

 - 3.1 page 4: IMHO [Internet Study 2008/2009] should be removed to
  leave only the reference, i.e., [Internet_Study_2008-2009]

 - 4.1 page 7: 'nor can they manage access' is a wording which could
  (so should) be improved a bit, IMHO 'nor access' is enough

 - A pages 11 and 12: e.g. -> e.g., (also at end of line but it is
  in an appendix 'to be removed by the RFC Editor'...)

Regards 

Francis.Dupont@fdupont.fr

PS: my dictionary dislikes 'infrastructural'?

From Francis.Dupont@fdupont.fr  Sun Feb 26 09:28:23 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 3E23321F85D3 for <gen-art@ietfa.amsl.com>; Sun, 26 Feb 2012 09:28:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.587
X-Spam-Level: 
X-Spam-Status: No, score=-2.587 tagged_above=-999 required=5 tests=[AWL=0.012,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0A5PTtLryzLF for <gen-art@ietfa.amsl.com>; Sun, 26 Feb 2012 09:28:22 -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 5FA5F21F85AE for <gen-art@ietf.org>; Sun, 26 Feb 2012 09:28:07 -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 q1QHS4mY073523; Sun, 26 Feb 2012 18:28:04 +0100 (CET) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201202261728.q1QHS4mY073523@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: gen-art@ietf.org
Date: Sun, 26 Feb 2012 18:28:04 +0100
Sender: Francis.Dupont@fdupont.fr
Cc: draft-mcgrew-tls-aes-ccm.all@tools.ietf.org
Subject: [Gen-art] review of draft-mcgrew-tls-aes-ccm-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: Sun, 26 Feb 2012 17:28: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-mcgrew-tls-aes-ccm-03.txt
Reviewer: Francis Dupont
Review Date: 20120224
IETF LC End Date: 20120313
IESG Telechat date: known

Summary: Ready

Major issues: None

Minor issues: None but please check my comment about 8.2

Nits/editorial comments:
 - ToC page 2 and 6.2 page 6: a 8-octet -> an 8-octet

 - ToC page 2 and 9 page 6: Acknowledgements -> Acknowledgments

 - 3 page 4: the wording about authentication tags is a bit strange:
  the first line uses singular and the next plural?

 - 3 page 4: the Nonce layout is not ambiguous for me but it doesn't
  use a common / easy to recognize programming language

 - 8.2 page 6: as the counter reuse is really critical I'd like to
  get a review by a cryptographer of 8.2 and 3.

Regards

Francis.Dupont@fdupont.fr

From christer.holmberg@ericsson.com  Sun Feb 26 11:20:55 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 B805C21F851B for <gen-art@ietfa.amsl.com>; Sun, 26 Feb 2012 11:20:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.159
X-Spam-Level: 
X-Spam-Status: No, score=-10.159 tagged_above=-999 required=5 tests=[AWL=0.439, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mV12NexPWqUi for <gen-art@ietfa.amsl.com>; Sun, 26 Feb 2012 11:20:55 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id EB83221F8510 for <gen-art@ietf.org>; Sun, 26 Feb 2012 11:20:54 -0800 (PST)
X-AuditID: c1b4fb39-b7bf2ae0000069a1-df-4f4a86159a9f
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 33.90.27041.5168A4F4; Sun, 26 Feb 2012 20:20:54 +0100 (CET)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.31]) by esessmw0197.eemea.ericsson.se ([153.88.115.87]) with mapi; Sun, 26 Feb 2012 20:20:53 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: General Area Review Team <gen-art@ietf.org>
Date: Sun, 26 Feb 2012 20:20:52 +0100
Thread-Topic: Gen-ART LC Review of draft-ietf-manet-smf-13
Thread-Index: Acz0u8FNBXvDMMNhQi+cpYJ5eSr8FA==
Message-ID: <7F2072F1E0DE894DA4B517B93C6A05852C3F4BA9FD@ESESSCMS0356.eemea.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_7F2072F1E0DE894DA4B517B93C6A05852C3F4BA9FDESESSCMS0356e_"
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "'draft-ietf-manet-smf.all@tools.ietf.org'" <draft-ietf-manet-smf.all@tools.ietf.org>
Subject: [Gen-art] Gen-ART LC Review of draft-ietf-manet-smf-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: Sun, 26 Feb 2012 19:20:55 -0000

--_000_7F2072F1E0DE894DA4B517B93C6A05852C3F4BA9FDESESSCMS0356e_
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/Gen=
Artfaq>.
Please wait for direction from your document shepherd or AD before posting =
a new version of the draft.
Document: draft-ietf-manet-smf-13
Reviewer: Christer Holmberg
Review Date: 26 February 2012
IETF LC End Date: 27 February 2012
IESG Telechat date: 1 March 2012
Summary: This draft is ready for publication.
Major issues: -
Minor issues: -
Nits/editorial comments: -
Regards,
Christer



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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
 #800000 2px solid; } --></style>
</head>
<body>
<font face=3D"Arial, sans-serif" size=3D"3">
<div>&nbsp;</div>
<div style=3D"margin-top: 5pt; margin-bottom: 5pt; "><font face=3D"Courier =
New" size=3D"2">I am the assigned Gen-ART reviewer for this draft. For back=
ground on Gen-ART, please see the FAQ at &lt;<a href=3D"http://wiki.tools.i=
etf.org/area/gen/trac/wiki/GenArtfaq"><font color=3D"#0000FF"><u>http://wik=
i.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</u></font></a>&gt;.
</font></div>
<div style=3D"margin-top: 5pt; margin-bottom: 5pt; "><font face=3D"Courier =
New" size=3D"2">Please wait for direction from your document shepherd or AD=
 before posting a new version of the draft. </font></div>
<div style=3D"margin-top: 5pt; margin-bottom: 5pt; "><font face=3D"Courier =
New" size=3D"2">Document: draft-ietf-manet-smf-13</font></div>
<div style=3D"margin-top: 5pt; margin-bottom: 5pt; "><font face=3D"Courier =
New" size=3D"2">Reviewer: Christer Holmberg </font></div>
<div style=3D"margin-top: 5pt; margin-bottom: 5pt; "><font face=3D"Courier =
New" size=3D"2">Review Date: 26 February 2012 </font></div>
<div style=3D"margin-top: 5pt; margin-bottom: 5pt; "><font face=3D"Courier =
New" size=3D"2">IETF LC End Date: 27 February 2012 </font></div>
<div style=3D"margin-top: 5pt; margin-bottom: 5pt; "><font face=3D"Courier =
New" size=3D"2">IESG Telechat date: 1 March 2012 </font></div>
<div style=3D"margin-top: 5pt; margin-bottom: 5pt; "><font face=3D"Courier =
New" size=3D"2">Summary: This draft is ready for publication. </font></div>
<div style=3D"margin-top: 5pt; margin-bottom: 5pt; "><font face=3D"Courier =
New" size=3D"2">Major issues: - </font></div>
<div style=3D"margin-top: 5pt; margin-bottom: 5pt; "><font face=3D"Courier =
New" size=3D"2">Minor issues: - </font></div>
<div style=3D"margin-top: 5pt; margin-bottom: 5pt; "><font face=3D"Courier =
New" size=3D"2">Nits/editorial comments: -</font></div>
<div style=3D"margin-top: 5pt; margin-bottom: 5pt; "><font face=3D"Courier =
New" size=3D"2">Regards, </font></div>
<div style=3D"margin-top: 5pt; margin-bottom: 5pt; "><font face=3D"Courier =
New" size=3D"2">Christer</font></div>
<div><font face=3D"Courier New" size=3D"2">&nbsp;</font></div>
<div><font size=3D"2">&nbsp;</font></div>
</font>
</body>
</html>

--_000_7F2072F1E0DE894DA4B517B93C6A05852C3F4BA9FDESESSCMS0356e_--

From christer.holmberg@ericsson.com  Sun Feb 26 11:41:57 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 9639121F84F6 for <gen-art@ietfa.amsl.com>; Sun, 26 Feb 2012 11:41:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.166
X-Spam-Level: 
X-Spam-Status: No, score=-10.166 tagged_above=-999 required=5 tests=[AWL=0.432, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V0vwl7jskFzx for <gen-art@ietfa.amsl.com>; Sun, 26 Feb 2012 11:41:57 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id BA0AF21F84D9 for <gen-art@ietf.org>; Sun, 26 Feb 2012 11:41:56 -0800 (PST)
X-AuditID: c1b4fb39-b7bf2ae0000069a1-bd-4f4a8b0329eb
Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 28.61.27041.30B8A4F4; Sun, 26 Feb 2012 20:41:55 +0100 (CET)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.31]) by esessmw0191.eemea.ericsson.se ([153.88.115.84]) with mapi; Sun, 26 Feb 2012 20:41:55 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: General Area Review Team <gen-art@ietf.org>
Date: Sun, 26 Feb 2012 20:41:54 +0100
Thread-Topic: Gen-ART review of draft-betts-itu-oam-ach-code-point-03
Thread-Index: Acz0vrEzWY2WmyE1TeGh2k1Q8rFHgg==
Message-ID: <7F2072F1E0DE894DA4B517B93C6A05852C3F4BA9FF@ESESSCMS0356.eemea.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_7F2072F1E0DE894DA4B517B93C6A05852C3F4BA9FFESESSCMS0356e_"
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "'draft-betts-itu-oam-ach-code-point.all@tools.ietf.org'" <draft-betts-itu-oam-ach-code-point.all@tools.ietf.org>
Subject: [Gen-art] Gen-ART review of draft-betts-itu-oam-ach-code-point-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: Sun, 26 Feb 2012 19:41:57 -0000

--_000_7F2072F1E0DE894DA4B517B93C6A05852C3F4BA9FFESESSCMS0356e_
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-betts-itu-oam-ach-code-point-03
Reviewer: Christer Holmberg
Review Date: 26 February 2012
IETF LC End Date: 21 March 2013
IESG Telechat date: N/A

Summary: The draft is ready for publication, with a couple of mindor editor=
ial nits.

Major issues: -

Minor issues: -

Nits/editorial comments:

- Section 1: Please expand 'MPLS-TP' and 'MPLS' when first used, and add a =
reference to where MPLS-TP and MPLS are defined.

- Section 1: Please expand ACH when first used.

Regards,

Christer


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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
 #800000 2px solid; } --></style>
</head>
<body>
<font face=3D"Arial, sans-serif" size=3D"3">
<div>&nbsp;</div>
<div><font face=3D"Courier New, monospace" size=3D"2">I am the assigned Gen=
-ART reviewer for this draft. For background on Gen-ART, please see the FAQ=
 at &lt; <a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
"><font color=3D"#0000FF"><u>http://wiki.tools.ietf.org/area/gen/trac/wiki/=
GenArtfaq</u></font></a>&gt;.</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">Please wait for direc=
tion from your document shepherd or AD before posting a new version of the =
draft.</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">Document: draft-betts=
-itu-oam-ach-code-point-03</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">Reviewer: Christer Ho=
lmberg</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">Review Date: 26 Febru=
ary 2012</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">IETF LC End Date: 21 =
March 2013</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">IESG Telechat date: N=
/A</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">Summary: The draft is=
 ready for publication, with a couple of mindor editorial nits.</font></div=
>
<div><font face=3D"Courier New, monospace" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">Major issues: -</font=
></div>
<div><font face=3D"Courier New, monospace" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">Minor issues: -</font=
></div>
<div><font face=3D"Courier New, monospace" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">Nits/editorial commen=
ts:</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">- Section 1: Please e=
xpand 'MPLS-TP' and 'MPLS' when first used, and add a reference to where MP=
LS-TP and MPLS are defined.</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">- Section 1: Please e=
xpand ACH when first used. </font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">Regards,</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Courier New, monospace" size=3D"2">Christer</font></div>
<div><font size=3D"2">&nbsp;</font></div>
</font>
</body>
</html>

--_000_7F2072F1E0DE894DA4B517B93C6A05852C3F4BA9FFESESSCMS0356e_--

From suresh.krishnan@ericsson.com  Mon Feb 27 04:25:05 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 85F1221F86B5 for <gen-art@ietfa.amsl.com>; Mon, 27 Feb 2012 04:25:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.183
X-Spam-Level: 
X-Spam-Status: No, score=-106.183 tagged_above=-999 required=5 tests=[AWL=0.416, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tJdI5qaIcaxJ for <gen-art@ietfa.amsl.com>; Mon, 27 Feb 2012 04:25:05 -0800 (PST)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id D902821F8693 for <gen-art@ietf.org>; Mon, 27 Feb 2012 04:25:04 -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 q1RCP12j007551 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 27 Feb 2012 06:25:02 -0600
Received: from [164.48.125.17] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.178) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 27 Feb 2012 07:25:00 -0500
Message-ID: <4F4B7617.30703@ericsson.com>
Date: Mon, 27 Feb 2012 07:24:55 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Mary Barnes <mary.ietf.barnes@gmail.com>
References: <CAHBDyN7azfTJnNa3uuTHSrss49q2TdosRAu3xw8baBHdfjHW7Q@mail.gmail.com>
In-Reply-To: <CAHBDyN7azfTJnNa3uuTHSrss49q2TdosRAu3xw8baBHdfjHW7Q@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-netext-pmip-lr.all@tools.ietf.org" <draft-ietf-netext-pmip-lr.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review:draft-ietf-netext-pmip-lr-08.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: Mon, 27 Feb 2012 12:25:05 -0000

Hi Mary,
   Thanks for your review and comments. Please find responses inline.

On 02/24/2012 04:42 PM, Mary Barnes wrote:
> - Section 4:
> -- Text after Figure 2 (before section 4.1).  There is no normative
> language in these paragraphs.
> --- For example in the first paragraph, I would expect that the elements
> that ought to be included in the messages should be specified as "MUST
> contain…". And, rather than "The LMA sends…", I would think it would be
> "The LMA MUST send…"
> --- 2nd paragraph: I would expect to see "…MUST send an LRA with status
> code…" , "MUST then create Localized Routing Entries…" .  There's also a
> "should contain" that I think ought to be "SHOULD contain"
> --- 5th paragraph:  First sentence:
> "and responds with.."  -> "MUST respond with"
> and it seems that there is some other normative language that could be
> added throughout that paragraph.
>
> - Section 4.1:
> -- 1st para, 1st sentence: "needs to be" -> "MUST be"
>
> - Section 5:
> -- Paragraph after Figure 3.  Similar comments as above.  There's only
> one normative statement in that paragraph.
> -- Section 5.1: "needs to be" -> "MUST be", "It will hence initiate" ->
> "It MUST initiate LR.
>
> - Section 6:
> -- First paragraph after Figure 5: "routing has to be initialized" ->
> "routing MUST be initialized"
> -- 2nd paragraph:  It would seem that somewhere it should be stated that
> the Status value MUST be set to zero.  Also, I don't the the last MUST
> in that paragraph is normative.  I would think it could be a "can" and
> maybe the "it can provide" is where the MUST should be.
>
> - Section 6.1:
> -- "needs to be" -> "MUST be"
>
> - Section 7:
> -- last sentence: should the recommended be upper case?
>
> - Section 8: shouldn't  the "must add the IPv4 HOAs" be a "MUST"
>
> - Section 9.1: "The LMA sends.." -> "The LMA MUST send", "The MAG may…" ->
> "The MAG MAY…"
>
> - Section 9.2: "The MAG sends…" -> "The MAG MUST send", "An LMA may send"
> -> "An LMA MAY send"
>
> - Section 11: "using IPSEC is required" -> "using IPSEC is REQUIRED"

Will fix these.

>
>
>
> 2) Section 4: last sentence of paragraph after Figure 1.   The use of
> the EnableMAGLocalRouting flag seems key to whether this functionality
> is applied in some of the cases. It's first introduced as a "Please
> note", although, it is clearly (but not normatively) specified in the
> 2nd paragraph after Figure 2.

Right. This is because the flag is not specified in this document. It is 
inherited from the PMIPv6 base specification (RFC5213).

>
> I would think it would be helpful to introduce this functionality in
> section 2, specifically in Section 2.1 by adding something like the
> following after the first sentence of that paragraph:
>    The MAG MUST set the EnableMAGLocalRouting to a value of 1.

This is actually not required. The localized routing will take place 
anyway, if needed. The flag only determines whether the MAG will 
independently initiate localized routing or will it wait for LMA 
instruction to do so. This document only specifies the behavior when the 
flag is set to 0 in the A11 case. The behavior for the flag set to 1 in 
the A11 case is specified in RFC5213.

>
> 3) IANA Considerations: My understanding is that IANA wants a list of
> the necessary registrations in the same form as they would appear in the
> registries (per RFC 5226)  - i.e., something like:
>
> Value      Description                                      Reference
> -----          -----------
>   -----------------
> TBD1       Localized Routing Initiation             [RFCXXXX]
> TBD2       Localized Routing Acknowledgment [RFCXXXX]

Sounds good. I will check with IANA for the format.

Thanks
Suresh


From haibin.song@huawei.com  Sun Feb 26 23:29:55 2012
Return-Path: <haibin.song@huawei.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 DE55E21F851D; Sun, 26 Feb 2012 23:29:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.536
X-Spam-Level: 
X-Spam-Status: No, score=-6.536 tagged_above=-999 required=5 tests=[AWL=0.063,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H-5JCWrTzaIz; Sun, 26 Feb 2012 23:29:55 -0800 (PST)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 29B4C21F8501; Sun, 26 Feb 2012 23:29:55 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0M010001PJHO7K@szxga04-in.huawei.com>; Mon, 27 Feb 2012 15:29:49 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0M01006LPJH6ZG@szxga04-in.huawei.com>; Mon, 27 Feb 2012 15:29:48 +0800 (CST)
Received: from szxeml209-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AHK81527; Mon, 27 Feb 2012 15:29:48 +0800
Received: from SZXEML430-HUB.china.huawei.com (10.72.61.38) by szxeml209-edg.china.huawei.com (172.24.2.184) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 27 Feb 2012 15:29:18 +0800
Received: from SZXEML534-MBX.china.huawei.com ([169.254.2.222]) by szxeml430-hub.china.huawei.com ([10.72.61.38]) with mapi id 14.01.0323.003; Mon, 27 Feb 2012 15:29:41 +0800
Date: Mon, 27 Feb 2012 07:30:11 +0000
From: Songhaibin <haibin.song@huawei.com>
In-reply-to: <201202261717.q1QHHE0r072883@givry.fdupont.fr>
X-Originating-IP: [10.138.41.129]
To: "Francis.Dupont@fdupont.fr" <Francis.Dupont@fdupont.fr>, "gen-art@ietf.org" <gen-art@ietf.org>
Message-id: <E33E01DFD5BEA24B9F3F18671078951F156DCB3E@szxeml534-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-language: zh-CN
Content-transfer-encoding: 7BIT
Accept-Language: en-US, zh-CN
Thread-topic: review of draft-ietf-decade-problem-statement-05.txt
Thread-index: AQHM9KqHGEiLFvsSxkqKVT/NIeFzUJZQWP3w
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: <201202261717.q1QHHE0r072883@givry.fdupont.fr>
X-Mailman-Approved-At: Mon, 27 Feb 2012 04:59:27 -0800
Cc: "decade@ietf.org" <decade@ietf.org>, "draft-ietf-decade-problem-statement.all@tools.ietf.org" <draft-ietf-decade-problem-statement.all@tools.ietf.org>
Subject: Re: [Gen-art] review of draft-ietf-decade-problem-statement-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: Mon, 27 Feb 2012 07:29:56 -0000

Hi Francis,

Thank you very much for the Gen-ART review. The nits will be resolved before publication.

BR,
-Haibin (as individual)

> -----Original Message-----
> From: Francis.Dupont@fdupont.fr [mailto:Francis.Dupont@fdupont.fr]
> Sent: Monday, February 27, 2012 1:17 AM
> To: gen-art@ietf.org
> Cc: draft-ietf-decade-problem-statement.all@tools.ietf.org
> Subject: review of draft-ietf-decade-problem-statement-05.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-decade-problem-statement-05.txt
> Reviewer: Francis Dupont
> Review Date: 20120224
> IETF LC End Date: 20120306
> IESG Telechat date: unknown
> 
> Summary: Ready
> 
> Major issues: None
> 
> 
> Minor issues: None
> 
> Nits/editorial comments:
>  - 1 page 3: P2P and CDN are not in the list of well known abbrevs
>   (IMHO for the first one because P2P means Point-to-Point too)
>   so should be introduced at the first use in the body (and for CDN
>   IMHO as soon as possible, this is why I put this in 1)
> 
>  - 1 page 3: in the networks. -> in networks. ?
> 
>  - 3.1 page 4: IMHO [Internet Study 2008/2009] should be removed to
>   leave only the reference, i.e., [Internet_Study_2008-2009]
> 
>  - 4.1 page 7: 'nor can they manage access' is a wording which could
>   (so should) be improved a bit, IMHO 'nor access' is enough
> 
>  - A pages 11 and 12: e.g. -> e.g., (also at end of line but it is
>   in an appendix 'to be removed by the RFC Editor'...)
> 
> Regards
> 
> Francis.Dupont@fdupont.fr
> 
> PS: my dictionary dislikes 'infrastructural'?

From rbarnes@bbn.com  Mon Feb 27 05:11:01 2012
Return-Path: <rbarnes@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 412D321F8682 for <gen-art@ietfa.amsl.com>; Mon, 27 Feb 2012 05:11:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.516
X-Spam-Level: 
X-Spam-Status: No, score=-106.516 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id myH-T2WFqbgX for <gen-art@ietfa.amsl.com>; Mon, 27 Feb 2012 05:10:45 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfa.amsl.com (Postfix) with ESMTP id 0A40F21F8684 for <gen-art@ietf.org>; Mon, 27 Feb 2012 05:10:44 -0800 (PST)
Received: from [128.89.255.166] (port=57158) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1S20Lf-000EA9-Tm; Mon, 27 Feb 2012 08:10:40 -0500
From: Richard Barnes <rbarnes@bbn.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Mon, 27 Feb 2012 18:40:35 +0530
Message-Id: <199ACCDB-1B9A-4C44-BEB6-BCE9253513CB@bbn.com>
To: gen-art@ietf.org, draft-ietf-pcp-base@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1251.1)
X-Mailer: Apple Mail (2.1251.1)
Subject: [Gen-art] Gen-ART review of draft-ietf-pcp-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: Mon, 27 Feb 2012 13:11: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>.

Document: draft-ietf-pcp-base-23.txt
Reviewer:  Richard Barnes=20
Review Date:  27 Feb 2012
IETF LC End Date: 27 Feb 2012
IESG Telechat Date: 01 March 2012

Summary: Almost ready

Major issues:

-- As I think others have noted during LC, it seems like it would =
simplify several aspects of the protocol if requests and responses could =
be correlated by means of a transaction identifier, instead of just by =
matching fields.  In addition to simplifying response processing and =
clarifying the meaning of lifetime parameters, this would also provide a =
measure of protection against address spoofing.

-- It would be helpful for the document to say a little more about risks =
posed from spoofed packets.  It seems like there are some cases where an =
off-path attacker could break synchronization in state between clients =
and servers, e.g., by sending gratuitous responses.  This is a rather =
serious attack, as it could be used by an off-path attacker to steal =
traffic:
1. Attacker obtains mapping from address:port=3DA:P on PCP controlled =
device to one of its ports B:Q
2. Attacker convinces client that it has a mapping from A:P to its port =
C:R
3. Attacker acts as a man in the middle: remote -> A:P -> B:Q -> C:R
Also, it seems the ANNOUNCE method provides an opportunity for an =
attacker capable of spoofing to cause an arbitrary number clients to =
flood the server with requests.


Minor issues:

-- The document says that v4-mapped addresses are not used as source or =
destination addresses for real IPv6 packets.  This is empirically not =
the case; in some work we have done on IPv6 traceroute scanning, we have =
encountered numerous routers that will respond from v4-mapped addresses. =
 It probably would be accurate to say that these addresses would never =
appear in a mapping.

-- In Section 6.4, the first paragraph says that each error is "long" or =
"short", but they're not all marked.  Is there a default?  It also seems =
like some of these errors are effectively permanent, e.g., =
UNSUPP_VERSION; the PCP NAT isn't going to support a new version of the =
protocol half an hour from now.

-- In Section 7.1, you first say that "only a single PCP server address =
is supported", but then in a couple of other places mention a "list of =
PCP servers".  Which is it?

-- In Section 7.1, it seems like it would be pretty unusual for the PCP =
server to be the first-hop router, at least outside of the CPE case.  =
Would it be better to use an anycast address to find the server?

-- I did not find that the code samples in Section 9 added any =
information.  The one case where one would have been helpful (9.4), =
there was none.=20


From suresh.krishnan@ericsson.com  Mon Feb 27 18:06:59 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 7727621E8042 for <gen-art@ietfa.amsl.com>; Mon, 27 Feb 2012 18:06:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.19
X-Spam-Level: 
X-Spam-Status: No, score=-106.19 tagged_above=-999 required=5 tests=[AWL=0.409, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mH1JAJQ4aTdK for <gen-art@ietfa.amsl.com>; Mon, 27 Feb 2012 18:06:58 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 8B85421E8029 for <gen-art@ietf.org>; Mon, 27 Feb 2012 18:06:58 -0800 (PST)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q1S263xi017145; Mon, 27 Feb 2012 20:06:57 -0600
Received: from [142.133.10.98] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.32) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 27 Feb 2012 21:06:42 -0500
Message-ID: <4F4C36B2.9090809@ericsson.com>
Date: Mon, 27 Feb 2012 21:06:42 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: General Area Review Team <gen-art@ietf.org>, <draft-ietf-l3vpn-mvpn-wildcards.all@tools.ietf.org>
X-Enigmail-Version: 1.3.5
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: [Gen-art] Gen-ART review of draft-ietf-l3vpn-mvpn-wildcards-02.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, 28 Feb 2012 02:06:59 -0000

I am the assigned Gen-ART reviewer for
draft-ietf-l3vpn-mvpn-wildcards-02.txt

For background on Gen-ART, please see the FAQ at
<http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html>.

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

Summary: This draft is ready for publication as a Proposed Standard.

Thanks
Suresh












From wassim.haddad@ericsson.com  Mon Feb 27 22:46:06 2012
Return-Path: <wassim.haddad@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 567FC21F8798 for <gen-art@ietfa.amsl.com>; Mon, 27 Feb 2012 22:46:06 -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=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 169qMnWDnceV for <gen-art@ietfa.amsl.com>; Mon, 27 Feb 2012 22:46:05 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id C594221F8794 for <gen-art@ietf.org>; Mon, 27 Feb 2012 22:46:05 -0800 (PST)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q1S6js33028857; Tue, 28 Feb 2012 00:46:03 -0600
Received: from [164.48.125.35] (147.117.20.214) by eusaamw0712.eamcs.ericsson.se (147.117.20.182) with Microsoft SMTP Server id 8.3.213.0; Tue, 28 Feb 2012 01:45:48 -0500
From: Wassim Haddad <wassim.haddad@ericsson.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 27 Feb 2012 22:45:44 -0800
Message-ID: <007CE9D8-F845-4FCA-9655-108B53BC5C69@ericsson.com>
To: Gen-art <gen-art@ietf.org>
MIME-Version: 1.0 (Apple Message framework v1257)
X-Mailer: Apple Mail (2.1257)
Cc: draft-ietf-manet-packetbb-sec@tools.ietf.org, Adrian Farrel <adrian@olddog.co.uk>, sratliff@cisco.com
Subject: [Gen-art]  Gen-ART review of draft-ietf-manet-packetbb-sec-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, 28 Feb 2012 06:46:06 -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-manet-packetbb-sec-08
Reviewer:  Wassim Haddad=20
Review Date:  27 Feb 2012
IETF LC End Date: 02/27/2012
IESG Telechat Date: 03/01/2012

Summary: The draft is ready for publication as proposed standard

Major issues: none
Minor issues: none


Regards,

Wassim H.






From david.black@emc.com  Tue Feb 28 08:01:37 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 BC31121F857A for <gen-art@ietfa.amsl.com>; Tue, 28 Feb 2012 08:01:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.695
X-Spam-Level: 
X-Spam-Status: No, score=-109.695 tagged_above=-999 required=5 tests=[AWL=0.904, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B6vuiOP2BxRA for <gen-art@ietfa.amsl.com>; Tue, 28 Feb 2012 08:01:36 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 5687A21F8576 for <gen-art@ietf.org>; Tue, 28 Feb 2012 08:01:36 -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 q1SG1HWm011424 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 28 Feb 2012 11:01:32 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.226]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Tue, 28 Feb 2012 11:01:06 -0500
Received: from mxhub09.corp.emc.com (mxhub09.corp.emc.com [10.254.92.104]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q1SG0xa9002130; Tue, 28 Feb 2012 11:01:05 -0500
Received: from mx14a.corp.emc.com ([169.254.1.157]) by mxhub09.corp.emc.com ([10.254.92.104]) with mapi; Tue, 28 Feb 2012 11:01:04 -0500
From: <david.black@emc.com>
To: <rpenno@juniper.net>, <tasaxena@cisco.com>, <mohamed.boucadair@orange.com>, <ssenthil@cisco.com>, <gen-art@ietf.org>
Date: Tue, 28 Feb 2012 11:01:02 -0500
Thread-Topic: Gen-ART review of draft-ietf-behave-64-analysis-06
Thread-Index: Acz2Mith6bPDej4wTwiRs+mM/3oLzg==
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E05AEC8C63C@MX14A.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: ietfdbh@comcast.net, dthaler@microsoft.com, dwing@cisco.com, Martin.Stiemerling@neclab.eu
Subject: [Gen-art] Gen-ART review of draft-ietf-behave-64-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, 28 Feb 2012 16:01:37 -0000

I have been selected as the General Area Review Team (Gen-ART) reviewer
for this draft (for background on Gen-ART, please see=20
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-behave-64-analysis-06
Reviewer: David L. Black
Review Date: February 28, 2012
IETF LC End Date: February 20, 2012
IESG Telechat Date: March 1, 2012

Summary:

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

Comments:

This draft summarizes the improvements of stateful 64 techniques over the n=
ow-historic
NAT-PT techniques for communication between IPv4 and IPv6 networks.  The dr=
aft does a
nice job of summarizing the current situation in a fashion that avoids the =
reader
having to go through the plethora of details in the cited references.  The =
draft is
clearly written and reads well.

There is one open issue that's almost a nit - unfortunately, the IPsec disc=
ussion in
item 6 of Section 3.2 is wrong, even though it was copied from RFC 4966 (FW=
IW, it's
wrong there, also):

   6.  Unless UDP encapsulation is used for IPsec [RFC3948], traffic
       using IPsec AH (Authentication Header), in transport and tunnel
       mode, and IPsec ESP (Encapsulating Security Payload), in
       transport mode, is unable to be carried through NAT-PT without
       terminating the security associations on the NAT-PT, due to their
       usage of cryptographic integrity protection (Section 4.5 of
       [RFC4966]).

There are four problems with that explanation:

(1) AH cannot be UDP-encapsulated.  RFC 3948 says:

   Because the protection of the outer IP addresses in IPsec AH is
   inherently incompatible with NAT, the IPsec AH was left out of the
   scope of this protocol specification.

(2) The reasons for use of UDP encapsulation with ESP do not include ESP's
"usage of cryptographic integrity protection."  because ESP's cryptographic
integrity protection does not include any IP header fields.  The actual rea=
sons
are considerably more subtle and involved (e.g., traffic selector issues an=
d
NAT implementations that did not work correctly with IKE), see RFC 3715.

(3) Nit: The correct RFC 4966 reference is Section 2.1, not 4.5.

(4) A number of additional references are needed, starting with RFC 3715.

Here's an attempt to propose a text change:

OLD
   6.  Unless UDP encapsulation is used for IPsec [RFC3948], traffic
       using IPsec AH (Authentication Header), in transport and tunnel
       mode, and IPsec ESP (Encapsulating Security Payload), in
       transport mode, is unable to be carried through NAT-PT without
       terminating the security associations on the NAT-PT, due to their
       usage of cryptographic integrity protection (Section 4.5 of
       [RFC4966]).
NEW
   6.  IPsec traffic using AH (Authentication Header) [RFC4302] in
       both transport and tunnel modes cannot be carried through NAT-PT
       without terminating the security associations on the NAT-PT, due
       to the inclusion of IP header fields in the scope of AH's cryptograp=
hic
       integrity protection [RFC3715] (Section 2.1 of [RFC4966]).  In
       addition, IPsec traffic using ESP (Encapsulating Security Payload)
       [RFC4303] in transport mode generally uses UDP encapsulation [RFC394=
8]
       for NAT traversal (including NAT-PT traversal) in order to avoid the
       problems described in [RFC3715] (Section 2.1 of [RFC 4966]).
END

The Security Area should review the above proposed text change.

idnits 2.12.13 noted that RFC 2766 was obsoleted by RFC 4966 - this is
fine, as RFC 2766 does need to be cited.

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 adrian@olddog.co.uk  Tue Feb 28 08:23:45 2012
Return-Path: <adrian@olddog.co.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 311D621F8650 for <gen-art@ietfa.amsl.com>; Tue, 28 Feb 2012 08:23:45 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tfh2voYPDKt8 for <gen-art@ietfa.amsl.com>; Tue, 28 Feb 2012 08:23:44 -0800 (PST)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id 5ED7321F860D for <gen-art@ietf.org>; Tue, 28 Feb 2012 08:23:44 -0800 (PST)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id q1SGNdc1016929;  Tue, 28 Feb 2012 16:23:39 GMT
Received: from 950129200 ([90.84.144.203]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id q1SGNXR6016792 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 28 Feb 2012 16:23:37 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Christer Holmberg'" <christer.holmberg@ericsson.com>, "'General Area Review Team'" <gen-art@ietf.org>
References: <7F2072F1E0DE894DA4B517B93C6A05852C3F4BA9FF@ESESSCMS0356.eemea.ericsson.se>
In-Reply-To: <7F2072F1E0DE894DA4B517B93C6A05852C3F4BA9FF@ESESSCMS0356.eemea.ericsson.se>
Date: Tue, 28 Feb 2012 16:23:34 -0000
Message-ID: <01f601ccf635$5476e780$fd64b680$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHB9KbPIOCobkCCRymEU9iPW2oSypZoRKJA
Content-Language: en-gb
Cc: draft-betts-itu-oam-ach-code-point.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-betts-itu-oam-ach-code-point-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
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, 28 Feb 2012 16:23:45 -0000

Thanks Christer,

> 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>.
>=A0
> Please wait for direction from your document shepherd or AD
> before posting a new version of the draft.
>=A0
> Summary: The draft is ready for publication, with a couple of minor
> editorial nits.
>=A0
> Nits/editorial comments:
>=A0
> - Section 1: Please expand 'MPLS-TP' and 'MPLS' when first used,
>    and add a reference to where MPLS-TP and MPLS are defined.
>
> - Section 1: Please expand ACH when first used.=20
=A0
Yes to all of this except that "MPLS" is a well-known acronym in the RFC
Editor's list.

Cheers,
Adrian


From housley@vigilsec.com  Tue Feb 28 12:43:56 2012
Return-Path: <housley@vigilsec.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 729DB21F86D0 for <gen-art@ietfa.amsl.com>; Tue, 28 Feb 2012 12:43:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.546
X-Spam-Level: 
X-Spam-Status: No, score=-102.546 tagged_above=-999 required=5 tests=[AWL=0.053, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FSWxm+YcPRar for <gen-art@ietfa.amsl.com>; Tue, 28 Feb 2012 12:43:54 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 7C63B21F86C7 for <gen-art@ietf.org>; Tue, 28 Feb 2012 12:43:54 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 509F99A472A; Tue, 28 Feb 2012 15:44:10 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id QiKR35SNhQJy; Tue, 28 Feb 2012 15:43:48 -0500 (EST)
Received: from [192.168.2.104] (pool-96-241-165-215.washdc.fios.verizon.net [96.241.165.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id D7C169A4727; Tue, 28 Feb 2012 15:44:09 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <7C4DFCE962635144B8FAE8CA11D0BF1E05AEC8C63C@MX14A.corp.emc.com>
Date: Tue, 28 Feb 2012 15:43:53 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <D2B84A7F-BF4D-4E97-B3E8-EDAC64F76836@vigilsec.com>
References: <7C4DFCE962635144B8FAE8CA11D0BF1E05AEC8C63C@MX14A.corp.emc.com>
To: <david.black@emc.com> <david.black@emc.com>
X-Mailer: Apple Mail (2.1084)
Cc: tasaxena@cisco.com, mohamed.boucadair@orange.com, gen-art@ietf.org, rpenno@juniper.net, ssenthil@cisco.com, dthaler@microsoft.com, dwing@cisco.com, Martin.Stiemerling@neclab.eu, ietfdbh@comcast.net
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-behave-64-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, 28 Feb 2012 20:43:56 -0000

David:

Has an errata been entered against RFC 3948?


On Feb 28, 2012, at 11:01 AM, <david.black@emc.com> =
<david.black@emc.com> wrote:

> I have been selected as the General Area Review Team (Gen-ART) =
reviewer
> for this draft (for background on Gen-ART, please see=20
> http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).
>=20
> Please wait for direction from your document shepherd or
> AD before posting a new version of the draft.
>=20
> Document: draft-ietf-behave-64-analysis-06
> Reviewer: David L. Black
> Review Date: February 28, 2012
> IETF LC End Date: February 20, 2012
> IESG Telechat Date: March 1, 2012
>=20
> Summary:
>=20
> This draft is on the right track but has open issues, described in the =
review.
>=20
> Comments:
>=20
> This draft summarizes the improvements of stateful 64 techniques over =
the now-historic
> NAT-PT techniques for communication between IPv4 and IPv6 networks.  =
The draft does a
> nice job of summarizing the current situation in a fashion that avoids =
the reader
> having to go through the plethora of details in the cited references.  =
The draft is
> clearly written and reads well.
>=20
> There is one open issue that's almost a nit - unfortunately, the IPsec =
discussion in
> item 6 of Section 3.2 is wrong, even though it was copied from RFC =
4966 (FWIW, it's
> wrong there, also):
>=20
>   6.  Unless UDP encapsulation is used for IPsec [RFC3948], traffic
>       using IPsec AH (Authentication Header), in transport and tunnel
>       mode, and IPsec ESP (Encapsulating Security Payload), in
>       transport mode, is unable to be carried through NAT-PT without
>       terminating the security associations on the NAT-PT, due to =
their
>       usage of cryptographic integrity protection (Section 4.5 of
>       [RFC4966]).
>=20
> There are four problems with that explanation:
>=20
> (1) AH cannot be UDP-encapsulated.  RFC 3948 says:
>=20
>   Because the protection of the outer IP addresses in IPsec AH is
>   inherently incompatible with NAT, the IPsec AH was left out of the
>   scope of this protocol specification.
>=20
> (2) The reasons for use of UDP encapsulation with ESP do not include =
ESP's
> "usage of cryptographic integrity protection."  because ESP's =
cryptographic
> integrity protection does not include any IP header fields.  The =
actual reasons
> are considerably more subtle and involved (e.g., traffic selector =
issues and
> NAT implementations that did not work correctly with IKE), see RFC =
3715.
>=20
> (3) Nit: The correct RFC 4966 reference is Section 2.1, not 4.5.
>=20
> (4) A number of additional references are needed, starting with RFC =
3715.
>=20
> Here's an attempt to propose a text change:
>=20
> OLD
>   6.  Unless UDP encapsulation is used for IPsec [RFC3948], traffic
>       using IPsec AH (Authentication Header), in transport and tunnel
>       mode, and IPsec ESP (Encapsulating Security Payload), in
>       transport mode, is unable to be carried through NAT-PT without
>       terminating the security associations on the NAT-PT, due to =
their
>       usage of cryptographic integrity protection (Section 4.5 of
>       [RFC4966]).
> NEW
>   6.  IPsec traffic using AH (Authentication Header) [RFC4302] in
>       both transport and tunnel modes cannot be carried through NAT-PT
>       without terminating the security associations on the NAT-PT, due
>       to the inclusion of IP header fields in the scope of AH's =
cryptographic
>       integrity protection [RFC3715] (Section 2.1 of [RFC4966]).  In
>       addition, IPsec traffic using ESP (Encapsulating Security =
Payload)
>       [RFC4303] in transport mode generally uses UDP encapsulation =
[RFC3948]
>       for NAT traversal (including NAT-PT traversal) in order to avoid =
the
>       problems described in [RFC3715] (Section 2.1 of [RFC 4966]).
> END
>=20
> The Security Area should review the above proposed text change.
>=20
> idnits 2.12.13 noted that RFC 2766 was obsoleted by RFC 4966 - this is
> fine, as RFC 2766 does need to be cited.
>=20
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA  01748
> +1 (508) 293-7953             FAX: +1 (508) 293-7786
> david.black@emc.com        Mobile: +1 (978) 394-7754
> ----------------------------------------------------
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From david.black@emc.com  Tue Feb 28 12:50:06 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 3D74021E8056 for <gen-art@ietfa.amsl.com>; Tue, 28 Feb 2012 12:50:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.702
X-Spam-Level: 
X-Spam-Status: No, score=-109.702 tagged_above=-999 required=5 tests=[AWL=0.897, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O2tPGPiS7Etu for <gen-art@ietfa.amsl.com>; Tue, 28 Feb 2012 12:50:04 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 8CD8F21E8054 for <gen-art@ietf.org>; Tue, 28 Feb 2012 12:50:04 -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 q1SKnwCM027173 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 28 Feb 2012 15:49:59 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.226]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Tue, 28 Feb 2012 15:49:50 -0500
Received: from mxhub26.corp.emc.com (mxhub26.corp.emc.com [10.254.110.182]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q1SKnnRx015299; Tue, 28 Feb 2012 15:49:50 -0500
Received: from mx14a.corp.emc.com ([169.254.1.157]) by mxhub26.corp.emc.com ([10.254.110.182]) with mapi; Tue, 28 Feb 2012 15:49:49 -0500
From: <david.black@emc.com>
To: <housley@vigilsec.com>
Date: Tue, 28 Feb 2012 15:49:47 -0500
Thread-Topic: [Gen-art] Gen-ART review of draft-ietf-behave-64-analysis-06
Thread-Index: Acz2WdCswU2U/45JTxCRSwL3yq/sbAAABlog
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E05AEC8C7A8@MX14A.corp.emc.com>
References: <7C4DFCE962635144B8FAE8CA11D0BF1E05AEC8C63C@MX14A.corp.emc.com> <D2B84A7F-BF4D-4E97-B3E8-EDAC64F76836@vigilsec.com>
In-Reply-To: <D2B84A7F-BF4D-4E97-B3E8-EDAC64F76836@vigilsec.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: tasaxena@cisco.com, mohamed.boucadair@orange.com, gen-art@ietf.org, rpenno@juniper.net, ssenthil@cisco.com, dthaler@microsoft.com, dwing@cisco.com, Martin.Stiemerling@neclab.eu, ietfdbh@comcast.net
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-behave-64-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, 28 Feb 2012 20:50:06 -0000

Russ,

I think the errata would be needed against RFC 4966 (not 3948), and there i=
s
no errata on this topic, yet.  I can enter one after the final text for thi=
s
draft is approved.

Thanks,
--David

> -----Original Message-----
> From: Russ Housley [mailto:housley@vigilsec.com]
> Sent: Tuesday, February 28, 2012 3:44 PM
> To: Black, David
> Cc: rpenno@juniper.net; tasaxena@cisco.com; mohamed.boucadair@orange.com;=
 ssenthil@cisco.com; gen-
> art@ietf.org; ietfdbh@comcast.net; dthaler@microsoft.com; dwing@cisco.com=
;
> Martin.Stiemerling@neclab.eu
> Subject: Re: [Gen-art] Gen-ART review of draft-ietf-behave-64-analysis-06
>=20
> David:
>=20
> Has an errata been entered against RFC 3948?
>=20
>=20
> On Feb 28, 2012, at 11:01 AM, <david.black@emc.com> <david.black@emc.com>=
 wrote:
>=20
> > 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-behave-64-analysis-06
> > Reviewer: David L. Black
> > Review Date: February 28, 2012
> > IETF LC End Date: February 20, 2012
> > IESG Telechat Date: March 1, 2012
> >
> > Summary:
> >
> > This draft is on the right track but has open issues, described in the =
review.
> >
> > Comments:
> >
> > This draft summarizes the improvements of stateful 64 techniques over t=
he now-historic
> > NAT-PT techniques for communication between IPv4 and IPv6 networks.  Th=
e draft does a
> > nice job of summarizing the current situation in a fashion that avoids =
the reader
> > having to go through the plethora of details in the cited references.  =
The draft is
> > clearly written and reads well.
> >
> > There is one open issue that's almost a nit - unfortunately, the IPsec =
discussion in
> > item 6 of Section 3.2 is wrong, even though it was copied from RFC 4966=
 (FWIW, it's
> > wrong there, also):
> >
> >   6.  Unless UDP encapsulation is used for IPsec [RFC3948], traffic
> >       using IPsec AH (Authentication Header), in transport and tunnel
> >       mode, and IPsec ESP (Encapsulating Security Payload), in
> >       transport mode, is unable to be carried through NAT-PT without
> >       terminating the security associations on the NAT-PT, due to their
> >       usage of cryptographic integrity protection (Section 4.5 of
> >       [RFC4966]).
> >
> > There are four problems with that explanation:
> >
> > (1) AH cannot be UDP-encapsulated.  RFC 3948 says:
> >
> >   Because the protection of the outer IP addresses in IPsec AH is
> >   inherently incompatible with NAT, the IPsec AH was left out of the
> >   scope of this protocol specification.
> >
> > (2) The reasons for use of UDP encapsulation with ESP do not include ES=
P's
> > "usage of cryptographic integrity protection."  because ESP's cryptogra=
phic
> > integrity protection does not include any IP header fields.  The actual=
 reasons
> > are considerably more subtle and involved (e.g., traffic selector issue=
s and
> > NAT implementations that did not work correctly with IKE), see RFC 3715=
.
> >
> > (3) Nit: The correct RFC 4966 reference is Section 2.1, not 4.5.
> >
> > (4) A number of additional references are needed, starting with RFC 371=
5.
> >
> > Here's an attempt to propose a text change:
> >
> > OLD
> >   6.  Unless UDP encapsulation is used for IPsec [RFC3948], traffic
> >       using IPsec AH (Authentication Header), in transport and tunnel
> >       mode, and IPsec ESP (Encapsulating Security Payload), in
> >       transport mode, is unable to be carried through NAT-PT without
> >       terminating the security associations on the NAT-PT, due to their
> >       usage of cryptographic integrity protection (Section 4.5 of
> >       [RFC4966]).
> > NEW
> >   6.  IPsec traffic using AH (Authentication Header) [RFC4302] in
> >       both transport and tunnel modes cannot be carried through NAT-PT
> >       without terminating the security associations on the NAT-PT, due
> >       to the inclusion of IP header fields in the scope of AH's cryptog=
raphic
> >       integrity protection [RFC3715] (Section 2.1 of [RFC4966]).  In
> >       addition, IPsec traffic using ESP (Encapsulating Security Payload=
)
> >       [RFC4303] in transport mode generally uses UDP encapsulation [RFC=
3948]
> >       for NAT traversal (including NAT-PT traversal) in order to avoid =
the
> >       problems described in [RFC3715] (Section 2.1 of [RFC 4966]).
> > END
> >
> > The Security Area should review the above proposed text change.
> >
> > idnits 2.12.13 noted that RFC 2766 was obsoleted by RFC 4966 - this is
> > fine, as RFC 2766 does need to be cited.
> >
> > Thanks,
> > --David
> > ----------------------------------------------------
> > David L. Black, Distinguished Engineer
> > EMC Corporation, 176 South St., Hopkinton, MA  01748
> > +1 (508) 293-7953             FAX: +1 (508) 293-7786
> > david.black@emc.com        Mobile: +1 (978) 394-7754
> > ----------------------------------------------------
> >
> > _______________________________________________
> > Gen-art mailing list
> > Gen-art@ietf.org
> > https://www.ietf.org/mailman/listinfo/gen-art
>=20


From ben@nostrum.com  Tue Feb 28 15:34: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 8C78F21F8472; Tue, 28 Feb 2012 15:34:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.255
X-Spam-Level: 
X-Spam-Status: No, score=-102.255 tagged_above=-999 required=5 tests=[AWL=-0.255, BAYES_00=-2.599, J_CHICKENPOX_92=0.6, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MNiCanWg9zKy; Tue, 28 Feb 2012 15:34:24 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id BF98121F8470; Tue, 28 Feb 2012 15:34:23 -0800 (PST)
Received: from [10.0.1.2] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q1SNYMB3099708 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 28 Feb 2012 17:34:22 -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, 28 Feb 2012 17:34:27 -0600
Message-Id: <03557735-170E-422A-B507-45A07DEC22AE@nostrum.com>
To: draft-ietf-mext-mip6-tls.all@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1257)
X-Mailer: Apple Mail (2.1257)
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>, The IETF <ietf@ietf.org>
Subject: [Gen-art] Gen-ART LC/Telechat review of draft-ietf-mext-mip6-tls-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: Tue, 28 Feb 2012 23:34: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 wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document: draft-ietf-mext-mip6-tls-03
Reviewer: Ben Campbell
Review Date: 2012-02-28
IETF LC End Date: 2012-02-29
IESG Telechat date: 2012-03-01

Note: Since the Telechat review deadline is a day before the end of the =
IETF last call, this review serves both as a Telechat review and an IETF =
Last Call review.

Summary: This draft is basically ready for publication as an =
experimental RFC. There are some clarification issues that might should =
be addressed prior to publication.

Major issues:

None


Minor issues:

-- general:=20

The draft seems to be missing information on how to match TLS =
certificates to identities for HAC authentication.

-- section 1, paragraph 1, last sentence: "Client implementation =
experience has shown that the use of IKE(v2)/IPsec with Mobile IPv6 is =
fairly complex."

It might be worth elaborating on why this is true. Could this be solved =
with a cleaner software architecture rather than a protocol change?

-- section 5.4:  "The actual domain name used in queries is up to the =
deployment to decide and out of scope of this specification."
=20
This seems under specified for SRV

-- 5.7.4:

Are more than one DNS server allowed for each protocol?

-- 5.8:

I find this section confusing,as the first and second paragraphs seem to =
make contradictory statements about the authentication, particularly =
about the use of PSK. I think you are talking about authentication of =
the HAC in the TLS handshake vs an higher level authentication of the MN =
using PSK or EAP. I think this could use some clarification, as both =
paragraphs talks about authentication between the MN and HAC without =
mentioning direction.

Note that this is more clear in the security considerations section, but =
it would help for it to be more clear here.

-- 5.9, 2nd to last paragraph:

How do the first and last sentences relate? It seems to say set it to =
"1", except for this case in which you set it to "1".

-- 8.1:

Is this registry only for TLS based MIPv6? If so, does it need to be =
explicitly constrained to not used for MIPv6 in general?




Nits/editorial comments:

-- section 4.1:=20

A picture showing the element and key relationships could be helpful =
here.

-- section 4.3, third paragraph:

Please expand BA on first mention

--section 4.3, "Security association validity times", : "hours or weeks"

Hours _to_ weeks?

-- section 4.3, "selected cyphersuite": " The selected algorithms SHOULD =
be one of the mutually supported ciphersuites"

How could it be otherwise? (i.e. why the SHOULD, and is this really =
normative vs descriptive?)

-- section 4.4: "Home Agent IP Address" : "Concerns both IPv6 and IPv4 =
home agent addresses."

Dual stack only?  (same applies to "Home Address" section)

-- section 5.1, second paragraph: "All data inside the Content portion =
of the message container MUST be encoded using octets."

I suspect I'm missing a subtlety here--but how else could you do it? Is =
this intended to imply a byte-field, or to imply no additional encoding =
is used?

-- section 5.2: "=46rom now on, we use TypeValue header (TV-header) term =
to refer request-response message content HTTP-like headers."
=20
Maybe that should be moved to the terminology section?

-- section 5.3, 2nd paragraph: "The MN is also the peer that always =
sends only request messages and the HAC only sends response messages."

I'm having trouble parsing. Is their a spurious "always"?

-- section 5.5 : "same to that used by HTTP"

same _as_?

-- section 5.5.5

s/till/until

-- 5.5.8, 1st sentence:

Sentence fragment. Missing words?

-- 5.9, first paragraph:

Sentence fragment.

-- 5.9, 2nd to last paragraph:

s/"In case the"/"In the case that the"

-- 9:

A general discussion of threats would be helpful. Some aspects are =
scattered in the subsections, but a summary in one place would be nice.

-- 9.2:=20

It's not clear to me if the text in the "Dictionary Attack" section is =
actually related to dictionary attacks.


-- 6.1:

A picture of the general packet format would be nice. You've got them =
later for specific packet types, but no "general" picture.

--6.2:=20

Section seems mostly redundant to 6.1

-- 6.3:

Please expand HoTI on first use.

-- 7:

Please expand CoTI/CoT on first use

-- 8.3:

I'm not sure I understand the mnemonic relevance of "HALTSEC"






From mccap@petoni.org  Tue Feb 28 20:33:16 2012
Return-Path: <mccap@petoni.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 1BB9221E8039 for <gen-art@ietfa.amsl.com>; Tue, 28 Feb 2012 20:33:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iFIdskGJ36R5 for <gen-art@ietfa.amsl.com>; Tue, 28 Feb 2012 20:33:15 -0800 (PST)
Received: from mail-tul01m020-f172.google.com (mail-tul01m020-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3C2C321E8010 for <gen-art@ietf.org>; Tue, 28 Feb 2012 20:33:14 -0800 (PST)
Received: by obbeh20 with SMTP id eh20so4221765obb.31 for <gen-art@ietf.org>; Tue, 28 Feb 2012 20:33:14 -0800 (PST)
Received-SPF: pass (google.com: domain of mccap@petoni.org designates 10.182.31.50 as permitted sender) client-ip=10.182.31.50; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of mccap@petoni.org designates 10.182.31.50 as permitted sender) smtp.mail=mccap@petoni.org; dkim=pass header.i=mccap@petoni.org
Received: from mr.google.com ([10.182.31.50]) by 10.182.31.50 with SMTP id x18mr7982481obh.53.1330489994402 (num_hops = 1); Tue, 28 Feb 2012 20:33:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=petoni.org; s=google; h=mime-version:x-originating-ip:date:message-id:subject:from:to :content-type; bh=iXv2g7zkwozl+Z7n5nIvwjqV/l38YZ+YufaFw7szdjs=; b=G6GYUZFKPZybQbL2tloXlEa0veIzZNadPqWu+aPSkDSaJniMcBX/xHRlC5v4QJph3I pC9VEivwniXiWU7W292Nrr6YqvyozMpy2hnco43OMWYXAjGr2RVSF7UmAO6CAgZMPmTo ZX2hevE3e9/5m+6B/pUUtIDIEGDZUU2eUzEUE=
MIME-Version: 1.0
Received: by 10.182.31.50 with SMTP id x18mr6964649obh.53.1330489994323; Tue, 28 Feb 2012 20:33:14 -0800 (PST)
Received: by 10.60.13.102 with HTTP; Tue, 28 Feb 2012 20:33:14 -0800 (PST)
X-Originating-IP: [68.45.157.93]
Date: Tue, 28 Feb 2012 23:33:14 -0500
Message-ID: <CACvMsLF5XNGWM16=vsnto4oFmNwLwajqE6num8U4z99FfKfn1A@mail.gmail.com>
From: Pete McCann <mccap@petoni.org>
To: gen-art@ietf.org, draft-ietf-pcn-encoding-comparison.all@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQli3d+3qn5O/GU6IO4fNV/xnT0PukbDnJHA8E/6Vdl2K+jV53tJzCak5IuW204RwBB/6AOv
Subject: [Gen-art] Gen-ART Telechat Review of draft-ietf-pcn-encoding-comparison-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, 29 Feb 2012 04:33:16 -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-pcn-encoding-comparison-08
Reviewer: Peter McCann
Review Date: 2012-02-28
IETF LC End Date:
IESG Telechat date: 2012-03-01

Summary: Ready

Major issues: None

Minor issues:

Section 3.3.3.4:
   With the normal mode, the ECN field of the inner header is copied to
   the ECN field of the outer header on encapsulation (like the limited
   functionality option in Section 3.3.3.1).
The limited functionality option says to set the outer header to not-ECT.
This seems to contradict the above statement.

Nits/editorial comments:

Section 3.3.3.3:
   full-
   functionality option in Section 3.3.2.2.
I think you meant "Section 3.3.3.2".  One other place in this
paragraph needs this correction.

Section 4.2:
   The problem with 3-in-1 encoding is that the 10-codepoint does not
   survive decapsulation with the tunneling options in Section 3.3.2.1 -
   3.3.2.3.
Again, you meant 3.3.3.1 - 3.3.3.3

From jouni.korhonen@nsn.com  Tue Feb 28 23:14:22 2012
Return-Path: <jouni.korhonen@nsn.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 C890B21F85B4; Tue, 28 Feb 2012 23:14:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.299
X-Spam-Level: 
X-Spam-Status: No, score=-106.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_92=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ISdmzJ3cyVvP; Tue, 28 Feb 2012 23:14:22 -0800 (PST)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 8E84321F855A; Tue, 28 Feb 2012 23:14:21 -0800 (PST)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id q1T7EJa8012121 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 29 Feb 2012 08:14:19 +0100
Received: from demuexc023.nsn-intra.net (demuexc023.nsn-intra.net [10.150.128.36]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q1T7EDwg022419; Wed, 29 Feb 2012 08:14:19 +0100
Received: from FIESEXC035.nsn-intra.net ([10.159.0.25]) by demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 29 Feb 2012 08:14:18 +0100
Received: from 10.144.254.14 ([10.144.254.14]) by FIESEXC035.nsn-intra.net ([10.159.0.182]) via Exchange Front-End Server demuexc023.nsn-intra.net ([10.150.128.36]) with Microsoft Exchange Server HTTP-DAV ; Wed, 29 Feb 2012 07:14:18 +0000
User-Agent: Microsoft-Entourage/12.32.0.111121
Date: Wed, 29 Feb 2012 09:14:16 +0200
From: Jouni Korhonen <jouni.korhonen@nsn.com>
To: ext Ben Campbell <ben@nostrum.com>, <draft-ietf-mext-mip6-tls.all@tools.ietf.org>
Message-ID: <CB739CE8.143E2%jouni.korhonen@nsn.com>
Thread-Topic: Gen-ART LC/Telechat review of draft-ietf-mext-mip6-tls-03
Thread-Index: Acz2sb7wE1W7YQs4502UdTOzhMgCUQ==
In-Reply-To: <03557735-170E-422A-B507-45A07DEC22AE@nostrum.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 29 Feb 2012 07:14:18.0706 (UTC) FILETIME=[C08DBB20:01CCF6B1]
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 5263
X-purgate-ID: 151667::1330499660-000015E0-4D29BBA1/0-0/0-0
X-Mailman-Approved-At: Wed, 29 Feb 2012 04:48:45 -0800
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC/Telechat review of draft-ietf-mext-mip6-tls-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: Wed, 29 Feb 2012 07:14:22 -0000

Thanks Ben for a thorough review. Very good comments indeed. We'll come back
to this in a bit.. you know -00 deadline approaching and such ;)

- Jouni


On 2/29/12 1:34 AM, "ext Ben Campbell" <ben@nostrum.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 wait for direction from your document shepherd
> or AD before posting a new version of the draft.
> 
> Document: draft-ietf-mext-mip6-tls-03
> Reviewer: Ben Campbell
> Review Date: 2012-02-28
> IETF LC End Date: 2012-02-29
> IESG Telechat date: 2012-03-01
> 
> Note: Since the Telechat review deadline is a day before the end of the IETF
> last call, this review serves both as a Telechat review and an IETF Last Call
> review.
> 
> Summary: This draft is basically ready for publication as an experimental RFC.
> There are some clarification issues that might should be addressed prior to
> publication.
> 
> Major issues:
> 
> None
> 
> 
> Minor issues:
> 
> -- general: 
> 
> The draft seems to be missing information on how to match TLS certificates to
> identities for HAC authentication.
> 
> -- section 1, paragraph 1, last sentence: "Client implementation experience
> has shown that the use of IKE(v2)/IPsec with Mobile IPv6 is fairly complex."
> 
> It might be worth elaborating on why this is true. Could this be solved with a
> cleaner software architecture rather than a protocol change?
> 
> -- section 5.4:  "The actual domain name used in queries is up to the
> deployment to decide and out of scope of this specification."
>  
> This seems under specified for SRV
> 
> -- 5.7.4:
> 
> Are more than one DNS server allowed for each protocol?
> 
> -- 5.8:
> 
> I find this section confusing,as the first and second paragraphs seem to make
> contradictory statements about the authentication, particularly about the use
> of PSK. I think you are talking about authentication of the HAC in the TLS
> handshake vs an higher level authentication of the MN using PSK or EAP. I
> think this could use some clarification, as both paragraphs talks about
> authentication between the MN and HAC without mentioning direction.
> 
> Note that this is more clear in the security considerations section, but it
> would help for it to be more clear here.
> 
> -- 5.9, 2nd to last paragraph:
> 
> How do the first and last sentences relate? It seems to say set it to "1",
> except for this case in which you set it to "1".
> 
> -- 8.1:
> 
> Is this registry only for TLS based MIPv6? If so, does it need to be
> explicitly constrained to not used for MIPv6 in general?
> 
> 
> 
> 
> Nits/editorial comments:
> 
> -- section 4.1: 
> 
> A picture showing the element and key relationships could be helpful here.
> 
> -- section 4.3, third paragraph:
> 
> Please expand BA on first mention
> 
> --section 4.3, "Security association validity times", : "hours or weeks"
> 
> Hours _to_ weeks?
> 
> -- section 4.3, "selected cyphersuite": " The selected algorithms SHOULD be
> one of the mutually supported ciphersuites"
> 
> How could it be otherwise? (i.e. why the SHOULD, and is this really normative
> vs descriptive?)
> 
> -- section 4.4: "Home Agent IP Address" : "Concerns both IPv6 and IPv4 home
> agent addresses."
> 
> Dual stack only?  (same applies to "Home Address" section)
> 
> -- section 5.1, second paragraph: "All data inside the Content portion of the
> message container MUST be encoded using octets."
> 
> I suspect I'm missing a subtlety here--but how else could you do it? Is this
> intended to imply a byte-field, or to imply no additional encoding is used?
> 
> -- section 5.2: "From now on, we use TypeValue header (TV-header) term to
> refer request-response message content HTTP-like headers."
>  
> Maybe that should be moved to the terminology section?
> 
> -- section 5.3, 2nd paragraph: "The MN is also the peer that always sends only
> request messages and the HAC only sends response messages."
> 
> I'm having trouble parsing. Is their a spurious "always"?
> 
> -- section 5.5 : "same to that used by HTTP"
> 
> same _as_?
> 
> -- section 5.5.5
> 
> s/till/until
> 
> -- 5.5.8, 1st sentence:
> 
> Sentence fragment. Missing words?
> 
> -- 5.9, first paragraph:
> 
> Sentence fragment.
> 
> -- 5.9, 2nd to last paragraph:
> 
> s/"In case the"/"In the case that the"
> 
> -- 9:
> 
> A general discussion of threats would be helpful. Some aspects are scattered
> in the subsections, but a summary in one place would be nice.
> 
> -- 9.2: 
> 
> It's not clear to me if the text in the "Dictionary Attack" section is
> actually related to dictionary attacks.
> 
> 
> -- 6.1:
> 
> A picture of the general packet format would be nice. You've got them later
> for specific packet types, but no "general" picture.
> 
> --6.2: 
> 
> Section seems mostly redundant to 6.1
> 
> -- 6.3:
> 
> Please expand HoTI on first use.
> 
> -- 7:
> 
> Please expand CoTI/CoT on first use
> 
> -- 8.3:
> 
> I'm not sure I understand the mnemonic relevance of "HALTSEC"
> 
> 
> 
> 
> 


From mohamed.boucadair@orange.com  Wed Feb 29 01:37:10 2012
Return-Path: <mohamed.boucadair@orange.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 525EC21F8879 for <gen-art@ietfa.amsl.com>; Wed, 29 Feb 2012 01:37:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.146
X-Spam-Level: 
X-Spam-Status: No, score=-2.146 tagged_above=-999 required=5 tests=[AWL=0.102,  BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1L9r49uu11Ke for <gen-art@ietfa.amsl.com>; Wed, 29 Feb 2012 01:37:09 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id 4191721F8876 for <gen-art@ietf.org>; Wed, 29 Feb 2012 01:37:03 -0800 (PST)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm09.si.francetelecom.fr (ESMTP service) with ESMTP id B39E52DC3CA; Wed, 29 Feb 2012 10:37:01 +0100 (CET)
Received: from PUEXCH51.nanterre.francetelecom.fr (unknown [10.101.44.31]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id 8E27627C054; Wed, 29 Feb 2012 10:37:01 +0100 (CET)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.12]) by PUEXCH51.nanterre.francetelecom.fr ([10.101.44.31]) with mapi; Wed, 29 Feb 2012 10:37:01 +0100
From: <mohamed.boucadair@orange.com>
To: "david.black@emc.com" <david.black@emc.com>, "rpenno@juniper.net" <rpenno@juniper.net>, "tasaxena@cisco.com" <tasaxena@cisco.com>, "ssenthil@cisco.com" <ssenthil@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Date: Wed, 29 Feb 2012 10:37:00 +0100
Thread-Topic: Gen-ART review of draft-ietf-behave-64-analysis-06
Thread-Index: Acz2Mith6bPDej4wTwiRs+mM/3oLzgAkSCQA
Message-ID: <94C682931C08B048B7A8645303FDC9F35D88B262B7@PUEXCB1B.nanterre.francetelecom.fr>
References: <7C4DFCE962635144B8FAE8CA11D0BF1E05AEC8C63C@MX14A.corp.emc.com>
In-Reply-To: <7C4DFCE962635144B8FAE8CA11D0BF1E05AEC8C63C@MX14A.corp.emc.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.2.29.81216
X-Mailman-Approved-At: Wed, 29 Feb 2012 04:49:19 -0800
Cc: "ietfdbh@comcast.net" <ietfdbh@comcast.net>, "dthaler@microsoft.com" <dthaler@microsoft.com>, "dwing@cisco.com" <dwing@cisco.com>, "Martin.Stiemerling@neclab.eu" <Martin.Stiemerling@neclab.eu>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-behave-64-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, 29 Feb 2012 09:37:10 -0000

Dear David,

Thank you for the review.=20

I adopted in my local copy the text you proposed to describe the IPsec issu=
e. I can even shorten the text to something like "IPsec complications with =
NAT-PT (Section 2.1 of [RFC4966])" but I prefer your text because it provid=
es more RFC pointers.

Cheers,
Med=20

> -----Message d'origine-----
> De : david.black@emc.com [mailto:david.black@emc.com]=20
> Envoy=E9 : mardi 28 f=E9vrier 2012 17:01
> =C0 : rpenno@juniper.net; tasaxena@cisco.com; BOUCADAIR Mohamed=20
> OLNC/NAD/TIP; ssenthil@cisco.com; gen-art@ietf.org
> Cc : david.black@emc.com; dwing@cisco.com;=20
> dthaler@microsoft.com; ietfdbh@comcast.net;=20
> Martin.Stiemerling@neclab.eu
> Objet : Gen-ART review of draft-ietf-behave-64-analysis-06
>=20
> I have been selected as the General Area Review Team=20
> (Gen-ART) reviewer
> for this draft (for background on Gen-ART, please see=20
> http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).
>=20
> Please wait for direction from your document shepherd or
> AD before posting a new version of the draft.
>=20
> Document: draft-ietf-behave-64-analysis-06
> Reviewer: David L. Black
> Review Date: February 28, 2012
> IETF LC End Date: February 20, 2012
> IESG Telechat Date: March 1, 2012
>=20
> Summary:
>=20
> This draft is on the right track but has open issues,=20
> described in the review.
>=20
> Comments:
>=20
> This draft summarizes the improvements of stateful 64=20
> techniques over the now-historic
> NAT-PT techniques for communication between IPv4 and IPv6=20
> networks.  The draft does a
> nice job of summarizing the current situation in a fashion=20
> that avoids the reader
> having to go through the plethora of details in the cited=20
> references.  The draft is
> clearly written and reads well.
>=20
> There is one open issue that's almost a nit - unfortunately,=20
> the IPsec discussion in
> item 6 of Section 3.2 is wrong, even though it was copied=20
> from RFC 4966 (FWIW, it's
> wrong there, also):
>=20
>    6.  Unless UDP encapsulation is used for IPsec [RFC3948], traffic
>        using IPsec AH (Authentication Header), in transport and tunnel
>        mode, and IPsec ESP (Encapsulating Security Payload), in
>        transport mode, is unable to be carried through NAT-PT without
>        terminating the security associations on the NAT-PT,=20
> due to their
>        usage of cryptographic integrity protection (Section 4.5 of
>        [RFC4966]).
>=20
> There are four problems with that explanation:
>=20
> (1) AH cannot be UDP-encapsulated.  RFC 3948 says:
>=20
>    Because the protection of the outer IP addresses in IPsec AH is
>    inherently incompatible with NAT, the IPsec AH was left out of the
>    scope of this protocol specification.
>=20
> (2) The reasons for use of UDP encapsulation with ESP do not=20
> include ESP's
> "usage of cryptographic integrity protection."  because ESP's=20
> cryptographic
> integrity protection does not include any IP header fields. =20
> The actual reasons
> are considerably more subtle and involved (e.g., traffic=20
> selector issues and
> NAT implementations that did not work correctly with IKE),=20
> see RFC 3715.
>=20
> (3) Nit: The correct RFC 4966 reference is Section 2.1, not 4.5.
>=20
> (4) A number of additional references are needed, starting=20
> with RFC 3715.
>=20
> Here's an attempt to propose a text change:
>=20
> OLD
>    6.  Unless UDP encapsulation is used for IPsec [RFC3948], traffic
>        using IPsec AH (Authentication Header), in transport and tunnel
>        mode, and IPsec ESP (Encapsulating Security Payload), in
>        transport mode, is unable to be carried through NAT-PT without
>        terminating the security associations on the NAT-PT,=20
> due to their
>        usage of cryptographic integrity protection (Section 4.5 of
>        [RFC4966]).
> NEW
>    6.  IPsec traffic using AH (Authentication Header) [RFC4302] in
>        both transport and tunnel modes cannot be carried=20
> through NAT-PT
>        without terminating the security associations on the=20
> NAT-PT, due
>        to the inclusion of IP header fields in the scope of=20
> AH's cryptographic
>        integrity protection [RFC3715] (Section 2.1 of [RFC4966]).  In
>        addition, IPsec traffic using ESP (Encapsulating=20
> Security Payload)
>        [RFC4303] in transport mode generally uses UDP=20
> encapsulation [RFC3948]
>        for NAT traversal (including NAT-PT traversal) in=20
> order to avoid the
>        problems described in [RFC3715] (Section 2.1 of [RFC 4966]).
> END
>=20
> The Security Area should review the above proposed text change.
>=20
> idnits 2.12.13 noted that RFC 2766 was obsoleted by RFC 4966 - this is
> fine, as RFC 2766 does need to be cited.
>=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 david.black@emc.com  Wed Feb 29 06:47:03 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 3EBBD21F86F6 for <gen-art@ietfa.amsl.com>; Wed, 29 Feb 2012 06:47:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.708
X-Spam-Level: 
X-Spam-Status: No, score=-109.708 tagged_above=-999 required=5 tests=[AWL=0.891, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ims8oAi0iifZ for <gen-art@ietfa.amsl.com>; Wed, 29 Feb 2012 06:47:01 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 5206921F86EF for <gen-art@ietf.org>; Wed, 29 Feb 2012 06:46:57 -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 q1TEkksF024900 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 29 Feb 2012 09:46:52 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.145]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Wed, 29 Feb 2012 09:46:35 -0500
Received: from mxhub11.corp.emc.com (mxhub11.corp.emc.com [10.254.92.106]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q1TEkVa0020663; Wed, 29 Feb 2012 09:46:34 -0500
Received: from mx14a.corp.emc.com ([169.254.1.157]) by mxhub11.corp.emc.com ([10.254.92.106]) with mapi; Wed, 29 Feb 2012 09:46:31 -0500
From: <david.black@emc.com>
To: <mohamed.boucadair@orange.com>, <rpenno@juniper.net>, <tasaxena@cisco.com>, <ssenthil@cisco.com>, <gen-art@ietf.org>
Date: Wed, 29 Feb 2012 09:46:30 -0500
Thread-Topic: Gen-ART review of draft-ietf-behave-64-analysis-06
Thread-Index: Acz2Mith6bPDej4wTwiRs+mM/3oLzgAkSCQAAAqGX+A=
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E05AEC8C94C@MX14A.corp.emc.com>
References: <7C4DFCE962635144B8FAE8CA11D0BF1E05AEC8C63C@MX14A.corp.emc.com> <94C682931C08B048B7A8645303FDC9F35D88B262B7@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F35D88B262B7@PUEXCB1B.nanterre.francetelecom.fr>
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: dthaler@microsoft.com, dwing@cisco.com, Martin.Stiemerling@neclab.eu, ietfdbh@comcast.net
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-behave-64-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, 29 Feb 2012 14:47:03 -0000

Hello Mohamed,

> I adopted in my local copy the text you proposed to describe the IPsec is=
sue. I can even shorten the
> text to something like "IPsec complications with NAT-PT (Section 2.1 of [=
RFC4966])" but I prefer your
> text because it provides more RFC pointers.

Thank you for picking up the text.

It would be helpful for the Security Area to double-check it - I've cc:'d S=
ean Turner (SEC AD) in the hope that he or one of the IPsec experts in the =
Security Directorate can quickly check this 1-paragraph proposed text chang=
e, as in addition to this draft, I will need to file the result as errata a=
gainst RFC 4966.

OLD
   6.  Unless UDP encapsulation is used for IPsec [RFC3948], traffic
       using IPsec AH (Authentication Header), in transport and tunnel
       mode, and IPsec ESP (Encapsulating Security Payload), in
       transport mode, is unable to be carried through NAT-PT without
       terminating the security associations on the NAT-PT, due to their
       usage of cryptographic integrity protection (Section 4.5 of
       [RFC4966]).
NEW
   6.  IPsec traffic using AH (Authentication Header) [RFC4302] in
       both transport and tunnel modes cannot be carried through NAT-PT
       without terminating the security associations on the NAT-PT, due
       to the inclusion of IP header fields in the scope of AH's cryptograp=
hic
       integrity protection [RFC3715] (Section 2.1 of [RFC4966]).  In
       addition, IPsec traffic using ESP (Encapsulating Security Payload)
       [RFC4303] in transport mode generally uses UDP encapsulation [RFC394=
8]
       for NAT traversal (including NAT-PT traversal) in order to avoid the
       problems described in [RFC3715] (Section 2.1 of [RFC 4966]).
END

Thanks,
--David

> -----Original Message-----
> From: mohamed.boucadair@orange.com [mailto:mohamed.boucadair@orange.com]
> Sent: Wednesday, February 29, 2012 4:37 AM
> To: Black, David; rpenno@juniper.net; tasaxena@cisco.com; ssenthil@cisco.=
com; gen-art@ietf.org
> Cc: dwing@cisco.com; dthaler@microsoft.com; ietfdbh@comcast.net; Martin.S=
tiemerling@neclab.eu
> Subject: RE: Gen-ART review of draft-ietf-behave-64-analysis-06
>=20
> Dear David,
>=20
> Thank you for the review.
>=20
> I adopted in my local copy the text you proposed to describe the IPsec is=
sue. I can even shorten the
> text to something like "IPsec complications with NAT-PT (Section 2.1 of [=
RFC4966])" but I prefer your
> text because it provides more RFC pointers.
>=20
> Cheers,
> Med
>=20
> > -----Message d'origine-----
> > De : david.black@emc.com [mailto:david.black@emc.com]
> > Envoy=E9 : mardi 28 f=E9vrier 2012 17:01
> > =C0 : rpenno@juniper.net; tasaxena@cisco.com; BOUCADAIR Mohamed
> > OLNC/NAD/TIP; ssenthil@cisco.com; gen-art@ietf.org
> > Cc : david.black@emc.com; dwing@cisco.com;
> > dthaler@microsoft.com; ietfdbh@comcast.net;
> > Martin.Stiemerling@neclab.eu
> > Objet : Gen-ART review of draft-ietf-behave-64-analysis-06
> >
> > 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-behave-64-analysis-06
> > Reviewer: David L. Black
> > Review Date: February 28, 2012
> > IETF LC End Date: February 20, 2012
> > IESG Telechat Date: March 1, 2012
> >
> > Summary:
> >
> > This draft is on the right track but has open issues,
> > described in the review.
> >
> > Comments:
> >
> > This draft summarizes the improvements of stateful 64
> > techniques over the now-historic
> > NAT-PT techniques for communication between IPv4 and IPv6
> > networks.  The draft does a
> > nice job of summarizing the current situation in a fashion
> > that avoids the reader
> > having to go through the plethora of details in the cited
> > references.  The draft is
> > clearly written and reads well.
> >
> > There is one open issue that's almost a nit - unfortunately,
> > the IPsec discussion in
> > item 6 of Section 3.2 is wrong, even though it was copied
> > from RFC 4966 (FWIW, it's
> > wrong there, also):
> >
> >    6.  Unless UDP encapsulation is used for IPsec [RFC3948], traffic
> >        using IPsec AH (Authentication Header), in transport and tunnel
> >        mode, and IPsec ESP (Encapsulating Security Payload), in
> >        transport mode, is unable to be carried through NAT-PT without
> >        terminating the security associations on the NAT-PT,
> > due to their
> >        usage of cryptographic integrity protection (Section 4.5 of
> >        [RFC4966]).
> >
> > There are four problems with that explanation:
> >
> > (1) AH cannot be UDP-encapsulated.  RFC 3948 says:
> >
> >    Because the protection of the outer IP addresses in IPsec AH is
> >    inherently incompatible with NAT, the IPsec AH was left out of the
> >    scope of this protocol specification.
> >
> > (2) The reasons for use of UDP encapsulation with ESP do not
> > include ESP's
> > "usage of cryptographic integrity protection."  because ESP's
> > cryptographic
> > integrity protection does not include any IP header fields.
> > The actual reasons
> > are considerably more subtle and involved (e.g., traffic
> > selector issues and
> > NAT implementations that did not work correctly with IKE),
> > see RFC 3715.
> >
> > (3) Nit: The correct RFC 4966 reference is Section 2.1, not 4.5.
> >
> > (4) A number of additional references are needed, starting
> > with RFC 3715.
> >
> > Here's an attempt to propose a text change:
> >
> > OLD
> >    6.  Unless UDP encapsulation is used for IPsec [RFC3948], traffic
> >        using IPsec AH (Authentication Header), in transport and tunnel
> >        mode, and IPsec ESP (Encapsulating Security Payload), in
> >        transport mode, is unable to be carried through NAT-PT without
> >        terminating the security associations on the NAT-PT,
> > due to their
> >        usage of cryptographic integrity protection (Section 4.5 of
> >        [RFC4966]).
> > NEW
> >    6.  IPsec traffic using AH (Authentication Header) [RFC4302] in
> >        both transport and tunnel modes cannot be carried
> > through NAT-PT
> >        without terminating the security associations on the
> > NAT-PT, due
> >        to the inclusion of IP header fields in the scope of
> > AH's cryptographic
> >        integrity protection [RFC3715] (Section 2.1 of [RFC4966]).  In
> >        addition, IPsec traffic using ESP (Encapsulating
> > Security Payload)
> >        [RFC4303] in transport mode generally uses UDP
> > encapsulation [RFC3948]
> >        for NAT traversal (including NAT-PT traversal) in
> > order to avoid the
> >        problems described in [RFC3715] (Section 2.1 of [RFC 4966]).
> > END
> >
> > The Security Area should review the above proposed text change.
> >
> > idnits 2.12.13 noted that RFC 2766 was obsoleted by RFC 4966 - this is
> > fine, as RFC 2766 does need to be cited.
> >
> > 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=
-7786
> > david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> > ----------------------------------------------------
> >
> >

From housley@vigilsec.com  Wed Feb 29 11:04:56 2012
Return-Path: <housley@vigilsec.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 0122021F87AB for <gen-art@ietfa.amsl.com>; Wed, 29 Feb 2012 11:04:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.549
X-Spam-Level: 
X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W+6KsklthZtL for <gen-art@ietfa.amsl.com>; Wed, 29 Feb 2012 11:04:55 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id D407821F866B for <gen-art@ietf.org>; Wed, 29 Feb 2012 11:04:53 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id B704CF2403F; Wed, 29 Feb 2012 14:05:19 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id yoBlMnO-pT3S; Wed, 29 Feb 2012 14:04:18 -0500 (EST)
Received: from [192.168.2.104] (pool-96-241-165-215.washdc.fios.verizon.net [96.241.165.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 7FB38F24035; Wed, 29 Feb 2012 14:05:18 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <4F279B35.9010409@restena.lu>
Date: Wed, 29 Feb 2012 14:04:51 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <F2F2B210-D61C-42A1-A947-B59414A36687@vigilsec.com>
References: <CACvMsLGwVVF3x92O7j-eBjC4_PZ2EC_DuP-pgi1E-4-XkqT6SA@mail.gmail.com> <4F279B35.9010409@restena.lu>
To: Pete McCann <mccap@petoni.org>
X-Mailer: Apple Mail (2.1084)
Cc: IETF Gen-ART <gen-art@ietf.org>, Dan Romascanu <dromasca@gmail.com>
Subject: Re: [Gen-art] Gen-ART Telechat Review of draft-ietf-radext-radsec-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, 29 Feb 2012 19:04:56 -0000

Pete:

I did not see a response to this message.  Do these changes resolve your =
concerns?

Russ


On Jan 31, 2012, at 2:41 AM, Stefan Winter wrote:

> Hello,
>=20
> thanks for your review!
>=20
>> Minor issues:
>>=20
>> Section 2.4:
>>   In TLS-X.509 with PKI infrastructure, a client is uniquely =
identified
>>   by the serial number of the tuple (presented client
>>   certificate;Issuer).
>> SHOULD BE:
>>   In TLS-X.509 with PKI infrastructure, a client is uniquely =
identified
>>   by the tuple (serial number of presented client =
certificate;Issuer).
>=20
> Right, thanks for spotting; fixed now in my working copy.
>=20
>> Because RADIUS supports the Disconnect Request (server-to-client) =
message,
>> it seems that there is some requirement to keep the TLS session open =
for the
>> duration of the access that was authorized.  Otherwise, the server =
would not be
>> able to send such a packet to the client without initiating its own
>> TLS connection
>> which may not be possible or desirable.  Is this aspect of the =
specification
>> inherited from the referenced TCP specification?  It may be helpful =
to
>> add a paragraph
>> about this issue.
>=20
> Dynamic Authoirzation traffic is only very loosely coupled with the
> corresponding authentication traffic. In particular, RFC5176 states =
that
> a DynAuth Client (i.e. the one that would initiate the DM message) may
> or may not be co-located with the RADIUS server which handled the
> authentication.
> There's a recommendation that a DynAuth client should not send its
> traffic directly to the NAS and instead route it via the RADIUS =
server.
> If that recommendation is followed, it may make sense to re-use the =
same
> TLS session to send the packets indeed.
> But it is certainly not a *requirement* that these types of traffic =
are
> "bundled" together, or even just take the same path.
>=20
> It's true that there may be some operational hassle in setting up a =
TLS
> session in the reverse direction if the original TLS session doesn't
> exist any more. RADIUS/TLS shares this fate with all the other
> transports though (in RADIUS/UDP, getting in the reverse direction
> through a firewall, possibly combined with traversing NAT is "fun"; =
same
> goes for RADIUS/TCP). So, nothing "new" here IMHO.
>=20
>> Nits/editorial comments:
>>=20
>> Section 2.3:
>>   x.y.z
>> Did you mean to fill in a real section number here?
>=20
> Right, for TLS 1.2 that would be RFC6066, section 6.
>=20
> I have updated the text to state:
>=20
>          +  Implementations SHOULD indicate their trusted =
Certification
>             Authorities.  For TLS 1.2, this is done using [RFC5246]
>             section 7.4.4 "certificate authorities" (server side) and
>             [RFC6066] Section 6 "Trusted CA Indication" (client side).
>             See also Section 3.2.
>=20
> I'm wondering if I should also include exact pointers to the TLS 1.1
> equivalents. After all TLS 1.1 is fading out anyway, so I could =
imagine
> to leave that as the famous "exercise to the reader" if he wants to =
use
> TLS 1.1 still. I wouldn't mind adding them explicitly though; just let
> me know what you think is preferable.
>=20
>>   Note Section 3.4 (1) )
>> Missing open paren?
>=20
> Right. Fixed to:
>=20
>   4.  start exchanging RADIUS datagrams (note Section 3.4 (1) ).  The
>       shared secret to compute the (obsolete) MD5 integrity checks and
>       attribute encryption MUST be "radsec" (see Section 3.4 (2) ).
>=20
> Greetings,
>=20
> Stefan Winter
>=20
> --=20
> Stefan WINTER
> Ingenieur de Recherche
> Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education =
Nationale et
> de la Recherche
> 6, rue Richard Coudenhove-Kalergi
> L-1359 Luxembourg
>=20
> Tel: +352 424409 1
> Fax: +352 422473
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From dromasca@avaya.com  Wed Feb 29 11:35:04 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 9CF7721F8799 for <gen-art@ietfa.amsl.com>; Wed, 29 Feb 2012 11:35:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.363
X-Spam-Level: 
X-Spam-Status: No, score=-103.363 tagged_above=-999 required=5 tests=[AWL=0.236, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BuTU8ZeTDOc3 for <gen-art@ietfa.amsl.com>; Wed, 29 Feb 2012 11:35:03 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 8634421F87A1 for <gen-art@ietf.org>; Wed, 29 Feb 2012 11:35:03 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAON8Tk/GmAcF/2dsb2JhbABEpk+NEIEHgXoBAQEBAgEBAQEJBh4+CwUHBAIBCA0EAwEBAQEKBgwLAQYBIAYfCQgBAQQTCA4Mh2IFC50wnCqJF4NjEwUBCwsEAkEUC4R/Bz0BDQEBBQQGBRWCSWMEiByTJIUZh1iBUwc
X-IronPort-AV: E=Sophos;i="4.73,504,1325480400"; d="scan'208";a="333370689"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 29 Feb 2012 14:35:02 -0500
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.13]) by co300216-co-erhwest-out.avaya.com with ESMTP; 29 Feb 2012 14:27:54 -0500
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 29 Feb 2012 20:34:57 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A0407534104@307622ANEX5.global.avaya.com>
In-Reply-To: <CAFgnS4V+1G-vaD2F6FT5K17zJegru1ZNUWbHXS7P-LT5R7AR=w@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Gen-art] Gen-ART Telechat Review of draft-ietf-radext-radsec-11
Thread-Index: Acz3GD65eY95Yb36Q5KhLsQ6ffN2YwAAL8MQ
References: <CACvMsLGwVVF3x92O7j-eBjC4_PZ2EC_DuP-pgi1E-4-XkqT6SA@mail.gmail.com><4F279B35.9010409@restena.lu><F2F2B210-D61C-42A1-A947-B59414A36687@vigilsec.com> <CAFgnS4V+1G-vaD2F6FT5K17zJegru1ZNUWbHXS7P-LT5R7AR=w@mail.gmail.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Pete McCann" <mccap@petoni.org>
Cc: gen-art@ietf.org
Subject: Re: [Gen-art] Gen-ART Telechat Review of draft-ietf-radext-radsec-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, 29 Feb 2012 19:35:04 -0000

Hi,

Please use this address (dromasca@avaya.com) when you respond.=20

Thanks and Reagrds,

Dan

> -----Original Message-----
> From: Dan Romascanu [mailto:dromasca@gmail.com]
> Sent: Wednesday, February 29, 2012 9:28 PM
> To: Romascanu, Dan (Dan)
> Subject: Fwd: [Gen-art] Gen-ART Telechat Review of draft-ietf-radext-
> radsec-11
>=20
> ---------- Forwarded message ----------
> From: Russ Housley <housley@vigilsec.com>
> Date: Wed, Feb 29, 2012 at 9:04 PM
> Subject: Re: [Gen-art] Gen-ART Telechat Review of draft-ietf-radext-
> radsec-11
> To: Pete McCann <mccap@petoni.org>
> Cc: IETF Gen-ART <gen-art@ietf.org>, Dan Romascanu =
<dromasca@gmail.com>
>=20
>=20
> Pete:
>=20
> I did not see a response to this message. =A0Do these changes resolve
> your concerns?
>=20
> Russ
>=20
>=20
> On Jan 31, 2012, at 2:41 AM, Stefan Winter wrote:
>=20
> > Hello,
> >
> > thanks for your review!
> >
> >> Minor issues:
> >>
> >> Section 2.4:
> >> =A0 In TLS-X.509 with PKI infrastructure, a client is uniquely
> identified
> >> =A0 by the serial number of the tuple (presented client
> >> =A0 certificate;Issuer).
> >> SHOULD BE:
> >> =A0 In TLS-X.509 with PKI infrastructure, a client is uniquely
> identified
> >> =A0 by the tuple (serial number of presented client
> certificate;Issuer).
> >
> > Right, thanks for spotting; fixed now in my working copy.
> >
> >> Because RADIUS supports the Disconnect Request (server-to-client)
> message,
> >> it seems that there is some requirement to keep the TLS session =
open
> for the
> >> duration of the access that was authorized. =A0Otherwise, the =
server
> would not be
> >> able to send such a packet to the client without initiating its own
> >> TLS connection
> >> which may not be possible or desirable. =A0Is this aspect of the
> specification
> >> inherited from the referenced TCP specification? =A0It may be =
helpful
> to
> >> add a paragraph
> >> about this issue.
> >
> > Dynamic Authoirzation traffic is only very loosely coupled with the
> > corresponding authentication traffic. In particular, RFC5176 states
> that
> > a DynAuth Client (i.e. the one that would initiate the DM message)
> may
> > or may not be co-located with the RADIUS server which handled the
> > authentication.
> > There's a recommendation that a DynAuth client should not send its
> > traffic directly to the NAS and instead route it via the RADIUS
> server.
> > If that recommendation is followed, it may make sense to re-use the
> same
> > TLS session to send the packets indeed.
> > But it is certainly not a *requirement* that these types of traffic
> are
> > "bundled" together, or even just take the same path.
> >
> > It's true that there may be some operational hassle in setting up a
> TLS
> > session in the reverse direction if the original TLS session doesn't
> > exist any more. RADIUS/TLS shares this fate with all the other
> > transports though (in RADIUS/UDP, getting in the reverse direction
> > through a firewall, possibly combined with traversing NAT is "fun";
> same
> > goes for RADIUS/TCP). So, nothing "new" here IMHO.
> >
> >> Nits/editorial comments:
> >>
> >> Section 2.3:
> >> =A0 x.y.z
> >> Did you mean to fill in a real section number here?
> >
> > Right, for TLS 1.2 that would be RFC6066, section 6.
> >
> > I have updated the text to state:
> >
> > =A0 =A0 =A0 =A0 =A0+ =A0Implementations SHOULD indicate their =
trusted
> Certification
> > =A0 =A0 =A0 =A0 =A0 =A0 Authorities. =A0For TLS 1.2, this is done =
using [RFC5246]
> > =A0 =A0 =A0 =A0 =A0 =A0 section 7.4.4 "certificate authorities" =
(server side) and
> > =A0 =A0 =A0 =A0 =A0 =A0 [RFC6066] Section 6 "Trusted CA Indication" =
(client
> side).
> > =A0 =A0 =A0 =A0 =A0 =A0 See also Section 3.2.
> >
> > I'm wondering if I should also include exact pointers to the TLS 1.1
> > equivalents. After all TLS 1.1 is fading out anyway, so I could
> imagine
> > to leave that as the famous "exercise to the reader" if he wants to
> use
> > TLS 1.1 still. I wouldn't mind adding them explicitly though; just
> let
> > me know what you think is preferable.
> >
> >> =A0 Note Section 3.4 (1) )
> >> Missing open paren?
> >
> > Right. Fixed to:
> >
> > =A0 4. =A0start exchanging RADIUS datagrams (note Section 3.4 (1) ). =
=A0The
> > =A0 =A0 =A0 shared secret to compute the (obsolete) MD5 integrity =
checks
> and
> > =A0 =A0 =A0 attribute encryption MUST be "radsec" (see Section 3.4 =
(2) ).
> >
> > Greetings,
> >
> > Stefan Winter
> >
> > --
> > Stefan WINTER
> > Ingenieur de Recherche
> > Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education =
Nationale
> et
> > de la Recherche
> > 6, rue Richard Coudenhove-Kalergi
> > L-1359 Luxembourg
> >
> > Tel: +352 424409 1
> > Fax: +352 422473
> >
> > _______________________________________________
> > Gen-art mailing list
> > Gen-art@ietf.org
> > https://www.ietf.org/mailman/listinfo/gen-art
>=20
>=20
>=20
> --
> Dan
> http://dan.romascanu.net/

From david.black@emc.com  Wed Feb 29 11:56:25 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 1F11121F87BE for <gen-art@ietfa.amsl.com>; Wed, 29 Feb 2012 11:56:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.715
X-Spam-Level: 
X-Spam-Status: No, score=-109.715 tagged_above=-999 required=5 tests=[AWL=0.884, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gnbqS0j-9dbn for <gen-art@ietfa.amsl.com>; Wed, 29 Feb 2012 11:56:24 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 5BA6721F87CC for <gen-art@ietf.org>; Wed, 29 Feb 2012 11:56:23 -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 q1TJuMux009084 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Wed, 29 Feb 2012 14:56:22 -0500
Received: from mailhub.lss.emc.com (mailhubhoprd01.lss.emc.com [10.254.221.251]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor) for <gen-art@ietf.org>; Wed, 29 Feb 2012 14:56:05 -0500
Received: from mxhub05.corp.emc.com (mxhub05.corp.emc.com [128.222.70.202]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q1TJu1qL030171 for <gen-art@ietf.org>; Wed, 29 Feb 2012 14:56:04 -0500
Received: from mx14a.corp.emc.com ([169.254.1.157]) by mxhub05.corp.emc.com ([128.222.70.202]) with mapi; Wed, 29 Feb 2012 14:56:03 -0500
From: <david.black@emc.com>
To: <gen-art@ietf.org>
Date: Wed, 29 Feb 2012 14:56:01 -0500
Thread-Topic: [Technical Errata Reported] RFC4966 (3142)
Thread-Index: Acz3GzmqLn5pgnVfS8Cr245D4RtKDAAAG/Gw
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E05AEC8CAD9@MX14A.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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: [Gen-art] FW: [Technical Errata Reported] RFC4966 (3142)
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, 29 Feb 2012 19:56:25 -0000

FYI - this errata was the result of Gen-ART review of draft-ietf-behave-64-=
analysis-06
which found problems in a paragraph copied from RFC 4966.

Thanks,
--David

-----Original Message-----
From: RFC Errata System [mailto:rfc-editor@rfc-editor.org]=20
Sent: Wednesday, February 29, 2012 2:43 PM
To: ietf@energizeurnet.com; elwynd@dial.pipex.com; rbonica@juniper.net; dro=
masca@avaya.com; fred.baker@cisco.com; joelja@bogus.com
Cc: Black, David; v6ops@ietf.org; rfc-editor@rfc-editor.org
Subject: [Technical Errata Reported] RFC4966 (3142)


The following errata report has been submitted for RFC4966,
"Reasons to Move the Network Address Translator - Protocol Translator (NAT-=
PT) to Historic Status".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=3D4966&eid=3D3142

--------------------------------------
Type: Technical
Reported by: David L. Black <david.black@emc.com>

Section: 2.1

Original Text
-------------
Unless UDP encapsulation is used for IPsec [RFC3498], traffic using
IPsec AH (Authentication Header), in transport and tunnel mode, and
IPsec ESP (Encapsulating Security Payload), in transport mode, is
unable to be carried through NAT-PT without terminating the security
associations on the NAT-PT, due to their usage of cryptographic
integrity protection.

Corrected Text
--------------
IPsec traffic using AH (Authentication Header) [RFC4302] in both
transport and tunnel modes cannot be carried through NAT-PT without
terminating the security associations on the NAT-PT, due to the
inclusion of IP header fields in the scope of AH's cryptographic
integrity protection [RFC3715].  In addition, IPsec traffic using
ESP (Encapsulating Security Payload) [RFC4303] in transport mode
generally uses UDP encapsulation [RFC3948] for NAT traversal
(including NAT-PT traversal) in order to avoid the problems
described in [RFC3715].


Notes
-----
This RFC4966 text was copied into draft-ietf-behave-64-analysis-06.
Gen-ART review of that draft found that the statement was incorrect
for ESP.  The correct explanations of the problems (in great detail)
can be found in RFC 3715.

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary.=20

--------------------------------------
RFC4966 (draft-ietf-v6ops-natpt-to-historic-00)
--------------------------------------
Title               : Reasons to Move the Network Address Translator - Prot=
ocol Translator (NAT-PT) to Historic Status
Publication Date    : July 2007
Author(s)           : C. Aoun, E. Davies
Category            : INFORMATIONAL
Source              : IPv6 Operations
Area                : Operations and Management
Stream              : IETF
Verifying Party     : IESG


From Francis.Dupont@fdupont.fr  Wed Feb 29 14:15:21 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 D014121E806F for <gen-art@ietfa.amsl.com>; Wed, 29 Feb 2012 14:15:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.587
X-Spam-Level: 
X-Spam-Status: No, score=-2.587 tagged_above=-999 required=5 tests=[AWL=0.012,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AaMVBu-I2rRD for <gen-art@ietfa.amsl.com>; Wed, 29 Feb 2012 14:15:20 -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 4BA9621E8056 for <gen-art@ietf.org>; Wed, 29 Feb 2012 14:15:09 -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 q1TMF7n9056089; Wed, 29 Feb 2012 23:15:07 +0100 (CET) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201202292215.q1TMF7n9056089@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: gen-art@ietf.org
Date: Wed, 29 Feb 2012 23:15:07 +0100
Sender: Francis.Dupont@fdupont.fr
Cc: draft-ietf-rmt-flute-revised.all@tools.ietf.org
Subject: [Gen-art] (quick) review of draft-ietf-rmt-flute-revised-13.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, 29 Feb 2012 22:15: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 wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document: draft-ietf-rmt-flute-revised-13.txt
Reviewer: Francis Dupont
Review Date: 20120229
IETF LC End Date: 20120224
IESG Telechat date: 20120301

Summary: Almost Ready

Important note: due to last comments from the Last Call it seems
there will be a -14 version...

Major issues: None

Minor issues: not a real one (it was inherited from RFC 5775) but
in the security considerations there is nothing about IPsec/AH
(BTW people who didn't implement it didn't implement the transport
mode (for IPsec/ESP) too :-).

Nits/editorial comments:
 - ToC page 3 and 9 page 36: Acknowledgements -> Acknowledgments

 - 1 page 6: please add a reference to RFC2357 (or make it an
  explicit reference)

 - 1.1.3 page 7: I suggest to add the "diode" in the environment
  where FLUTE can be used (diodes are more common than you can
  believe :-)

 - 3 page 9 (and other places): e.g. -> , e.g., and i.e. -> , i.e.,

 - 3.1 page 9: I'd like to get the type (e.g., integer) of fields,
  for instance I have no idea of what a TSI really looks like.

 - 6 page 27: session ; -> session; and at the next line
  session. -> session; (only the last item gets a dot)

 - 7.2.2 page 30: this is the place I am surprised to not get
  IPsec/AH [RFC4302] as an alternative to IPsec/ESP [RFC4303]
  when integrity and sender authentication is wanted.

 - 10 page 36:
  52134 Herzogenrath, Germany ->
  52134 Herzogenrath
  Germany

 - Authors' Addresses page 45: US -> USA
  (note: the Innovallee; is dubious too)

Regards

Francis.Dupont@fdupont.fr

PS: I expect to get the new version so to have more time
to read (more) carefully the body of the document (i.e., 3 - 6).
