
From meral.shirazipour@ericsson.com  Mon Oct  1 12:08:40 2012
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C10E321F8B0C for <gen-art@ietfa.amsl.com>; Mon,  1 Oct 2012 12:08:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.599
X-Spam-Level: 
X-Spam-Status: No, score=-7.599 tagged_above=-999 required=5 tests=[AWL=1.000,  BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x1-vLl0nXd35 for <gen-art@ietfa.amsl.com>; Mon,  1 Oct 2012 12:08:39 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id CE43C21F8B0B for <gen-art@ietf.org>; Mon,  1 Oct 2012 12:08:39 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q91JFTwO017676; Mon, 1 Oct 2012 14:15:43 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.2.164]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Mon, 1 Oct 2012 15:08:37 -0400
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "draft-ietf-fecframe-ldpc-all@tools.ietf.org" <draft-ietf-fecframe-ldpc-all@tools.ietf.org>
Date: Mon, 1 Oct 2012 15:08:35 -0400
Thread-Topic: Gen-ART Last Call review of draft-ietf-fecframe-ldpc-02
Thread-Index: Ac2gCCUIGq62/fwLSD2TBMU6tfh9hw==
Message-ID: <25DC600D0CC1F2479C7053ADEB93004E6DF62A0166@EUSAACMS0703.eamcs.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
Cc: "gen-art@ietf.org" <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART Last Call review of draft-ietf-fecframe-ldpc-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: Mon, 01 Oct 2012 19:08:41 -0000

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

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

Document: draft-ietf-fecframe-ldpc-02
Reviewer: Meral Shirazipour
Review Date: 2012-10-01
IETF LC End Date: 2012-10-01
IESG Telechat date: NA


Summary:
This draft is almost ready for publication as a standard track RFC, but I h=
ave some comments.

Nits/editorial comments:
[Page 3], Section 1, "ALC [RFC5775]", please spell out ALC: "Asynchronous L=
ayered Coding (ALC)"

[Page 3], Section 1, "NORM [RFC5740]", please spell out NORM: "NACK-Oriente=
d Reliable Multicast (NORM)"

[Page 4], line 3, ALU is first used, please spell out: "Application Data Un=
it (ADU)", or move section "3.3 Abbreviations" to the beginning.

[Page 4], Section "3.1.  Definitions", after the ":" for all definitions, p=
lease start with capital letters or with lower case (for consistency please=
 choose one)

[Page 5], for "ADU Block", it would clearer to have Flow ID, Length and Pad=
ding fields in parenthesis next to F[], L[], and Pad[] respectively.

[Page 5], after "FEC Framework Configuration Information" please add "(FFCI=
)".

[Page 5], section 4.1, "G MUST be equal..", please define G in section "3.2=
.  Notations".

[Page 9], last sentence, "Each ADUI contributes to exactly one source symbo=
l to the source block.", it is clearer to say "...of the source block."

[Page 15], Section 6.1.1, "(e.g., before versus after FEC protection, and w=
ithin the end-system versus in a middlebox)", please rephrase if possible, =
this is not very clear.

[Page 19], reference [SIMPLE_RS] is now at version 03.

[Page 19], reference [RFC5053]: title is missing "for Object Delivery"

-Overall for clarity, please adapt one method for spelling out acronyms (ei=
ther in one section in intro, or throughout the text as they are first used=
; but not both).
-Overall for clarity, some line feed would be useful in section 5. =20


Best Regards,
Meral

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

From mccap@petoni.org  Mon Oct  1 15:56:23 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 DB2D41F0D3F for <gen-art@ietfa.amsl.com>; Mon,  1 Oct 2012 15:56:23 -0700 (PDT)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dvkjv2b+hwcG for <gen-art@ietfa.amsl.com>; Mon,  1 Oct 2012 15:56:23 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 244441F0CF9 for <gen-art@ietf.org>; Mon,  1 Oct 2012 15:56:23 -0700 (PDT)
Received: by yenl13 with SMTP id l13so1596568yen.31 for <gen-art@ietf.org>; Mon, 01 Oct 2012 15:56:19 -0700 (PDT)
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=UFE5LyCFKB0mY8p57lA8WWS7RYArBq9NwAFBfODZkH0=; b=HJqkeustr/w0YuMYB8yXWf00WBSt09sau/gTVkoWIN5p0XptghA+aHfx8JWUire9h5 eeUXL31+i/wNoF19h4XTotYrD3MsLa8TciT673YKtr4sRK84MoIiCwXq/K7V6Cim5wmB IiS9XiBtB5ePJSzjEk+RB83a3FCIif8zlHA1o=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=UFE5LyCFKB0mY8p57lA8WWS7RYArBq9NwAFBfODZkH0=; b=Hr4bL9hrZukSy5kUIQKXOMzj6FiojGSXMfZX1TxRvMlol5SrKFP9JeGbkt0leAlKAZ xitGYvunP1qPkkzqu38qd3ZfJo6Rtxoyed0N5fDpUvGVwoXDCT6YExlm9SgUJ5J83xF+ fEltemFvrCzmSSrqgLh9waqW8GYGihad/7/J6J1fWoEym0B2bVYuZHqOrIWaQy/7d9nb eXvPoo+wZLxeSzld8VMpfLIUTfP/3hxVs8yG3cRyoKdr3S1t8Gd1NqAOYEoNssZzEEeU 9tBHicFDUK7OkyhrXRPc1G27gCY7iYV1ct8EutLlAeLNnaHMW8ykTvBoyNSP0Z107QOD 9R4g==
MIME-Version: 1.0
Received: by 10.236.125.133 with SMTP id z5mr17039442yhh.121.1349132179501; Mon, 01 Oct 2012 15:56:19 -0700 (PDT)
Received: by 10.101.89.7 with HTTP; Mon, 1 Oct 2012 15:56:19 -0700 (PDT)
X-Originating-IP: [68.45.157.93]
Date: Mon, 1 Oct 2012 18:56:19 -0400
Message-ID: <CACvMsLG97q4Zvo-xQ=L_u6C_YCTAiTuOujFoyUsM1P+NY-prmA@mail.gmail.com>
From: Pete McCann <mccap@petoni.org>
To: gen-art@ietf.org, draft-ietf-sidr-pfx-validate.all@tools.ietf.org,  ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQkcXOxLF8E5cJj1+o7F5lSARieLnxQOvef7cBVBLxmNT6GKnxqIPE2vIkte2q+/Ucbyed5H
Subject: [Gen-art] Gen-ART Last Call Review of draft-ietf-sidr-pfx-validate-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Oct 2012 22:56:24 -0000

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

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

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

Document:  draft-ietf-sidr-pfx-validate-09
Reviewer:  Peter McCann
Review Date:  2012-10-01
IETF LC End Date:  2012-10-01
IESG Telechat date: unknown

Summary: Ready

Major issues: None

Minor issues:

Section 4:
    An "affected prefix" is any prefix that
   was matched by a deleted or updated mapping, or could be matched by
   an added mapping.
SHOULD BE:
   An "affected prefix" is any prefix that
   was matched by a deleted or updated mapping, or could be matched by
   an added or updated mapping.

Nits/editorial comments:

Abstract:
   monkey-in-the-middle
That's a game of keep-away.  Did you mean man-in-the-middle?  Perhaps
this is a technical term that has been discussed on the mailing list.

From abegen@cisco.com  Tue Oct  2 08:37:35 2012
Return-Path: <abegen@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 CCCD521F852E for <gen-art@ietfa.amsl.com>; Tue,  2 Oct 2012 08:37:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0h3KGuneXJJg for <gen-art@ietfa.amsl.com>; Tue,  2 Oct 2012 08:37:35 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 1578621F84FC for <gen-art@ietf.org>; Tue,  2 Oct 2012 08:37:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1153; q=dns/txt; s=iport; t=1349192255; x=1350401855; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=Wm5dSQUXgC2nEjqQa4cb7SpYWi1ESJy9tMwY5BwmpWg=; b=Ea8x8nND5Ua2eHMX3HLZ7JAVNdanyC50Y8KmEGQwNsyanLRBYtzCO0Bo grQiF/8KLQJYQpVeCUNAVbExg5nSFeVgqgi+tXgbTA4bZ3fWe+xLwSqbT Zllbb1NWsEhX4u17wgIxGNX9KIPfTRuJQUM/zUkJen35tvk8crXZa8Q7s s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhsFABIJa1CtJXHA/2dsb2JhbABFgm64I4NJgQiCIgEEEgEnPxIBCCIUQiUCBAENDRqHYwGZDY9WkGORBWADpCuBaYJnghc
X-IronPort-AV: E=Sophos;i="4.80,524,1344211200"; d="scan'208";a="127541524"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-3.cisco.com with ESMTP; 02 Oct 2012 15:37:34 +0000
Received: from xhc-aln-x12.cisco.com (xhc-aln-x12.cisco.com [173.36.12.86]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id q92FbYcH007592 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 2 Oct 2012 15:37:34 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.02.0318.001; Tue, 2 Oct 2012 10:37:34 -0500
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>, "kozat@docomolabs-usa.com" <kozat@docomolabs-usa.com>, Greg Shepherd <gjshep@gmail.com>, "fecframe-chairs@tools.ietf.org" <fecframe-chairs@tools.ietf.org>, Martin Stiemerling <martin.stiemerling@neclab.eu>
Thread-Topic: Gen-ART review of draft-ietf-fecframe-pseudo-cdp-04
Thread-Index: AQHNnIA+q6L2oXhDAUiXeF29Cvt7A5emP28A
Date: Tue, 2 Oct 2012 15:37:34 +0000
Message-ID: <C15918F2FCDA0243A7C919DA7C4BE994E703D8@xmb-aln-x01.cisco.com>
In-Reply-To: <5063FDAB.3070006@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.4.120824
x-originating-ip: [10.86.247.224]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19230.001
x-tm-as-result: No--37.501000-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-ID: <A5C4CF785CAFFE419D05BADB2ADE2A7C@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-fecframe-pseudo-cdp-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, 02 Oct 2012 15:37:36 -0000

Hi Miguel,

Thanks for the review.


>- About the SDP example in Section 3.1. The first paragraph reads:
>
>    The SDP description below states that the source flow defined
>    by the tuple {*,*,233.252.0.1,30000} is identified with FID=3D0 and th=
e
>    source flow defined by the tuple {*,*,233.252.0.2,30000} is
>    identified with FID=3D1.
>
>
>However, the example shows flows does not show any flow with any token
>named "FID". I don't know if the text is trying to refer to the "mid"
>attribute, in which case the values are S1 and S2, respectively. Or the
>text is trying to refer to the "id" parameter of the "fec-source-flow"
>attribute. The text should not leave this interpretation to the reader.

It is the id parameter. I added text for this.

>- Figure 7 and 8. Do the captions need to indicate that these are "for
>IPv4", for example, in Figure 7: "Example of a source packet for IPv4"

Good idea.

>
>- idnits reveals that draft-ietf-fecframe-config-signaling ha sbeen
>published as RFC 6695.

Will replace it.

-acbegen

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


From christer.holmberg@ericsson.com  Tue Oct  2 10:49:39 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 B003821F855A for <gen-art@ietfa.amsl.com>; Tue,  2 Oct 2012 10:49:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.109
X-Spam-Level: 
X-Spam-Status: No, score=-6.109 tagged_above=-999 required=5 tests=[AWL=0.140,  BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q3RKSaTrxvsJ for <gen-art@ietfa.amsl.com>; Tue,  2 Oct 2012 10:49:38 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 81E7B21F8559 for <gen-art@ietf.org>; Tue,  2 Oct 2012 10:49:38 -0700 (PDT)
X-AuditID: c1b4fb2d-b7fea6d000002ccb-47-506b29306619
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id D9.AE.11467.0392B605; Tue,  2 Oct 2012 19:49:37 +0200 (CEST)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.99]) by esessmw0184.eemea.ericsson.se ([10.2.3.53]) with mapi; Tue, 2 Oct 2012 19:49:36 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-leiba-3777upd-eligibility.all@tools.ietf.org" <draft-leiba-3777upd-eligibility.all@tools.ietf.org>
Date: Tue, 2 Oct 2012 19:49:35 +0200
Thread-Topic: GenART LC review of draft-leiba-3777upd-eligibility-04
Thread-Index: AQHNoMZJpp7dA+oWuUewEbIdr7kWfg==
Message-ID: <7F2072F1E0DE894DA4B517B93C6A05853409FF2FD9@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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrCLMWRmVeSWpSXmKPExsUyM+Jvra6hZnaAwbULHBZdf/6yWVx99ZnF gcljyZKfTB5fLn9mC2CK4rJJSc3JLEst0rdL4Mp4d3oRW8Fhloq7c98wNzAeZu5i5OSQEDCR mHNuAhOELSZx4d56ti5GLg4hgVOMEu1vJrFDOLMZJX7u/8LSxcjBwSZgIdH9TxskLiIwg1Fi 44zlbCBxFgEViTNzBUEGCQvYS3xfOocNxBYRcJHYe+s9O4StJzHtzSqwZbwC4RLfmr4xgtiM QIu/n1oDFmcWEJe49WQ+1EECEkv2nIc6VFTi5eN/rBD1ohJ32tczQtTrSdyYOoUNwtaWWLbw NTPEfEGJkzOfsExgFJ6FZOwsJC2zkLTMQtKygJFlFaNwbmJmTnq5oV5qUWZycXF+nl5x6iZG YMgf3PJbdwfjqXMihxilOViUxHm5kvb7CwmkJ5akZqemFqQWxReV5qQWH2Jk4uCUamA0lrc2 mJlT/C+d5+Ry0TM3nZa1+8t37JpvlfbgW6tMc+eUPG318zWquy6yn6rrfs/j+k56M1NwzIw9 BatvSDjlWkl/lq/7GrDuTOFEed0vr96y9R9cl38qXenAZaZ1H7I12i9fklkrUvxbt2RHUUhO sM3Va0xmskZ7osxeVtum9usbnD5+/qASS3FGoqEWc1FxIgDWhKrhRwIAAA==
Subject: [Gen-art] GenART LC review of draft-leiba-3777upd-eligibility-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, 02 Oct 2012 17:49:39 -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-leiba-3777upd-eligibility-04
Reviewer:              Christer Holmberg
Review Date:         2012-10-02
IETF LC End Date: 2012-10-25
IESG Telechat date:

Summary: The document is well written, and is ready for publication.

Major issues: -

Minor issues: -

Nits/editorial comments: -

From peter@akayla.com  Tue Oct  2 16:49:39 2012
Return-Path: <peter@akayla.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB54C21F860B; Tue,  2 Oct 2012 16:49:39 -0700 (PDT)
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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KWb+dGoseKBF; Tue,  2 Oct 2012 16:49:39 -0700 (PDT)
Received: from p3plsmtpa06-05.prod.phx3.secureserver.net (p3plsmtpa06-05.prod.phx3.secureserver.net [173.201.192.106]) by ietfa.amsl.com (Postfix) with ESMTP id 1BC9321F8608; Tue,  2 Oct 2012 16:49:39 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa06-05.prod.phx3.secureserver.net with  id 6Ppd1k00G1huGat01PpeKF; Tue, 02 Oct 2012 16:49:38 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-6man-udpchecksums.all@tools.ietf.org>
Date: Tue, 2 Oct 2012 16:49:43 -0700
Message-ID: <002e01cda0f8$98f8d3f0$caea7bd0$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac2g8orrJo+0BFndRS2G2P+THDWYgQ==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART review of draft-ietf-6man-udpchecksums-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, 02 Oct 2012 23:49:39 -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-6man-udpchecksums-04
Reviewer: Peter Yee
Review Date: Sep-30-2012
IETF LC End Date: Oct-2-2012
IESG Telechat date: Oct-11-2012

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

Presuming the assumptions in I-D.ietf-6man-udpzero are valid and agreed to
by the community, this document
provides an update to 2460 to allow the use of zero checksum UDP packets
over IPv6 in certain cases involving
protocols tunneled inside of UDP packets.

Nits:

General: references throughout the document to various Internet Drafts will,
of course, need to be cleaned up.

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

Abstract, last sentence: "defines" -> "define"

Section 3, first sentence: "tunnelled" -> "tunneled"
	Change the comma after "checksum" to a period to split the sentence,
capitalizing the following "there".
	Then change "compute" -> "computing" and "check" -> "checking" for
parseability.

Section 3, last sentence: "cost, " -> "cost".

Section 4, 4th paragraph: "The below" -> "The points below"
	Also: "an UDP" -> "a UDP"

Section 4, 1st bullet item, last sentence: "reception UDP" -> "reception of
UDP"

Section 4, 4th bullet item, 1st sentence: "port, destination" -> "port, and
destination"
	Also: "fields :" -> "fields:" (eliminate a superfluous space
character)

Section 5, paragraph 5 (the replacement text), last sentence: you refer to
RFC 2460.  That
would seem to read oddly when the replacement text is actually inserted into
RFC 2460.
I think it would be preferable to put in a specific cross-reference to where
in 2460 the
existing method resides instead of the document itself.

Section 5, item 2, last sentence: "call," -> "call"

Section 5, item 5, 1st sentence: "UDP Tunnels" -> "UDP tunnels" for
consistency.

Section 5, item 6, 2 occurrences: "Non-IP" -> "non-IP"

Section 5, item 8, parenthetical: " Necessary" -> "necessary".  Note the
leading space before
"Necessary" that is omitted in the replacement.

Section 8 includes one incredibly long run-on sentence.  I would suggest
splitting it as follows:

However, this does not lead to any significant new vulnerabilities as
checksums are not a
security measure and can be easily generated by any attacker. Properly
configured tunnels
should check the validity of the inner packet and perform any needed
security checks
regardless of the checksum status. Most attacks are generated from
compromised hosts
which automatically create checksummed packets (in other words, it would
generally be
more, not less, effort for most attackers to generate zero UDP checksums on
the host).

Authors' Addresses:
Unused Fax and URI fields may be omitted.
Phone numbers  should be presented in international dialing format to
facilitate use, e.g.,
+1 703 501 4376 and +46 10 714 82 87.





From mahoney@nostrum.com  Thu Oct  4 15:21:19 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 D80F521F84CF for <gen-art@ietfa.amsl.com>; Thu,  4 Oct 2012 15:21:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.59
X-Spam-Level: 
X-Spam-Status: No, score=-2.59 tagged_above=-999 required=5 tests=[AWL=0.010,  BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gSy3xLT4nUzp for <gen-art@ietfa.amsl.com>; Thu,  4 Oct 2012 15:21:16 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 112D521F84CE for <gen-art@ietf.org>; Thu,  4 Oct 2012 15:21:14 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-57-93-208.dllstx.fios.verizon.net [173.57.93.208]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id q94MLE0c092595 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 4 Oct 2012 17:21:14 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <506E0BD9.8050705@nostrum.com>
Date: Thu, 04 Oct 2012 17:21:13 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:15.0) Gecko/20120907 Thunderbird/15.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.93.208 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2012-10-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: Thu, 04 Oct 2012 22:21:19 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end        Draft

Dan Romascanu     2012-10-12    draft-ietf-dnsext-rfc6195bis-04 *

David Black       2012-10-16    draft-ietf-softwire-dslite-deployment-06

Elwyn Davies      2012-10-17    draft-ietf-karp-ospf-analysis-05

Francis Dupont    2012-10-17    draft-ietf-dhc-client-id-06

Joel Halpern      2012-10-17    draft-ietf-softwire-stateless-4v6-motivation-04

Kathleen Moriarty 2012-11-01    draft-gont-intarea-obsolete-eid-option-01

Suresh Krishnan   2012-10-29    draft-ietf-dnsext-rfc2671bis-edns0-09 **

* On the Oct 11 telechat. The LC ends after the telechat ;-)
** 2nd last call


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

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


The standard template is included below.

Thanks,

Jean

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

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

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

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

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

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

From mahoney@nostrum.com  Thu Oct  4 15:27:29 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 C113821F8551 for <gen-art@ietfa.amsl.com>; Thu,  4 Oct 2012 15:27:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.591
X-Spam-Level: 
X-Spam-Status: No, score=-2.591 tagged_above=-999 required=5 tests=[AWL=0.009,  BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JxkFaWrJNfiZ for <gen-art@ietfa.amsl.com>; Thu,  4 Oct 2012 15:27:29 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 077A621F8545 for <gen-art@ietf.org>; Thu,  4 Oct 2012 15:27:28 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-57-93-208.dllstx.fios.verizon.net [173.57.93.208]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id q94MRMB8093170 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 4 Oct 2012 17:27:28 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <506E0D4A.6060709@nostrum.com>
Date: Thu, 04 Oct 2012 17:27:22 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:15.0) Gecko/20120907 Thunderbird/15.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.93.208 is authenticated by a trusted mechanism)
Subject: [Gen-art] Assignments for the 2012-10-11 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, 04 Oct 2012 22:27:29 -0000

Hi all,

The following reviewers have assignments:

Reviewer             LC end       Draft

Brian Carpenter      2012-09-18   draft-ietf-sipcore-proxy-feature-11 *

Dan Romascanu        2012-10-12   draft-ietf-dnsext-rfc6195bis-04

Francis Dupont       2012-09-25   draft-ietf-v6ops-ivi-icmp-address-06 **

Kathleen Moriarty    2012-08-13   draft-ietf-storm-iscsi-cons-07 *

Miguel Garcia        2012-10-01   draft-ietf-fecframe-pseudo-cdp-04 **

Meral Shirazipour    2012-10-01   draft-ietf-fecframe-ldpc-03 *

Peter Yee            2012-10-02   draft-ietf-6man-udpchecksums-04 **

Richard Barnes       2012-10-02   draft-ietf-6man-udpzero-06

Roni Even            2012-10-03   draft-ietf-6man-dad-proxy-05 **

Suresh Krishnan      2012-10-04   draft-ietf-abfab-gss-eap-naming-05

Wassim Haddad        2012-04-03   draft-ietf-avtext-splicing-for-rtp-09
Wassim Haddad        2012-08-22   draft-ietf-manet-olsrv2-16

* Earlier draft reviewed
** Already reviewed


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

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

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

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

Jean

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

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

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

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

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

From brian.e.carpenter@gmail.com  Fri Oct  5 06:27:53 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 A641F21F8759 for <gen-art@ietfa.amsl.com>; Fri,  5 Oct 2012 06:27:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.564
X-Spam-Level: 
X-Spam-Status: No, score=-103.564 tagged_above=-999 required=5 tests=[AWL=0.035, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gtEaIo9ZJ8BT for <gen-art@ietfa.amsl.com>; Fri,  5 Oct 2012 06:27:52 -0700 (PDT)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id C269321F8731 for <gen-art@ietf.org>; Fri,  5 Oct 2012 06:27:52 -0700 (PDT)
Received: by mail-ie0-f172.google.com with SMTP id 9so4377490iec.31 for <gen-art@ietf.org>; Fri, 05 Oct 2012 06:27:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type; bh=ZuKlKVCFk6j1JNemvLyftgWkHyw/t72S97Ww2VfMMM4=; b=msTnLSEKkJaMY3ro/Z3zg6vDGdW2emzathdEnh9YHd2/VC0lSBYeqyJezqL//HEwlT nnXUncUWOfsCJLsmALbQv6T1ppavyHAoSYWnPpw6HNFXqE6/D93tl/UGrasMdfjVTbug 1Z9B3w5aWL//nOltiEubBTZr/C+PGN4FXsZGKRPbpeHlpLm+DPqLJZ3sD2ySafGCWgc2 6hLp8ltuV42iSg9MOELIGE0ZUT00NUBWz3IfYzl5C7yGKrG4drVJRQ1OFdKflbe1pA/U 0lF9JQcWu2WQhCayyvPTYYzyD7BU4/8ijNtYiIxr0Uvp+9KIpw6qq3CurwRQG/9FMScq ZU5A==
Received: by 10.50.212.97 with SMTP id nj1mr1115336igc.26.1349443672218; Fri, 05 Oct 2012 06:27:52 -0700 (PDT)
Received: from [10.255.25.102] (50-76-68-140-static.hfc.comcastbusiness.net. [50.76.68.140]) by mx.google.com with ESMTPS id km8sm715289igc.12.2012.10.05.06.27.51 (version=SSLv3 cipher=OTHER); Fri, 05 Oct 2012 06:27:51 -0700 (PDT)
Message-ID: <506EE05C.1050608@gmail.com>
Date: Fri, 05 Oct 2012 14:27:56 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: draft-ietf-sipcore-proxy-feature.all@tools.ietf.org,  General Area Review Team <gen-art@ietf.org>
Content-Type: multipart/mixed; boundary="------------040108010808090902070301"
Subject: [Gen-art] Gen-ART telechat review of draft-ietf-sipcore-proxy-feature-11.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, 05 Oct 2012 13:27:53 -0000

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

Please see attached review.

     Brian


--------------040108010808090902070301
Content-Type: text/plain;
 name="draft-ietf-sipcore-proxy-feature-11-carpenter.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="draft-ietf-sipcore-proxy-feature-11-carpenter.txt"

SSBoYXZlIGJlZW4gc2VsZWN0ZWQgYXMgdGhlIEdlbmVyYWwgQXJlYSBSZXZpZXcgVGVhbSAo
R2VuLUFSVCkNCnJldmlld2VyIGZvciB0aGlzIGRyYWZ0IChmb3IgYmFja2dyb3VuZCBvbiBH
ZW4tQVJULCBwbGVhc2Ugc2VlDQpodHRwOi8vd3d3LmFsdmVzdHJhbmQubm8vaWV0Zi9nZW4v
YXJ0L2dlbi1hcnQtRkFRLmh0bWwpLg0KDQpQbGVhc2Ugd2FpdCBmb3IgZGlyZWN0aW9uIGZy
b20geW91ciBkb2N1bWVudCBzaGVwaGVyZA0Kb3IgQUQgYmVmb3JlIHBvc3RpbmcgYSBuZXcg
dmVyc2lvbiBvZiB0aGUgZHJhZnQuDQoNCkRvY3VtZW50OiBkcmFmdC1pZXRmLXNpcGNvcmUt
cHJveHktZmVhdHVyZS0xMQ0KUmV2aWV3ZXI6IEJyaWFuIENhcnBlbnRlcg0KUmV2aWV3IERh
dGU6IDIwMTItMTAtMDUNCklFVEYgTEMgRW5kIERhdGU6IDIwMTItMDktMTgNCklFU0cgVGVs
ZWNoYXQgZGF0ZTogMjAxMi0xMC0xMQ0KDQpTdW1tYXJ5OiAgUmVhZHkNCi0tLS0tLS0tDQoN
CkNvbW1lbnQ6IE15IExhc3QgQ2FsbCBjb21tZW50cyB3ZXJlIGhhbmRsZWQgYW5kIHRoZSBv
dGhlciByZWNlbnQgY2hhbmdlcyBhcmUgZmluZS4NCi0tLS0tLS0tDQo=
--------------040108010808090902070301--

From christer.holmberg@ericsson.com  Fri Oct  5 06:28:58 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 E649721F8686 for <gen-art@ietfa.amsl.com>; Fri,  5 Oct 2012 06:28:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.097
X-Spam-Level: 
X-Spam-Status: No, score=-6.097 tagged_above=-999 required=5 tests=[AWL=0.152,  BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cmVY+QkCAByZ for <gen-art@ietfa.amsl.com>; Fri,  5 Oct 2012 06:28:58 -0700 (PDT)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id BAF5B21F85B8 for <gen-art@ietf.org>; Fri,  5 Oct 2012 06:28:57 -0700 (PDT)
X-AuditID: c1b4fb30-b7f7d6d0000042ea-05-506ee09854e8
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 97.FA.17130.890EE605; Fri,  5 Oct 2012 15:28:56 +0200 (CEST)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.99]) by esessmw0256.eemea.ericsson.se ([153.88.115.96]) with mapi; Fri, 5 Oct 2012 15:28:56 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "draft-ietf-sipcore-proxy-feature.all@tools.ietf.org" <draft-ietf-sipcore-proxy-feature.all@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>
Date: Fri, 5 Oct 2012 15:28:54 +0200
Thread-Topic: [Gen-art] Gen-ART telechat review of draft-ietf-sipcore-proxy-feature-11.txt
Thread-Index: Ac2i/Ts0koe4BXfrRLqgpEBKNSDFbwAABixg
Message-ID: <7F2072F1E0DE894DA4B517B93C6A0585340A7BD3F4@ESESSCMS0356.eemea.ericsson.se>
References: <506EE05C.1050608@gmail.com>
In-Reply-To: <506EE05C.1050608@gmail.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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrCLMWRmVeSWpSXmKPExsUyM+Jvre6MB3kBBmu/Sli0XdzHZDGpbw6b xdVXn1kcmD12zrrL7rFkyU8mjy+XP7MFMEdx2aSk5mSWpRbp2yVwZex8/IGt4ABLxdY939gb GDewdDFyckgImEhs7rzCBGGLSVy4t56ti5GLQ0jgFKNE+5otUM58RolDa34wdzFycLAJWEh0 /9MGiYsIXGaUeLiyGSzOIqAiMXdiEcggYYFoiUUNi1lBbBGBGImZTT+ZIGwjicOffoHFeQXC Jb5Oe8EMYgsJaEjce/iHHcTmFNCUaNm/DcxmBDro+6k1YL3MAuISt57MhzpUQGLJnvPMELao xMvH/1gh6kUl7rSvZwQ5hxlozvpd+hCtihJTuh+yQ6wVlDg58wnLBEbRWUimzkLomIWkYxaS jgWMLKsYhXMTM3PSy831Uosyk4uL8/P0ilM3MQJj5uCW3wY7GDfdFzvEKM3BoiTOq6e6319I ID2xJDU7NbUgtSi+qDQntfgQIxMHp1QDY+K0Y/6SMSF39Stzd/ydeetjgNLRtJmFz5+uK5Hb mHbl6KT7uvGdBruWHVy/JvE0e+nZP/c+LvmVNuFR7zoBnTMFL5ze8Ia9bVIpaNwoLsVqtECo 8LdCjX5hfKDzs/SXze8OT7twbP2sye+mb3H/l9eap16pwb276+XJFAPH4yWsGQv3FnLw7FRi Kc5INNRiLipOBAAoaEWVZwIAAA==
Subject: Re: [Gen-art] Gen-ART telechat review of	draft-ietf-sipcore-proxy-feature-11.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, 05 Oct 2012 13:28:59 -0000

VGhhbmsgWW91LCBCcmlhbiENCg0KUmVnYXJkcywNCg0KQ2hyaXN0ZXINCg0KLS0tLS1PcmlnaW5h
bCBNZXNzYWdlLS0tLS0NCkZyb206IGdlbi1hcnQtYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOmdl
bi1hcnQtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIEJyaWFuIEUgQ2FycGVudGVyDQpT
ZW50OiA1LiBsb2tha3V1dGEgMjAxMiAxNjoyOA0KVG86IGRyYWZ0LWlldGYtc2lwY29yZS1wcm94
eS1mZWF0dXJlLmFsbEB0b29scy5pZXRmLm9yZzsgR2VuZXJhbCBBcmVhIFJldmlldyBUZWFtDQpT
dWJqZWN0OiBbR2VuLWFydF0gR2VuLUFSVCB0ZWxlY2hhdCByZXZpZXcgb2YgZHJhZnQtaWV0Zi1z
aXBjb3JlLXByb3h5LWZlYXR1cmUtMTEudHh0DQoNClBsZWFzZSBzZWUgYXR0YWNoZWQgcmV2aWV3
Lg0KDQogICAgIEJyaWFuDQoNCg==

From jmh@joelhalpern.com  Fri Oct  5 08:15:00 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 B8C6121F869C; Fri,  5 Oct 2012 08:15:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.11
X-Spam-Level: 
X-Spam-Status: No, score=-102.11 tagged_above=-999 required=5 tests=[AWL=0.155, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mOdQdSLKZt31; Fri,  5 Oct 2012 08:14:59 -0700 (PDT)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 47DD221F872E; Fri,  5 Oct 2012 08:14:54 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by morbo.tigertech.net (Postfix) with ESMTP id DF12FA3830; Fri,  5 Oct 2012 08:14:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 50DC51C07FE; Fri,  5 Oct 2012 08:14:50 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [10.10.10.104] (pool-71-161-51-10.clppva.btas.verizon.net [71.161.51.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 42A131C0567; Fri,  5 Oct 2012 08:14:49 -0700 (PDT)
Message-ID: <506EF961.7040809@joelhalpern.com>
Date: Fri, 05 Oct 2012 11:14:41 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>
References: <506E0BD9.8050705@nostrum.com>
In-Reply-To: <506E0BD9.8050705@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "softwires@ietf.org" <softwires@ietf.org>, gen-art@ietf.org, Yong Cui <cuiyong@tsinghua.edu.cn>, draft-ietf-softwire-stateless-4v6-motivation@tools.ietf.org
Subject: [Gen-art] Review: draft-ietf-softwire-stateless-4v6-motivation-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, 05 Oct 2012 15:15:01 -0000

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

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

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

Document: draft-ietf-softwire-stateless-4v6-motivation-04
     Motivations for Carrier-side Stateless IPv4 over IPv6
         Migration Solutions
Reviewer: Joel M. Halpern
Review Date: 5-Oct-2012
IETF LC End Date: 17-Oct-2012
IESG Telechat date: 25-Oct-2012

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

Major issues:
     I may be misreading the first sub-paragraph in section 3.3.2.  It 
seems to assert that no ALGs are necessary with stateless 4v6 solution 
as "the payload of IPv4 packets is not altered in the path."  This seems 
to make very strong assumptions on the end host behavior, which are not 
called out in the document.

Minor issues:
     It is unfortunate that the elaborations on the motivations do not 
correlate with the initial list of those motivations.  They are not in 
the same order, and do not use the same titles.  This makes it harder 
for the reader who, after reading the base list, is looking for more 
explanation of item(i).

     The description of the anycast capability (Section 3 bullet 5 and 
section 3.2.1 first bullet) is very unclear.  Since packets are not 
addressed to the address translator, this reader is left confused as to 
what "anycast" capability is preserved by this and damaged by stateful 
NAT.  A few additional words in section 3.2.1 would be helpful.

     The issues raised in section 4 of the document ("Discussion") are 
interesting.  But they do not seem related to the motivation for seeking 
a stateless v4v6 solution.  They seem to be details of how such a 
solution might be built.  Why is this section in this document?

Nits/editorial comments:

From mohamed.boucadair@orange.com  Fri Oct  5 08:38:07 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 DB3AD21F8740; Fri,  5 Oct 2012 08:38:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.102
X-Spam-Level: 
X-Spam-Status: No, score=-2.102 tagged_above=-999 required=5 tests=[AWL=0.146,  BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uTtXvtNm-+SM; Fri,  5 Oct 2012 08:38:07 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 1389721F8731; Fri,  5 Oct 2012 08:38:06 -0700 (PDT)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id 4AEC83B4167; Fri,  5 Oct 2012 17:38:06 +0200 (CEST)
Received: from PUEXCH41.nanterre.francetelecom.fr (unknown [10.101.44.30]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id 2A6694C024; Fri,  5 Oct 2012 17:38:06 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.8]) by PUEXCH41.nanterre.francetelecom.fr ([10.101.44.30]) with mapi; Fri, 5 Oct 2012 17:38:06 +0200
From: <mohamed.boucadair@orange.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, "A. Jean Mahoney" <mahoney@nostrum.com>
Date: Fri, 5 Oct 2012 17:38:04 +0200
Thread-Topic: [Softwires] [Gen-art] Review: draft-ietf-softwire-stateless-4v6-motivation-04
Thread-Index: Ac2jDDsIoI58CP+fQG2/u1dH7nWQngAAKfUQ
Message-ID: <94C682931C08B048B7A8645303FDC9F36E5FA80A70@PUEXCB1B.nanterre.francetelecom.fr>
References: <506E0BD9.8050705@nostrum.com> <506EF961.7040809@joelhalpern.com>
In-Reply-To: <506EF961.7040809@joelhalpern.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.10.5.124533
Cc: "softwires@ietf.org" <softwires@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, Yong Cui <cuiyong@tsinghua.edu.cn>, "draft-ietf-softwire-stateless-4v6-motivation@tools.ietf.org" <draft-ietf-softwire-stateless-4v6-motivation@tools.ietf.org>
Subject: Re: [Gen-art] [Softwires] Review:	draft-ietf-softwire-stateless-4v6-motivation-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, 05 Oct 2012 15:38:08 -0000

Dear Joel,

Thank you for the review.=20

Please see inline.=20

Cheers,
Med=20

>-----Message d'origine-----
>De : softwires-bounces@ietf.org=20
>[mailto:softwires-bounces@ietf.org] De la part de Joel M. Halpern
>Envoy=E9 : vendredi 5 octobre 2012 17:15
>=C0 : A. Jean Mahoney
>Cc : softwires@ietf.org; gen-art@ietf.org; Yong Cui;=20
>draft-ietf-softwire-stateless-4v6-motivation@tools.ietf.org
>Objet : [Softwires] [Gen-art] Review:=20
>draft-ietf-softwire-stateless-4v6-motivation-04
>
>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-softwire-stateless-4v6-motivation-04
>     Motivations for Carrier-side Stateless IPv4 over IPv6
>         Migration Solutions
>Reviewer: Joel M. Halpern
>Review Date: 5-Oct-2012
>IETF LC End Date: 17-Oct-2012
>IESG Telechat date: 25-Oct-2012
>
>Summary: This document is nearly ready for publication as an=20
>Informational RFC.
>
>Major issues:
>     I may be misreading the first sub-paragraph in section 3.3.2.  It=20
>seems to assert that no ALGs are necessary with stateless 4v6 solution=20
>as "the payload of IPv4 packets is not altered in the path." =20
>This seems=20
>to make very strong assumptions on the end host behavior,=20
>which are not=20
>called out in the document.

Med: I guess you are referring to this text:=20

   Facilitates service evolution:  Since the payload of IPv4 packets is
      not altered in the path, services can evolve without requiring any
      specific function (e.g., Application Level Gateway (ALG)) in the
      Service Provider's network;

The host behaviour is the same as for deployments where no NAT is enabled i=
n the SP's network.=20

Could you please clarify what is the issue with that text?=20
Would it be better if I change "not altered in the path" with "not altered =
in Service Provider's network"?

>
>Minor issues:
>     It is unfortunate that the elaborations on the motivations do not=20
>correlate with the initial list of those motivations.  They are not in=20
>the same order, and do not use the same titles.  This makes it harder=20
>for the reader who, after reading the base list, is looking for more=20
>explanation of item(i).

Med: Point taken, I will see how to re-order the list to be aligned with th=
e sections/sub-sections ordering.

>
>     The description of the anycast capability (Section 3 bullet 5 and=20
>section 3.2.1 first bullet) is very unclear.  Since packets are not=20
>addressed to the address translator, this reader is left=20
>confused as to=20
>what "anycast" capability is preserved by this and damaged by stateful=20
>NAT.  A few additional words in section 3.2.1 would be helpful.

Med: What about this change?

OLD: "anycast-based schemes can be used for load-balancing and  redundancy =
purposes."
NEW: "anycast-based schemes can be used for load-balancing and redundancy p=
urposes between nodes embedding the Stateless IPv4/IPv6 interconnection fun=
ction."


>
>     The issues raised in section 4 of the document ("Discussion") are=20
>interesting.  But they do not seem related to the motivation=20
>for seeking=20
>a stateless v4v6 solution.  They seem to be details of how such a=20
>solution might be built.  Why is this section in this document?

Med: We added this section because we received comments asking for having a=
 section listing the main "limitations(?)" stateless solutions. It was a fa=
ir comment.

>
>Nits/editorial comments:
>_______________________________________________
>Softwires mailing list
>Softwires@ietf.org
>https://www.ietf.org/mailman/listinfo/softwires
>=

From jmh@joelhalpern.com  Fri Oct  5 08:52:35 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 9562F21F876F; Fri,  5 Oct 2012 08:52:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.115
X-Spam-Level: 
X-Spam-Status: No, score=-102.115 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qVtNSLbcXBl1; Fri,  5 Oct 2012 08:52:28 -0700 (PDT)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id AEF2521F8762; Fri,  5 Oct 2012 08:52:27 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by morbo.tigertech.net (Postfix) with ESMTP id 92F23557F8B; Fri,  5 Oct 2012 08:52:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 090A11BDB84F; Fri,  5 Oct 2012 08:52:26 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [10.10.10.104] (pool-71-161-51-10.clppva.btas.verizon.net [71.161.51.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id B16531BDB828; Fri,  5 Oct 2012 08:52:21 -0700 (PDT)
Message-ID: <506F022C.1040302@joelhalpern.com>
Date: Fri, 05 Oct 2012 11:52:12 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: mohamed.boucadair@orange.com
References: <506E0BD9.8050705@nostrum.com> <506EF961.7040809@joelhalpern.com> <94C682931C08B048B7A8645303FDC9F36E5FA80A70@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36E5FA80A70@PUEXCB1B.nanterre.francetelecom.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "softwires@ietf.org" <softwires@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, Yong Cui <cuiyong@tsinghua.edu.cn>, "draft-ietf-softwire-stateless-4v6-motivation@tools.ietf.org" <draft-ietf-softwire-stateless-4v6-motivation@tools.ietf.org>
Subject: Re: [Gen-art] [Softwires] Review: draft-ietf-softwire-stateless-4v6-motivation-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, 05 Oct 2012 15:52:35 -0000

Thank you for the prompt followup.

Taking things out of order, if the Discussion section were called 
Limitations, I would have understood why it was there.  It is not clear 
to me that the content actually describes limitations though.  It 
describes design choices that need to be made in specifying and 
deploying statelessv4v6 solutions.

On the packet preservation description text in section 3.3.2, I am not 
sure what assumptions the document makes.  For good and appropriate 
reasons, the document does not describe.  I believe tat the ability to 
avoid ALGs is dependent upon more specific choices of solution, beyond 
merely the stateless property.  Would it be acceptable to weaken the 
statement in the document to one that notes that stateless solutions 
admit the possibility of solutions which do not require ALGs?  And that 
such avoidance is highly desirable?

Yours,
Joel

On 10/5/2012 11:38 AM, mohamed.boucadair@orange.com wrote:
> Dear Joel,
>
> Thank you for the review.
>
> Please see inline.
>
> Cheers,
> Med
>
>> -----Message d'origine-----
>> De : softwires-bounces@ietf.org
>> [mailto:softwires-bounces@ietf.org] De la part de Joel M. Halpern
>> Envoyé : vendredi 5 octobre 2012 17:15
>> À : A. Jean Mahoney
>> Cc : softwires@ietf.org; gen-art@ietf.org; Yong Cui;
>> draft-ietf-softwire-stateless-4v6-motivation@tools.ietf.org
>> Objet : [Softwires] [Gen-art] Review:
>> draft-ietf-softwire-stateless-4v6-motivation-04
>>
>> 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-softwire-stateless-4v6-motivation-04
>>      Motivations for Carrier-side Stateless IPv4 over IPv6
>>          Migration Solutions
>> Reviewer: Joel M. Halpern
>> Review Date: 5-Oct-2012
>> IETF LC End Date: 17-Oct-2012
>> IESG Telechat date: 25-Oct-2012
>>
>> Summary: This document is nearly ready for publication as an
>> Informational RFC.
>>
>> Major issues:
>>      I may be misreading the first sub-paragraph in section 3.3.2.  It
>> seems to assert that no ALGs are necessary with stateless 4v6 solution
>> as "the payload of IPv4 packets is not altered in the path."
>> This seems
>> to make very strong assumptions on the end host behavior,
>> which are not
>> called out in the document.
>
> Med: I guess you are referring to this text:
>
>     Facilitates service evolution:  Since the payload of IPv4 packets is
>        not altered in the path, services can evolve without requiring any
>        specific function (e.g., Application Level Gateway (ALG)) in the
>        Service Provider's network;
>
> The host behaviour is the same as for deployments where no NAT is enabled in the SP's network.
>
> Could you please clarify what is the issue with that text?
> Would it be better if I change "not altered in the path" with "not altered in Service Provider's network"?
>
>>
>> Minor issues:
>>      It is unfortunate that the elaborations on the motivations do not
>> correlate with the initial list of those motivations.  They are not in
>> the same order, and do not use the same titles.  This makes it harder
>> for the reader who, after reading the base list, is looking for more
>> explanation of item(i).
>
> Med: Point taken, I will see how to re-order the list to be aligned with the sections/sub-sections ordering.
>
>>
>>      The description of the anycast capability (Section 3 bullet 5 and
>> section 3.2.1 first bullet) is very unclear.  Since packets are not
>> addressed to the address translator, this reader is left
>> confused as to
>> what "anycast" capability is preserved by this and damaged by stateful
>> NAT.  A few additional words in section 3.2.1 would be helpful.
>
> Med: What about this change?
>
> OLD: "anycast-based schemes can be used for load-balancing and  redundancy purposes."
> NEW: "anycast-based schemes can be used for load-balancing and redundancy purposes between nodes embedding the Stateless IPv4/IPv6 interconnection function."
>
>
>>
>>      The issues raised in section 4 of the document ("Discussion") are
>> interesting.  But they do not seem related to the motivation
>> for seeking
>> a stateless v4v6 solution.  They seem to be details of how such a
>> solution might be built.  Why is this section in this document?
>
> Med: We added this section because we received comments asking for having a section listing the main "limitations(?)" stateless solutions. It was a fair comment.
>
>>
>> Nits/editorial comments:
>> _______________________________________________
>> Softwires mailing list
>> Softwires@ietf.org
>> https://www.ietf.org/mailman/listinfo/softwires
>>

From jgs@juniper.net  Fri Oct  5 13:32:52 2012
Return-Path: <jgs@juniper.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8ED1C21F858F; Fri,  5 Oct 2012 13:32:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.352
X-Spam-Level: 
X-Spam-Status: No, score=-3.352 tagged_above=-999 required=5 tests=[AWL=-1.886, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, SARE_RAND_6=2, UNRESOLVED_TEMPLATE=3.132]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 53OXHBAxspQF; Fri,  5 Oct 2012 13:32:51 -0700 (PDT)
Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159]) by ietfa.amsl.com (Postfix) with ESMTP id 5B7CB21F8582; Fri,  5 Oct 2012 13:32:51 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob103.postini.com ([64.18.6.12]) with SMTP ID DSNKUG9D86hz7B3wH9Hw5CAmqOKjwvH8jglB@postini.com; Fri, 05 Oct 2012 13:32:51 PDT
Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 5 Oct 2012 13:31:15 -0700
Received: from o365mail.juniper.net (207.17.137.149) by o365mail.juniper.net (172.24.192.60) with Microsoft SMTP Server id 14.1.355.2; Fri, 5 Oct 2012 13:31:14 -0700
Received: from tx2outboundpool.messaging.microsoft.com (65.55.88.14) by o365mail.juniper.net (207.17.137.149) with Microsoft SMTP Server (TLS) id 14.1.355.2; Fri, 5 Oct 2012 13:33:02 -0700
Received: from mail170-tx2-R.bigfish.com (10.9.14.248) by TX2EHSOBE003.bigfish.com (10.9.40.23) with Microsoft SMTP Server id 14.1.225.23; Fri, 5 Oct 2012 20:31:10 +0000
Received: from mail170-tx2 (localhost [127.0.0.1])	by mail170-tx2-R.bigfish.com (Postfix) with ESMTP id BFD42600DD; Fri,  5 Oct 2012 20:31:10 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); (null); H:BL2PRD0510HT002.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -21
X-BigFish: PS-21(zz98dI9371Id6eah936eIc85dh1432Izz1202h1d1ah1d2ah1082kzz1033IL17326ah8275dhz2dh2a8h668h839hd25he5bhf0ah107ah1288h12a5h12bdh137ah139eh1441h1155h)
Received: from mail170-tx2 (localhost.localdomain [127.0.0.1]) by mail170-tx2 (MessageSwitch) id 1349469068666404_6305; Fri,  5 Oct 2012 20:31:08 +0000 (UTC)
Received: from TX2EHSMHS024.bigfish.com (unknown [10.9.14.249])	by mail170-tx2.bigfish.com (Postfix) with ESMTP id 9B4AB34007A; Fri,  5 Oct 2012 20:31:08 +0000 (UTC)
Received: from BL2PRD0510HT002.namprd05.prod.outlook.com (157.56.240.101) by TX2EHSMHS024.bigfish.com (10.9.99.124) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 5 Oct 2012 20:31:07 +0000
Received: from jgs-sslvpn-nc.jnpr.net (66.129.224.52) by pod51010.outlook.com (10.255.100.37) with Microsoft SMTP Server (TLS) id 14.16.207.9; Fri, 5 Oct 2012 20:31:05 +0000
Content-Type: multipart/alternative; boundary="Apple-Mail=_A23C14FB-A124-4C57-AA7C-9360D38C41D6"
MIME-Version: 1.0 (Mac OS X Mail 6.1 \(1498\))
From: John Scudder <jgs@juniper.net>
In-Reply-To: <CACvMsLG97q4Zvo-xQ=L_u6C_YCTAiTuOujFoyUsM1P+NY-prmA@mail.gmail.com>
Date: Fri, 5 Oct 2012 16:30:54 -0400
Message-ID: <2DEE274C-EDC7-4353-B8E7-A4CCEAF1A80E@juniper.net>
References: <CACvMsLG97q4Zvo-xQ=L_u6C_YCTAiTuOujFoyUsM1P+NY-prmA@mail.gmail.com>
To: Pete McCann <mccap@petoni.org>, Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1498)
X-Originating-IP: [66.129.224.52]
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%TOOLS.IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%PETONI.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%PSG.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
Cc: gen-art@ietf.org, draft-ietf-sidr-pfx-validate.all@tools.ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART Last Call Review of draft-ietf-sidr-pfx-validate-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Oct 2012 20:32:52 -0000

--Apple-Mail=_A23C14FB-A124-4C57-AA7C-9360D38C41D6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"

Pete,

Your Section 4 change looks fine to me, thanks.

The "monkey-in-the-middle" terminology is Randy's and I will defer to =
him. (I've added him to the To:)

--John

On Oct 1, 2012, at 6:56 PM, Pete McCann <mccap@petoni.org> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document:  draft-ietf-sidr-pfx-validate-09
> Reviewer:  Peter McCann
> Review Date:  2012-10-01
> IETF LC End Date:  2012-10-01
> IESG Telechat date: unknown
>=20
> Summary: Ready
>=20
> Major issues: None
>=20
> Minor issues:
>=20
> Section 4:
>    An "affected prefix" is any prefix that
>   was matched by a deleted or updated mapping, or could be matched by
>   an added mapping.
> SHOULD BE:
>   An "affected prefix" is any prefix that
>   was matched by a deleted or updated mapping, or could be matched by
>   an added or updated mapping.
>=20
> Nits/editorial comments:
>=20
> Abstract:
>   monkey-in-the-middle
> That's a game of keep-away.  Did you mean man-in-the-middle?  Perhaps
> this is a technical term that has been discussed on the mailing list.
>=20


--Apple-Mail=_A23C14FB-A124-4C57-AA7C-9360D38C41D6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="iso-8859-1"

<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-line-break: after-white-space; =
">Pete,<div><br></div><div>Your Section 4 change looks fine to me, =
thanks.</div><div><br></div><div>The "monkey-in-the-middle" terminology =
is Randy's and I will defer to him. (I've added him to the =
To:)</div><div><br></div><div>--John</div><div><br><div><div>On Oct 1, =
2012, at 6:56 PM, Pete McCann &lt;<a =
href=3D"mailto:mccap@petoni.org">mccap@petoni.org</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">I am the assigned Gen-ART reviewer for this draft. For =
background on<br>Gen-ART, please see the FAQ at<br><br>&lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://wi=
ki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<br><br>Please =
resolve these comments along with any other Last Call comments<br>you =
may receive.<br><br>Document: =
&nbsp;draft-ietf-sidr-pfx-validate-09<br>Reviewer: &nbsp;Peter =
McCann<br>Review Date: &nbsp;2012-10-01<br>IETF LC End Date: =
&nbsp;2012-10-01<br>IESG Telechat date: unknown<br><br>Summary: =
Ready<br><br>Major issues: None<br><br>Minor issues:<br><br>Section =
4:<br> &nbsp;&nbsp;&nbsp;An "affected prefix" is any prefix that<br> =
&nbsp;&nbsp;was matched by a deleted or updated mapping, or could be =
matched by<br> &nbsp;&nbsp;an added mapping.<br>SHOULD BE:<br> =
&nbsp;&nbsp;An "affected prefix" is any prefix that<br> &nbsp;&nbsp;was =
matched by a deleted or updated mapping, or could be matched by<br> =
&nbsp;&nbsp;an added or updated mapping.<br><br>Nits/editorial =
comments:<br><br>Abstract:<br> =
&nbsp;&nbsp;monkey-in-the-middle<br>That's a game of keep-away. =
&nbsp;Did you mean man-in-the-middle? &nbsp;Perhaps<br>this is a =
technical term that has been discussed on the mailing =
list.<br><br></blockquote></div><br></div></body></html>=

--Apple-Mail=_A23C14FB-A124-4C57-AA7C-9360D38C41D6--

From glenzorn@gmail.com  Sun Oct  7 00:28:20 2012
Return-Path: <glenzorn@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 859F921F84EC; Sun,  7 Oct 2012 00:28:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.949
X-Spam-Level: 
X-Spam-Status: No, score=-3.949 tagged_above=-999 required=5 tests=[AWL=-0.350, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QJeOIyN2wjX8; Sun,  7 Oct 2012 00:28:19 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 38A9F21F84EA; Sun,  7 Oct 2012 00:28:19 -0700 (PDT)
Received: by mail-pb0-f44.google.com with SMTP id ro8so3203714pbb.31 for <multiple recipients>; Sun, 07 Oct 2012 00:28:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=Xa6g5o0xcjFHO82Ht242m0ngBDIZSArp/jH6CIuiQ6A=; b=WQYq2mEvCOMWxbDQO3asOtatYVP9P3lw6+8kbX6o064bJzsDjVqQZZNXnEkKazhXKH i7ifP2wxhaK1wErNv3SV5xxpRB6QVsvHgrSMCfAKipZiEs0ww9ogmEZnMcdGXuavobpQ q4FrgiuL7FkqXq6Hc126Ro7tOiVsIU2jGPQTJRp81EOkP1RVDSvZjUw36Q4YE9aMzOQM tEREvFP/ZquvStaBwOaSM9XXmV3PwOiFxJrrxHFT/5sXcSLRi+Xs6oz/ymekMXSCWpEm urdxlG1jEOB++nm6OXkeBHd9tgRFqz47iAJamydyfJaBQIXQNehyETOtWaGIkva4iMBA 2kqg==
Received: by 10.68.234.7 with SMTP id ua7mr44345460pbc.91.1349594898753; Sun, 07 Oct 2012 00:28:18 -0700 (PDT)
Received: from [192.168.0.102] (ppp-115-87-90-243.revip4.asianet.co.th. [115.87.90.243]) by mx.google.com with ESMTPS id oi2sm7531203pbb.62.2012.10.07.00.28.15 (version=SSLv3 cipher=OTHER); Sun, 07 Oct 2012 00:28:18 -0700 (PDT)
Message-ID: <50712F0A.1050309@gmail.com>
Date: Sun, 07 Oct 2012 14:28:10 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120914 Thunderbird/15.0.1
MIME-Version: 1.0
To: "Black, David" <david.black@emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE7120DCD17FD@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7120DCD17FD@MX15A.corp.emc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-dime-rfc4005bis@tools.ietf.org" <draft-ietf-dime-rfc4005bis@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "lionel.morand@orange.com" <lionel.morand@orange.com>, Benoit Claise <bclaise@cisco.com>, "dime@ietf.org" <dime@ietf.org>, "glenzorn@gmail.com" <glenzorn@gmail.com>, "dime-chairs@tools.ietf.org" <dime-chairs@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-dime-rfc4005bis-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: Sun, 07 Oct 2012 07:28:20 -0000

On 09/18/2012 06:53 AM, Black, David 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-dime-rfc4005bis-11 Reviewer: David L. Black
 > Review Date: September 17, 2012 IETF LC End Date: September 18, 2012
 > IESG Telechat date: (if known)
 >
 > Summary:
 >
 > This draft is on the right track but has open issues, described in
 > the review.
 >
 > This draft is part of a set of drafts that updates the DIAMETER
 > protocol; this draft specifies the application of DIAMETER to AAA for
 > network access. The draft is heavily based on RFC 4005, which it
 > obsoletes, and requires significant DIAMETER familiarity (including
 > familiarity with its companion drafts, starting with the rfc3588bis
 > draft) for complete understanding.
 >
 > The draft is in good shape and reads well. I found one major open
 > issue, a few minor issues, and several nits.
 >
 > Major issues:
 >
 > This draft makes significant use of UTF-8 in its formats (some
 > subsections of sections 4.2, 4.4 and 4.5) for strings that are
 > intended to be compared for equality or processed by protocol
 > participants, but does not contain considerations for Unicode
 > processing that are sufficient to support this usage. Examples of
 > UTF-8 usage in this draft include:
 >
 > - 4.2.5 and 4.2.6: The NAS server may perform authorization based on
 > the Called-Station-Id and Calling-Station-Id AVPs under some
 > circumstances. - 4.4.3: The Callback-Id AVP is intended to be
 > interpreted by the NAS.
 >
 > All use of UTF-8 in this draft relies upon the specification of the
 > UTF8String format in the rfc3588bis draft. That specification is
 > insufficient to support the usage in the above examples, and there
 > are no Unicode considerations in this draft. Even binary comparison
 > of Unicode strings for equality generally requires specification of
 > string preparation (e.g., normalization) in order for string
 > comparison to work as expected.
 >
 > The variety of Unicode strings in this draft makes it important to
 > lay out the Unicode requirements and considerations for each AVP. I
 > see at least 5 classes of possible Unicode
 > requirements/considerations:
 >
 > 1) String preparation so that tests for equality work as expected.
 > This may suffice for the Called-Station-ID AVP (4.2.5) and
 > Calling-Station-ID AVP (4.2.6) if the internal structure of those
 > strings is not used in authorization.

Both those AVPs are specified to contain ASCII encoded as UTF-8.  Is 
string preparation necessary in that case?

> 2) Detailed string format for a
 > string that is processed by a protocol participant, e.g., the
 > Callback-ID AVP (4.4.3).

That format is unknown in this case.
...
> 5) Statement that the string  contains an FQDN, as stated for one case of
 > the Tunnel-Client-Endpoint AVP in 4.5.4. That specific statement is
 > incomplete, as it needs to be accompanied by a normative reference to
 > a document that specifies the format of internationalized domain
 > names, and probably needs to also state which types of labels (e.g.,
 > A-label, U-label) are allowed.
 >
 > Every use of UTF8String in this draft needs to be checked, and most
 > of them are likely to need some attention. The ongoing work in the
 > precis WG may help with some of this, and I would suggest talking to
 > the APP ADs, especially Pete Resnick (hi Pete) before embarking on
 > significant work in this area in order to avoid wasted or duplicated
 > efforts.

OK, this last one bothers me a lot: you /seem /to be suggesting that we 
hold up this draft to wait for the result of a WG which has yet to 
publish a problem statement.  I'm sure that that is not the case, but it 
sure sounds like it.

>
 > Minor Issues:
 >
 > [1] End of Section 2 on p.8:
 >
 > As a result, service cannot be started as a result of a response to
 > an authorization-only request without introducing a significant
 > security vulnerability.
 >
 > Please explain what to do about this - a simple rewrite with a
 > "SHOULD NOT" would suffice, e.g.:
 >
 > As a result, service SHOULD NOT be started as a result of a response
 > to an authorization-only request because that may introduce a
 > significant security vulnerability.

The text in question is descriptive, not prescriptive.at said, however, 
I think that it's not really clear.  I think that it should say 
something like "As a result, a new session cannot be started as a result 
of a response to an authorization-only request without introducing a 
significant security vulnerability."

>
 > This should also be noted in the Security Considerations section.
 >
 > [2] In the message formats in Section 3, QoS-Filter-Rule is
 > inconsistently capitalized.

OK, thanks.

> Also the use of QoSFilterRule  as the
 > format for the QoS-Filter-Rule AVP in Section 4.1.1 is potentially
 > confusing. Please add a sentence in 4.1.1 to say that QoSFilterRule
 > is the format for the QoS-Filter-Rule AVP.
 >
 > [3] Section 4.2.1. In this and the other AVP Flag Rules tables,
 > please explain what the values in the MUST and MUST NOT columns
 > mean.
 >
 > [4] Based on this text in 4.4.9:
 >
 > The use of this AVP is NOT RECOMMENDED; the AVPs defined by
 > Korhonen, et al. [RFC5777] SHOULD be used instead.
 >
 > I would have expected RFC5777 to be a Normative Reference, not an
 > Informative Reference.

I don't care particularly, but I don't think that it's really necessary 
to understand RFC 5777 to understand this document.

>
 > Nits/editorial comments:
 >
 > After the command table in Section 3 and other similar tables, please
 > add a sentence to say that the -Request and -Answer commands in each
 > similarly-named command pair are distinguished by the value of the
 > 'R' bit in the Command Flags field of the command. This is already
 > stated in the command definitions, but the sentence should be added
 > after the table for clarity because each command pair shares a
 > Command Code.
 >
 > idnits 2.12.13 found a few potential nits:
 >
 > == There are 7 instances of lines with non-RFC5735-compliant IPv4
 > addresses in the document. If these are example addresses, they
 > should be changed.
 >
 > That can probably be ignored, as these instances are likely generated
 > by text such as cross-references to Section 4.4.10.1
 >
 > == Missing Reference: 'BASE' is mentioned on line 219, but not
 > defined
 >
 > That's definitely a problem. Was [I-D.ietf-dime-rfc3588bis]
 > intended?

No.  The passage in question is a verbatim quote from RFC 4005.

>
 > -- Possible downref: Non-RFC (?) normative reference: ref.
 > 'ANITypes'
 >
 > That reference would be:
 >
 > [ANITypes] NANPA Number Resource Info, "ANI Assignments",
 > <http://www.nanpa.com/ number_resource_info/
 > ani_ii_assignments.html>.
 >
 > Is that reference sufficiently stable (e.g., IANA-class or better
 > management)?

Yes, I think so.

> My guess is that it is  sufficiently stable, but I'm not
 > the expert.
>
 > -- Obsolete informational reference (is this intentional?): RFC 1334
 > (Obsoleted by RFC 1994)
 >
 > That reference may be intentional,

Yes.

...

From mohamed.boucadair@orange.com  Sun Oct  7 23:13:08 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 D11FE21F8701; Sun,  7 Oct 2012 23:13:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level: 
X-Spam-Status: No, score=-2.105 tagged_above=-999 required=5 tests=[AWL=0.143,  BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4uRKKt5kCUHx; Sun,  7 Oct 2012 23:13:07 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 98E0621F86DC; Sun,  7 Oct 2012 23:13:07 -0700 (PDT)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm14.si.francetelecom.fr (ESMTP service) with ESMTP id 3302822C35E; Mon,  8 Oct 2012 08:13:06 +0200 (CEST)
Received: from PUEXCH51.nanterre.francetelecom.fr (unknown [10.101.44.31]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id 119374C015; Mon,  8 Oct 2012 08:13:06 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.8]) by PUEXCH51.nanterre.francetelecom.fr ([10.101.44.31]) with mapi; Mon, 8 Oct 2012 08:13:05 +0200
From: <mohamed.boucadair@orange.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Date: Mon, 8 Oct 2012 08:13:04 +0200
Thread-Topic: [Softwires] [Gen-art] Review: draft-ietf-softwire-stateless-4v6-motivation-04
Thread-Index: Ac2jEWzshgS5iV3HSkeKfqjMXQebCwCBoGLA
Message-ID: <94C682931C08B048B7A8645303FDC9F36E6174562C@PUEXCB1B.nanterre.francetelecom.fr>
References: <506E0BD9.8050705@nostrum.com> <506EF961.7040809@joelhalpern.com> <94C682931C08B048B7A8645303FDC9F36E5FA80A70@PUEXCB1B.nanterre.francetelecom.fr> <506F022C.1040302@joelhalpern.com>
In-Reply-To: <506F022C.1040302@joelhalpern.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.10.8.50339
Cc: "softwires@ietf.org" <softwires@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, Yong Cui <cuiyong@tsinghua.edu.cn>, "draft-ietf-softwire-stateless-4v6-motivation@tools.ietf.org" <draft-ietf-softwire-stateless-4v6-motivation@tools.ietf.org>
Subject: Re: [Gen-art] [Softwires] Review: draft-ietf-softwire-stateless-4v6-motivation-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, 08 Oct 2012 06:13:09 -0000

Dear Joel,

Please see inline.

Cheers,
Med=20

>-----Message d'origine-----
>De : Joel M. Halpern [mailto:jmh@joelhalpern.com]=20
>Envoy=E9 : vendredi 5 octobre 2012 17:52
>=C0 : BOUCADAIR Mohamed OLNC/OLN
>Cc : A. Jean Mahoney; softwires@ietf.org; gen-art@ietf.org;=20
>Yong Cui; draft-ietf-softwire-stateless-4v6-motivation@tools.ietf.org
>Objet : Re: [Softwires] [Gen-art] Review:=20
>draft-ietf-softwire-stateless-4v6-motivation-04
>
>Thank you for the prompt followup.
>
>Taking things out of order, if the Discussion section were called=20
>Limitations, I would have understood why it was there.  It is=20
>not clear=20
>to me that the content actually describes limitations though.  It=20
>describes design choices that need to be made in specifying and=20
>deploying statelessv4v6 solutions.

Med: The points listed in that section are usually presented as limitations=
 of the solution. If you noticed I said in my first answer "limitations(?)"=
 because I disagree those points were limitations but rather open questions=
 which depend on the design choices.=20

>
>On the packet preservation description text in section 3.3.2, I am not=20
>sure what assumptions the document makes.  For good and appropriate=20
>reasons, the document does not describe.  I believe tat the ability to=20
>avoid ALGs is dependent upon more specific choices of solution, beyond=20
>merely the stateless property. =20
Would it be acceptable to weaken the=20
>statement in the document to one that notes that stateless solutions=20
>admit the possibility of solutions which do not require ALGs? =20
>And that=20
>such avoidance is highly desirable?

Med: Below a text proposal:=20

OLD:

   Facilitates service evolution:  Since the payload of IPv4 packets is
      not altered in the path, services can evolve without requiring any
      specific function (e.g., Application Level Gateway (ALG)) in the
      Service Provider's network;

NEW:

   Facilitates service evolution:  Stateless solutions admit
      applications can be deployed without enabling any application-
      specific function (e.g., Application Level Gateway (ALG)) in the
      Service Provider's network.  Avoiding ALGs is highly desirable.

Better?

>
>Yours,
>Joel
>
>On 10/5/2012 11:38 AM, mohamed.boucadair@orange.com wrote:
>> Dear Joel,
>>
>> Thank you for the review.
>>
>> Please see inline.
>>
>> Cheers,
>> Med
>>
>>> -----Message d'origine-----
>>> De : softwires-bounces@ietf.org
>>> [mailto:softwires-bounces@ietf.org] De la part de Joel M. Halpern
>>> Envoy=E9 : vendredi 5 octobre 2012 17:15
>>> =C0 : A. Jean Mahoney
>>> Cc : softwires@ietf.org; gen-art@ietf.org; Yong Cui;
>>> draft-ietf-softwire-stateless-4v6-motivation@tools.ietf.org
>>> Objet : [Softwires] [Gen-art] Review:
>>> draft-ietf-softwire-stateless-4v6-motivation-04
>>>
>>> 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=20
>Call comments
>>> you may receive.
>>>
>>> Document: draft-ietf-softwire-stateless-4v6-motivation-04
>>>      Motivations for Carrier-side Stateless IPv4 over IPv6
>>>          Migration Solutions
>>> Reviewer: Joel M. Halpern
>>> Review Date: 5-Oct-2012
>>> IETF LC End Date: 17-Oct-2012
>>> IESG Telechat date: 25-Oct-2012
>>>
>>> Summary: This document is nearly ready for publication as an
>>> Informational RFC.
>>>
>>> Major issues:
>>>      I may be misreading the first sub-paragraph in section=20
>3.3.2.  It
>>> seems to assert that no ALGs are necessary with stateless=20
>4v6 solution
>>> as "the payload of IPv4 packets is not altered in the path."
>>> This seems
>>> to make very strong assumptions on the end host behavior,
>>> which are not
>>> called out in the document.
>>
>> Med: I guess you are referring to this text:
>>
>>     Facilitates service evolution:  Since the payload of=20
>IPv4 packets is
>>        not altered in the path, services can evolve without=20
>requiring any
>>        specific function (e.g., Application Level Gateway=20
>(ALG)) in the
>>        Service Provider's network;
>>
>> The host behaviour is the same as for deployments where no=20
>NAT is enabled in the SP's network.
>>
>> Could you please clarify what is the issue with that text?
>> Would it be better if I change "not altered in the path"=20
>with "not altered in Service Provider's network"?
>>
>>>
>>> Minor issues:
>>>      It is unfortunate that the elaborations on the=20
>motivations do not
>>> correlate with the initial list of those motivations.  They=20
>are not in
>>> the same order, and do not use the same titles.  This makes=20
>it harder
>>> for the reader who, after reading the base list, is looking for more
>>> explanation of item(i).
>>
>> Med: Point taken, I will see how to re-order the list to be=20
>aligned with the sections/sub-sections ordering.
>>
>>>
>>>      The description of the anycast capability (Section 3=20
>bullet 5 and
>>> section 3.2.1 first bullet) is very unclear.  Since packets are not
>>> addressed to the address translator, this reader is left
>>> confused as to
>>> what "anycast" capability is preserved by this and damaged=20
>by stateful
>>> NAT.  A few additional words in section 3.2.1 would be helpful.
>>
>> Med: What about this change?
>>
>> OLD: "anycast-based schemes can be used for load-balancing=20
>and  redundancy purposes."
>> NEW: "anycast-based schemes can be used for load-balancing=20
>and redundancy purposes between nodes embedding the Stateless=20
>IPv4/IPv6 interconnection function."
>>
>>
>>>
>>>      The issues raised in section 4 of the document=20
>("Discussion") are
>>> interesting.  But they do not seem related to the motivation
>>> for seeking
>>> a stateless v4v6 solution.  They seem to be details of how such a
>>> solution might be built.  Why is this section in this document?
>>
>> Med: We added this section because we received comments=20
>asking for having a section listing the main "limitations(?)"=20
>stateless solutions. It was a fair comment.
>>
>>>
>>> Nits/editorial comments:
>>> _______________________________________________
>>> Softwires mailing list
>>> Softwires@ietf.org
>>> https://www.ietf.org/mailman/listinfo/softwires
>>>
>=

From julian.reschke@gmx.de  Mon Oct  8 04:45:58 2012
Return-Path: <julian.reschke@gmx.de>
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 6983721F86C2 for <gen-art@ietfa.amsl.com>; Mon,  8 Oct 2012 04:45:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.403
X-Spam-Level: 
X-Spam-Status: No, score=-103.403 tagged_above=-999 required=5 tests=[AWL=-0.804, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YGS8jXesG1kR for <gen-art@ietfa.amsl.com>; Mon,  8 Oct 2012 04:45:58 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 75A2221F86B2 for <gen-art@ietf.org>; Mon,  8 Oct 2012 04:45:57 -0700 (PDT)
Received: (qmail invoked by alias); 08 Oct 2012 11:45:56 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp016) with SMTP; 08 Oct 2012 13:45:56 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18K+ktyY/AKDk6Dy+Oy58N6mIg4K9eZCi5K69hR+U nsQTr8XL7fv4tE
Message-ID: <5072BCEE.60807@gmx.de>
Date: Mon, 08 Oct 2012 13:45:50 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>
References: <4E1F6AAD24975D4BA5B16804296739436673769B@TK5EX14MBXC285.redmond.corp.microsoft.com> <5006A010.60408@isode.com>
In-Reply-To: <5006A010.60408@isode.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: Mike Jones <Michael.Jones@microsoft.com>, "oauth@ietf.org" <oauth@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>, The IESG <iesg@ietf.org>
Subject: Re: [Gen-art] [OAUTH-WG] Gen-ART Telechat review of draft-ietf-oauth-v2-bearer-22.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, 08 Oct 2012 11:45:58 -0000

On 2012-07-18 13:37, Alexey Melnikov wrote:
> On 17/07/2012 19:01, Mike Jones wrote:
>> You should actually probably make that name change request to the
>> HTTPbis working group.  I suspect that if they decide to change the
>> name, that we could direct the RFC editor to make the same name change
>> as HTTPbis does.
> It looks like the discussion of changing this in HTTPBIS is in progress
> now.

We made that change in HTTPbis, but bearer still seems to use 
"b64token". Can this be fixed in AUTH48???

Best regards, Julian


From barryleiba.mailing.lists@gmail.com  Mon Oct  8 10:16:53 2012
Return-Path: <barryleiba.mailing.lists@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 A95A221F87E8; Mon,  8 Oct 2012 10:16:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.1
X-Spam-Level: 
X-Spam-Status: No, score=-103.1 tagged_above=-999 required=5 tests=[AWL=-0.123, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AJAnkpc3SQYu; Mon,  8 Oct 2012 10:16:53 -0700 (PDT)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2F40321F87E4; Mon,  8 Oct 2012 10:16:52 -0700 (PDT)
Received: by mail-la0-f44.google.com with SMTP id b11so2672668lam.31 for <multiple recipients>; Mon, 08 Oct 2012 10:16:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=DvWnnNe9gwL58ZzSLvx2fDmeW+DHgNZyJ/zBR0qrcC4=; b=QrXTvh35QLhsYKEBrjTZh4RDJzid44fLvgjKFa34yj45VcCiCeXDkbuSUiFg2mLJCk OQ5GFGmeG4PScRu/C8O8eHvqmOPg/WgIbQtGZxiXCn2dao6DRu6RXM22WUE49aoS/3qK 3289cay5RWysjlh7EPRbWalnELv1VDJrauDsqIKCZzeqKkfDghrPkOVgHkXkNSlCs2bs 6FEXGo0piv0Ck4XFtmYrgpKaAwsMYpE0A2Qrc/v1LTQvkC/TceSp7xkfRowLT5ibibHp eGhux1LMDU3XPWQhE3OfOuRgzX52KESDck9k9ZuIuLasTNlMF1WVFp77/IyXzcw4SSKe mjTQ==
MIME-Version: 1.0
Received: by 10.112.101.133 with SMTP id fg5mr2771608lbb.3.1349716611100; Mon, 08 Oct 2012 10:16:51 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.150.194 with HTTP; Mon, 8 Oct 2012 10:16:50 -0700 (PDT)
In-Reply-To: <50712F0A.1050309@gmail.com>
References: <8D3D17ACE214DC429325B2B98F3AE7120DCD17FD@MX15A.corp.emc.com> <50712F0A.1050309@gmail.com>
Date: Mon, 8 Oct 2012 13:16:50 -0400
X-Google-Sender-Auth: kuSWlw21NSFpLbLwLkm8lk1x1sk
Message-ID: <CAC4RtVDDBo+kVJMpS+j1sCHy_qtn0FzLkrpzqysPZTaPTHpm1w@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Glen Zorn <glenzorn@gmail.com>, precis-chairs@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: "ietf@ietf.org" <ietf@ietf.org>, "lionel.morand@orange.com" <lionel.morand@orange.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-dime-rfc4005bis@tools.ietf.org" <draft-ietf-dime-rfc4005bis@tools.ietf.org>, "dime@ietf.org" <dime@ietf.org>, "dime-chairs@tools.ietf.org" <dime-chairs@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-dime-rfc4005bis-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Oct 2012 17:16:53 -0000

>> 5) Statement that the string  contains an FQDN, as stated for one case of
>> the Tunnel-Client-Endpoint AVP in 4.5.4. That specific statement is
>> incomplete, as it needs to be accompanied by a normative reference to
>> a document that specifies the format of internationalized domain
>> names, and probably needs to also state which types of labels (e.g.,
>> A-label, U-label) are allowed.
>>
>> Every use of UTF8String in this draft needs to be checked, and most
>> of them are likely to need some attention. The ongoing work in the
>> precis WG may help with some of this, and I would suggest talking to
>> the APP ADs, especially Pete Resnick (hi Pete) before embarking on
>> significant work in this area in order to avoid wasted or duplicated
>> efforts.
>
> OK, this last one bothers me a lot: you /seem /to be suggesting that we hold
> up this draft to wait for the result of a WG which has yet to publish a
> problem statement.  I'm sure that that is not the case, but it sure sounds
> like it.

David can clarify if I'm wrong, but that's not what it sounds like to
me.  What it sounds like he's suggesting is that you talk with the
precis people to see if things are OK, or if there's anything you
should be doing differently.  I'm adding the precis chairs to this
message, and asking them to respond to this point.


A tangential point, while I'm here:

>> [4] Based on this text in 4.4.9:
>> The use of this AVP is NOT RECOMMENDED; the AVPs defined by
>> Korhonen, et al. [RFC5777] SHOULD be used instead.
>>
>> I would have expected RFC5777 to be a Normative Reference, not an
>> Informative Reference.
>
> I don't care particularly, but I don't think that it's really necessary to
> understand RFC 5777 to understand this document.

It would seem odd, in general, if something that's a "MUST implement"
or "SHOULD implement" weren't a normative reference.  But I haven't
(yet) looked at this particular case to see.

Barry

From rbarnes@bbn.com  Mon Oct  8 11:17:05 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 796F21F041C; Mon,  8 Oct 2012 11:17:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.424
X-Spam-Level: 
X-Spam-Status: No, score=-106.424 tagged_above=-999 required=5 tests=[AWL=-0.084, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Z=0.259, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2wqGELZS1zUv; Mon,  8 Oct 2012 11:17:04 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id 977E71F0381; Mon,  8 Oct 2012 11:17:04 -0700 (PDT)
Received: from [128.89.253.160] (port=60951) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1TLHst-000Da3-Vl; Mon, 08 Oct 2012 14:16:56 -0400
From: Richard Barnes <rbarnes@bbn.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Mon, 8 Oct 2012 14:16:55 -0400
Message-Id: <AFA53290-369B-43EA-93B5-D14273B8A9A7@bbn.com>
To: IETF discussion list <ietf@ietf.org>, IESG IESG <iesg@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1283)
X-Mailer: Apple Mail (2.1283)
Cc: gen-art@ietf.org, draft-ietf-6man-udpzero@tools.ietf.org
Subject: [Gen-art] Gen-ART telechat review of draft-ietf-6man-udpzero-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: Mon, 08 Oct 2012 18:17: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 =
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-6man-udpzero-06
Reviewer: Richard Barnes
Review Date: 2012-10-08
IETF LC End Date: 2012-10-02
IESG Telechat date: 2012-10-11

Summary:  Ready

Comment:

In general, the document is well-written and seems to cover the relevant =
considerations well.  I agree with Barry's DISCUSS that the restrictions =
in Section 5.1 should be general to all usages of UDP zero checksums, =
and not specific to tunnels.=

From david.black@emc.com  Mon Oct  8 13:11:56 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 A918E21F87F9; Mon,  8 Oct 2012 13:11:56 -0700 (PDT)
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=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x26clcZ4oPbd; Mon,  8 Oct 2012 13:11:56 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id BA61821F8702; Mon,  8 Oct 2012 13:11:55 -0700 (PDT)
Received: from hop04-l1d11-si04.isus.emc.com (HOP04-L1D11-SI04.isus.emc.com [10.254.111.24]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q98KBlHj021251 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Oct 2012 16:11:48 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.145]) by hop04-l1d11-si04.isus.emc.com (RSA Interceptor); Mon, 8 Oct 2012 16:11:43 -0400
Received: from mxhub24.corp.emc.com (mxhub24.corp.emc.com [128.222.70.136]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q98KBeoH030012; Mon, 8 Oct 2012 16:11:41 -0400
Received: from mx15a.corp.emc.com ([169.254.1.83]) by mxhub24.corp.emc.com ([128.222.70.136]) with mapi; Mon, 8 Oct 2012 16:11:41 -0400
From: "Black, David" <david.black@emc.com>
To: Barry Leiba <barryleiba@computer.org>, Glen Zorn <glenzorn@gmail.com>, "precis-chairs@tools.ietf.org" <precis-chairs@tools.ietf.org>
Date: Mon, 8 Oct 2012 16:11:39 -0400
Thread-Topic: Gen-ART review of draft-ietf-dime-rfc4005bis-11
Thread-Index: Ac2leMQ+3QDh/2XtR/iDfUkrQqimgwAFfE4Q
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7120DF11C12@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE7120DCD17FD@MX15A.corp.emc.com> <50712F0A.1050309@gmail.com> <CAC4RtVDDBo+kVJMpS+j1sCHy_qtn0FzLkrpzqysPZTaPTHpm1w@mail.gmail.com>
In-Reply-To: <CAC4RtVDDBo+kVJMpS+j1sCHy_qtn0FzLkrpzqysPZTaPTHpm1w@mail.gmail.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: "dime-chairs@tools.ietf.org" <dime-chairs@tools.ietf.org>, "lionel.morand@orange.com" <lionel.morand@orange.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-dime-rfc4005bis@tools.ietf.org" <draft-ietf-dime-rfc4005bis@tools.ietf.org>, "dime@ietf.org" <dime@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-dime-rfc4005bis-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Oct 2012 20:11:56 -0000

Barry,

> >> 5) Statement that the string contains an FQDN, as stated for one case =
of
> >> the Tunnel-Client-Endpoint AVP in 4.5.4. That specific statement is
> >> incomplete, as it needs to be accompanied by a normative reference to
> >> a document that specifies the format of internationalized domain
> >> names, and probably needs to also state which types of labels (e.g.,
> >> A-label, U-label) are allowed.
> >>
> >> Every use of UTF8String in this draft needs to be checked, and most
> >> of them are likely to need some attention. The ongoing work in the
> >> precis WG may help with some of this, and I would suggest talking to
> >> the APP ADs, especially Pete Resnick (hi Pete) before embarking on
> >> significant work in this area in order to avoid wasted or duplicated
> >> efforts.
> >
> > OK, this last one bothers me a lot: you /seem /to be suggesting that we=
 hold
> > up this draft to wait for the result of a WG which has yet to publish a
> > problem statement.  I'm sure that that is not the case, but it sure sou=
nds
> > like it.
>=20
> David can clarify if I'm wrong, but that's not what it sounds like to
> me.  What it sounds like he's suggesting is that you talk with the
> precis people to see if things are OK, or if there's anything you
> should be doing differently.  I'm adding the precis chairs to this
> message, and asking them to respond to this point.

It's somewhere in between, as things are definitely *not* OK at the moment,
but my reason for suggesting a discussion with the pr=E9cis folks is to tak=
e
advantage of their insights and work to date.  If I thought this draft need=
ed
to wait for the output of the pr=E9cis WG, I would have indicated which pr=
=E9cis
draft ought to be a normative reference (and I did not do that).  Whether
that's a good idea will only be clear after every use of UTF8String is chec=
ked.

FWIW, the FQDN situation is worked out, start with a normative reference to
RFC 5890, which includes the specification of the various label types.

> A tangential point, while I'm here:
>=20
> >> [4] Based on this text in 4.4.9:
> >> The use of this AVP is NOT RECOMMENDED; the AVPs defined by
> >> Korhonen, et al. [RFC5777] SHOULD be used instead.
> >>
> >> I would have expected RFC5777 to be a Normative Reference, not an
> >> Informative Reference.
> >
> > I don't care particularly, but I don't think that it's really necessary=
 to
> > understand RFC 5777 to understand this document.
>=20
> It would seem odd, in general, if something that's a "MUST implement"
> or "SHOULD implement" weren't a normative reference.  But I haven't
> (yet) looked at this particular case to see.

My expectation is the same - if [RFCxxxx] is specified as "MUST implement"
or "SHOULD implement", then I usually expect that RFC to be a normative
reference.

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 david.black@emc.com  Mon Oct  8 13:53:17 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 EBEA011E80F1; Mon,  8 Oct 2012 13:53:17 -0700 (PDT)
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=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cPELdoa54pNm; Mon,  8 Oct 2012 13:53:16 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id AF71A11E80F0; Mon,  8 Oct 2012 13:53:16 -0700 (PDT)
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 q98KrEHS006683 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Oct 2012 16:53:14 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.130]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Mon, 8 Oct 2012 16:52:59 -0400
Received: from mxhub16.corp.emc.com (mxhub16.corp.emc.com [128.222.70.237]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q98KqwFY017595; Mon, 8 Oct 2012 16:52:58 -0400
Received: from mx15a.corp.emc.com ([169.254.1.83]) by mxhub16.corp.emc.com ([128.222.70.237]) with mapi; Mon, 8 Oct 2012 16:52:58 -0400
From: "Black, David" <david.black@emc.com>
To: Glen Zorn <glenzorn@gmail.com>
Date: Mon, 8 Oct 2012 16:52:56 -0400
Thread-Topic: Gen-ART review of draft-ietf-dime-rfc4005bis-11
Thread-Index: Ac2kXoeQSUAX8En/RPGw5bTX7IkshwBMzE7Q
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7120DF11C25@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE7120DCD17FD@MX15A.corp.emc.com> <50712F0A.1050309@gmail.com>
In-Reply-To: <50712F0A.1050309@gmail.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: "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-dime-rfc4005bis@tools.ietf.org" <draft-ietf-dime-rfc4005bis@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "lionel.morand@orange.com" <lionel.morand@orange.com>, "dime@ietf.org" <dime@ietf.org>, Benoit Claise <bclaise@cisco.com>, "dime-chairs@tools.ietf.org" <dime-chairs@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-dime-rfc4005bis-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Oct 2012 20:53:18 -0000

Glen,

Picking up the topics that weren't in Barry's email ...

>  > 1) String preparation so that tests for equality work as expected.
>  > This may suffice for the Called-Station-ID AVP (4.2.5) and
>  > Calling-Station-ID AVP (4.2.6) if the internal structure of those
>  > strings is not used in authorization.
>=20
> Both those AVPs are specified to contain ASCII encoded as UTF-8.  Is
> string preparation necessary in that case?

Not in the full glory that is needed for serious usage of UTF-8, but
it looks like the language in the draft should be tightened.  At a
minimum, a "MUST" is in order to require use of 7-bit ASCII encoded
as UTF-8.  Among the reasons for such a requirement is to prohibit the
various ISO/IEC 8859-* character sets (a/k/a Latin-*), which are
8-bit ASCII and not distinguishable from each other on the wire
without an additional character set tag of some form.

I would also suggest forbidding control characters (e.g., require
displayable 7-bit ASCII characters) and saying something about case
handling, starting with whether the strings are case sensitive or case
insensitive.  Case sensitivity is simpler to specify, but may not yield
intuitive and/or expected results.  If the strings are case insensitive,
text should be added to say whether the strings are case-normalized on
the wire and/or whether the recipient is expected to implement case-
insensitive string comparison.

> > 2) Detailed string format for a
>  > string that is processed by a protocol participant, e.g., the
>  > Callback-ID AVP (4.4.3).
>=20
> That format is unknown in this case.

Please explain how that's supposed to result in interoperable processing
by the "protocol participant".

>  > [1] End of Section 2 on p.8:
>  >
>  > As a result, service cannot be started as a result of a response to
>  > an authorization-only request without introducing a significant
>  > security vulnerability.
>  >
>  > Please explain what to do about this - a simple rewrite with a
>  > "SHOULD NOT" would suffice, e.g.:
>  >
>  > As a result, service SHOULD NOT be started as a result of a response
>  > to an authorization-only request because that may introduce a
>  > significant security vulnerability.
>=20
> The text in question is descriptive, not prescriptive. That said, however=
,
> I think that it's not really clear.  I think that it should say
> something like "As a result, a new session cannot be started as a result
> of a response to an authorization-only request without introducing a
> significant security vulnerability."
>=20
> >
>  > This should also be noted in the Security Considerations section.

The rewrite helps, and make sure to add text about this in the Security
Considerations section.

>  > =3D=3D Missing Reference: 'BASE' is mentioned on line 219, but not
>  > defined
>  >
>  > That's definitely a problem. Was [I-D.ietf-dime-rfc3588bis]
>  > intended?
>=20
> No.  The passage in question is a verbatim quote from RFC 4005.

Ok, just fix this so idnits can find something else to complain about :-).

Thanks,
--David

> -----Original Message-----
> From: Glen Zorn [mailto:glenzorn@gmail.com]
> Sent: Sunday, October 07, 2012 3:28 AM
> To: Black, David
> Cc: glenzorn@gmail.com; lionel.morand@orange.com; gen-art@ietf.org; dime-
> chairs@tools.ietf.org; draft-ietf-dime-rfc4005bis@tools.ietf.org;
> ietf@ietf.org; dime@ietf.org; Benoit Claise
> Subject: Re: Gen-ART review of draft-ietf-dime-rfc4005bis-11
>=20
> On 09/18/2012 06:53 AM, Black, David wrote:
>=20
> > I am the assigned Gen-ART  reviewer for this draft. For background on
>  > Gen-ART, please see the FAQ at
>  > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>  >
>  > Please resolve these comments along with any other Last Call
>  > comments you may receive.
>  >
>  > Document: draft-ietf-dime-rfc4005bis-11 Reviewer: David L. Black
>  > Review Date: September 17, 2012 IETF LC End Date: September 18, 2012
>  > IESG Telechat date: (if known)
>  >
>  > Summary:
>  >
>  > This draft is on the right track but has open issues, described in
>  > the review.
>  >
>  > This draft is part of a set of drafts that updates the DIAMETER
>  > protocol; this draft specifies the application of DIAMETER to AAA for
>  > network access. The draft is heavily based on RFC 4005, which it
>  > obsoletes, and requires significant DIAMETER familiarity (including
>  > familiarity with its companion drafts, starting with the rfc3588bis
>  > draft) for complete understanding.
>  >
>  > The draft is in good shape and reads well. I found one major open
>  > issue, a few minor issues, and several nits.
>  >
>  > Major issues:
>  >
>  > This draft makes significant use of UTF-8 in its formats (some
>  > subsections of sections 4.2, 4.4 and 4.5) for strings that are
>  > intended to be compared for equality or processed by protocol
>  > participants, but does not contain considerations for Unicode
>  > processing that are sufficient to support this usage. Examples of
>  > UTF-8 usage in this draft include:
>  >
>  > - 4.2.5 and 4.2.6: The NAS server may perform authorization based on
>  > the Called-Station-Id and Calling-Station-Id AVPs under some
>  > circumstances. - 4.4.3: The Callback-Id AVP is intended to be
>  > interpreted by the NAS.
>  >
>  > All use of UTF-8 in this draft relies upon the specification of the
>  > UTF8String format in the rfc3588bis draft. That specification is
>  > insufficient to support the usage in the above examples, and there
>  > are no Unicode considerations in this draft. Even binary comparison
>  > of Unicode strings for equality generally requires specification of
>  > string preparation (e.g., normalization) in order for string
>  > comparison to work as expected.
>  >
>  > The variety of Unicode strings in this draft makes it important to
>  > lay out the Unicode requirements and considerations for each AVP. I
>  > see at least 5 classes of possible Unicode
>  > requirements/considerations:
>  >
>  > 1) String preparation so that tests for equality work as expected.
>  > This may suffice for the Called-Station-ID AVP (4.2.5) and
>  > Calling-Station-ID AVP (4.2.6) if the internal structure of those
>  > strings is not used in authorization.
>=20
> Both those AVPs are specified to contain ASCII encoded as UTF-8.  Is
> string preparation necessary in that case?
>=20
> > 2) Detailed string format for a
>  > string that is processed by a protocol participant, e.g., the
>  > Callback-ID AVP (4.4.3).
>=20
> That format is unknown in this case.
> ...
> > 5) Statement that the string  contains an FQDN, as stated for one case =
of
>  > the Tunnel-Client-Endpoint AVP in 4.5.4. That specific statement is
>  > incomplete, as it needs to be accompanied by a normative reference to
>  > a document that specifies the format of internationalized domain
>  > names, and probably needs to also state which types of labels (e.g.,
>  > A-label, U-label) are allowed.
>  >
>  > Every use of UTF8String in this draft needs to be checked, and most
>  > of them are likely to need some attention. The ongoing work in the
>  > precis WG may help with some of this, and I would suggest talking to
>  > the APP ADs, especially Pete Resnick (hi Pete) before embarking on
>  > significant work in this area in order to avoid wasted or duplicated
>  > efforts.
>=20
> OK, this last one bothers me a lot: you /seem /to be suggesting that we
> hold up this draft to wait for the result of a WG which has yet to
> publish a problem statement.  I'm sure that that is not the case, but it
> sure sounds like it.
>=20
> >
>  > Minor Issues:
>  >
>  > [1] End of Section 2 on p.8:
>  >
>  > As a result, service cannot be started as a result of a response to
>  > an authorization-only request without introducing a significant
>  > security vulnerability.
>  >
>  > Please explain what to do about this - a simple rewrite with a
>  > "SHOULD NOT" would suffice, e.g.:
>  >
>  > As a result, service SHOULD NOT be started as a result of a response
>  > to an authorization-only request because that may introduce a
>  > significant security vulnerability.
>=20
> The text in question is descriptive, not prescriptive.at said, however,
> I think that it's not really clear.  I think that it should say
> something like "As a result, a new session cannot be started as a result
> of a response to an authorization-only request without introducing a
> significant security vulnerability."
>=20
> >
>  > This should also be noted in the Security Considerations section.
>  >
>  > [2] In the message formats in Section 3, QoS-Filter-Rule is
>  > inconsistently capitalized.
>=20
> OK, thanks.
>=20
> > Also the use of QoSFilterRule  as the
>  > format for the QoS-Filter-Rule AVP in Section 4.1.1 is potentially
>  > confusing. Please add a sentence in 4.1.1 to say that QoSFilterRule
>  > is the format for the QoS-Filter-Rule AVP.
>  >
>  > [3] Section 4.2.1. In this and the other AVP Flag Rules tables,
>  > please explain what the values in the MUST and MUST NOT columns
>  > mean.
>  >
>  > [4] Based on this text in 4.4.9:
>  >
>  > The use of this AVP is NOT RECOMMENDED; the AVPs defined by
>  > Korhonen, et al. [RFC5777] SHOULD be used instead.
>  >
>  > I would have expected RFC5777 to be a Normative Reference, not an
>  > Informative Reference.
>=20
> I don't care particularly, but I don't think that it's really necessary
> to understand RFC 5777 to understand this document.
>=20
> >
>  > Nits/editorial comments:
>  >
>  > After the command table in Section 3 and other similar tables, please
>  > add a sentence to say that the -Request and -Answer commands in each
>  > similarly-named command pair are distinguished by the value of the
>  > 'R' bit in the Command Flags field of the command. This is already
>  > stated in the command definitions, but the sentence should be added
>  > after the table for clarity because each command pair shares a
>  > Command Code.
>  >
>  > idnits 2.12.13 found a few potential nits:
>  >
>  > =3D=3D There are 7 instances of lines with non-RFC5735-compliant IPv4
>  > addresses in the document. If these are example addresses, they
>  > should be changed.
>  >
>  > That can probably be ignored, as these instances are likely generated
>  > by text such as cross-references to Section 4.4.10.1
>  >
>  > =3D=3D Missing Reference: 'BASE' is mentioned on line 219, but not
>  > defined
>  >
>  > That's definitely a problem. Was [I-D.ietf-dime-rfc3588bis]
>  > intended?
>=20
> No.  The passage in question is a verbatim quote from RFC 4005.
>=20
> >
>  > -- Possible downref: Non-RFC (?) normative reference: ref.
>  > 'ANITypes'
>  >
>  > That reference would be:
>  >
>  > [ANITypes] NANPA Number Resource Info, "ANI Assignments",
>  > <http://www.nanpa.com/ number_resource_info/
>  > ani_ii_assignments.html>.
>  >
>  > Is that reference sufficiently stable (e.g., IANA-class or better
>  > management)?
>=20
> Yes, I think so.
>=20
> > My guess is that it is  sufficiently stable, but I'm not
>  > the expert.
> >
>  > -- Obsolete informational reference (is this intentional?): RFC 1334
>  > (Obsoleted by RFC 1994)
>  >
>  > That reference may be intentional,
>=20
> Yes.
>=20
> ...


From andrew.g.malis@verizon.com  Mon Oct  8 17:55:31 2012
Return-Path: <andrew.g.malis@verizon.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 D4C1811E80F5; Mon,  8 Oct 2012 17:55:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.561
X-Spam-Level: 
X-Spam-Status: No, score=-3.561 tagged_above=-999 required=5 tests=[AWL=0.037,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rfzCBo+0yet1; Mon,  8 Oct 2012 17:55:31 -0700 (PDT)
Received: from fldsmtpe02.verizon.com (fldsmtpe02.verizon.com [140.108.26.141]) by ietfa.amsl.com (Postfix) with ESMTP id 9529111E80DF; Mon,  8 Oct 2012 17:55:30 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: false
Received: from unknown (HELO fldsmtpi03.verizon.com) ([166.68.71.145]) by fldsmtpe02.verizon.com with ESMTP; 09 Oct 2012 00:55:13 +0000
From: "Malis, Andrew G \(Andy\)" <andrew.g.malis@verizon.com>
X-IronPort-AV: E=Sophos;i="4.80,556,1344211200";  d="scan'208,217";a="342506104"
Received: from fhdp1lumxc7hb02.verizon.com (HELO FHDP1LUMXC7HB02.us.one.verizon.com) ([166.68.59.189]) by fldsmtpi03.verizon.com with ESMTP; 09 Oct 2012 00:55:13 +0000
Received: from fhdp1lumxc7v22.us.one.verizon.com ([166.68.59.158]) by FHDP1LUMXC7HB02.us.one.verizon.com ([166.68.59.189]) with mapi; Mon, 8 Oct 2012 20:55:13 -0400
To: Roni Even <ron.even.tlv@gmail.com>, "draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org" <draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org>
Date: Mon, 8 Oct 2012 20:55:12 -0400
Thread-Topic: Gen-ART LC review of draft-ietf-ccamp-rfc5787bis-05
Thread-Index: Ac2luLyUqlVszi5WS+u1neT2y/FIkQ==
Message-ID: <CC98C05A.2FC85%andrew.g.malis@one.verizon.com>
In-Reply-To: <002101cd7997$a5204330$ef60c990$@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.4.120824
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_CC98C05A2FC85andrewgmalisoneverizoncom_"
MIME-Version: 1.0
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "Malis, Andrew G \(Andy\)" <andrew.g.malis@verizon.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-ccamp-rfc5787bis-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Oct 2012 00:55:31 -0000

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

Roni,

Thanks for your review, and sorry for the delay on the response, but we've =
also been working on incorporating other changes to the draft as well.

To answer your question on section 6.1, that was a good catch. That should =
have said "other than the first", rather than "preceding the first". This w=
ill be corrected.

To answer your question on section 10, the text is repeated in the subsecti=
ons to make life easier for IANA, since they would probably have replicated=
 it themselves anyway in the three registry listings.

On your last comment, we agree with you that the more familiar reader will =
not have a problem.

Thanks again,
Andy

From: Roni Even <ron.even.tlv@gmail.com<mailto:ron.even.tlv@gmail.com>>
Date: Monday, August 13, 2012 14:07
To: "draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org<mailto:draft-ietf-ccamp=
-rfc5787bis.all@tools.ietf.org>" <draft-ietf-ccamp-rfc5787bis.all@tools.iet=
f.org<mailto:draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org>>
Cc: "ietf@ietf.org<mailto:ietf@ietf.org>" <ietf@ietf.org<mailto:ietf@ietf.o=
rg>>, "gen-art@ietf.org<mailto:gen-art@ietf.org>" <gen-art@ietf.org<mailto:=
gen-art@ietf.org>>
Subject: Gen-ART LC review of draft-ietf-ccamp-rfc5787bis-05
Resent-To: <acee.lindem@ericsson.com<mailto:acee.lindem@ericsson.com>>, Adr=
ian Farrell <adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>>, Andrew Malis=
 <andrew.g.malis@verizon.com<mailto:andrew.g.malis@verizon.com>>, <dbrungar=
d@att.com<mailto:dbrungard@att.com>>, <dimitri.papadimitriou@alcatel-lucent=
.com<mailto:dimitri.papadimitriou@alcatel-lucent.com>>, <lberger@labn.net<m=
ailto:lberger@labn.net>>

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-ccamp-rfc5787bis-05.

Reviewer: Roni Even

Review Date:2012=968=9612

IETF LC End Date: 2012=968=9617

IESG Telechat date:



Summary: This draft is almost ready for publication as a standard track RFC=
.





Major issues:



Minor issues:
In section 6.1 =93 If specified more than once, instances preceding the fir=
st will be ignored and condition SHOULD be logged for possible action by th=
e network operator.=94  I am not sure what is meant by preceding the first.




Nits/editorial comments:



 1.  The following note appears in section 10.1, 10.2 and 10.3. =93Note tha=
t the same values for the Inter-RA Export Upward sub-TLV and the Inter-RA E=
xport Downward Sub-TLV MUST be used when they appear in the Link TLV, Node =
Attribute TLV, and Router Address TLV.=94 =96 why not have it in section 10=
 before section 10.1.
 2.  I saw in appendix  B that one of the changes from RFC 5787 was to clar=
ify the terminology before defining extensions, I would have found it easie=
r to read if the ASON hierarchy and the relation to OSPF in section 2 were =
presented in figures. This was more an issue to me as a reader not familiar=
 with the terminology and I would like to think that the more familiar read=
er will not have problem.


--_000_CC98C05A2FC85andrewgmalisoneverizoncom_
Content-Type: text/html; charset="Windows-1252"
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-line-break: after-white-space; color: rgb(8, 0, 63); font-size: 14=
px; font-family: Verdana, sans-serif; "><div>Roni,</div><div><br></div><div=
><div>Thanks for your review, and sorry for the delay on the response, but =
we've&nbsp;also been working on incorporating other changes to the draft as=
 well.&nbsp;</div></div><div><br></div><div>To answer your question on sect=
ion 6.1, that was a good catch. That should have said &quot;other than the =
first&quot;, rather than &quot;preceding the first&quot;. This will be corr=
ected.</div><div><br></div><div>To answer your question on section 10, the =
text is repeated in the subsections to make life easier for IANA, since the=
y would probably have replicated it themselves anyway in the three registry=
 listings.</div><div><br></div><div>On your last comment, we agree with you=
 that the more familiar reader will not have a problem.</div><div><br></div=
><div>Thanks again,</div><div>Andy</div><div><br></div><span id=3D"OLK_SRC_=
BODY_SECTION"><div style=3D"font-family:Tahoma; font-size:10pt; text-align:=
left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PA=
DDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4=
df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span style=3D"f=
ont-weight:bold">From: </span> Roni Even &lt;<a href=3D"mailto:ron.even.tlv=
@gmail.com">ron.even.tlv@gmail.com</a>&gt;<br><span style=3D"font-weight:bo=
ld">Date: </span> Monday, August 13, 2012 14:07 <br><span style=3D"font-wei=
ght:bold">To: </span> &quot;<a href=3D"mailto:draft-ietf-ccamp-rfc5787bis.a=
ll@tools.ietf.org">draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org</a>&quot;=
 &lt;<a href=3D"mailto:draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org">draf=
t-ietf-ccamp-rfc5787bis.all@tools.ietf.org</a>&gt;<br><span style=3D"font-w=
eight:bold">Cc: </span> &quot;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.or=
g</a>&quot; &lt;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;, &qu=
ot;<a href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a>&quot; &lt;<a hr=
ef=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a>&gt;<br><span style=3D"f=
ont-weight:bold">Subject: </span> Gen-ART LC review of draft-ietf-ccamp-rfc=
5787bis-05<br><span style=3D"font-weight:bold">Resent-To: </span> &lt;<a hr=
ef=3D"mailto:acee.lindem@ericsson.com">acee.lindem@ericsson.com</a>&gt;, Ad=
rian Farrell &lt;<a href=3D"mailto:adrian@olddog.co.uk">adrian@olddog.co.uk=
</a>&gt;, Andrew Malis &lt;<a href=3D"mailto:andrew.g.malis@verizon.com">an=
drew.g.malis@verizon.com</a>&gt;, &lt;<a href=3D"mailto:dbrungard@att.com">=
dbrungard@att.com</a>&gt;, &lt;<a href=3D"mailto:dimitri.papadimitriou@alca=
tel-lucent.com">dimitri.papadimitriou@alcatel-lucent.com</a>&gt;, &lt;<a hr=
ef=3D"mailto:lberger@labn.net">lberger@labn.net</a>&gt;<br></div><div><br><=
/div><div 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:wo=
rd" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"h=
ttp://www.w3.org/TR/REC-html40"><meta name=3D"Generator" content=3D"Microso=
ft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:715087181;
	mso-list-type:hybrid;
	mso-list-template-ids:-1205706658 -1668626108 67698713 67698715 67698703 6=
7698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-bidi-font-family:Calibri;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--><div lang=3D"EN-US" link=3D"blue" vlink=
=3D"purple"><div class=3D"WordSection1"><p class=3D"MsoNormal">I am the ass=
igned Gen-ART reviewer for this draft. For background on Gen-ART, please se=
e the FAQ at &lt;<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/G=
enArtfaq" target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/G=
enArtfaq</a>&gt;.<o:p></o:p></p><p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p=
><p class=3D"MsoNormal">Please resolve these comments along with any other =
Last Call comments you may receive.<o:p></o:p></p><p class=3D"MsoPlainText"=
><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; "><o:p>&=
nbsp;</o:p></span></p><p class=3D"MsoPlainText"><span style=3D"font-size: 1=
1pt; font-family: Calibri, sans-serif; ">Document:
</span>draft-ietf-ccamp-rfc5787bis-05.<span style=3D"font-size: 11pt; font-=
family: Calibri, sans-serif; "><o:p></o:p></span></p><p class=3D"MsoPlainTe=
xt"><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; ">Rev=
iewer: Roni Even<o:p></o:p></span></p><p class=3D"MsoPlainText"><span style=
=3D"font-size: 11pt; font-family: Calibri, sans-serif; ">Review Date:2012=
=968=9612<o:p></o:p></span></p><p class=3D"MsoPlainText"><span style=3D"fon=
t-size: 11pt; font-family: Calibri, sans-serif; ">IETF LC End Date: 2012=96=
8=9617<o:p></o:p></span></p><p class=3D"MsoPlainText"><span style=3D"font-s=
ize: 11pt; font-family: Calibri, sans-serif; ">IESG Telechat date:<o:p></o:=
p></span></p><p class=3D"MsoPlainText"><span style=3D"font-size: 11pt; font=
-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></span></p><p class=3D"Mso=
PlainText"><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif=
; ">Summary: This draft is almost ready for publication as</span><span styl=
e=3D"font-size: 11pt; font-family: Calibri, sans-serif; "> a standard track
</span><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; ">=
RFC</span><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif;=
 ">.<o:p></o:p></span></p><p class=3D"MsoPlainText"><span style=3D"font-siz=
e: 11pt; font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></span></p><p=
 class=3D"MsoPlainText"><span style=3D"font-size: 11pt; font-family: Calibr=
i, sans-serif; "><o:p>&nbsp;</o:p></span></p><p class=3D"MsoPlainText"><spa=
n style=3D"font-size: 11pt; font-family: Calibri, sans-serif; ">Major issue=
s:<o:p></o:p></span></p><p class=3D"MsoPlainText"><span style=3D"font-size:=
 11pt; font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></span></p><p c=
lass=3D"MsoPlainText"><span style=3D"font-size: 11pt; font-family: Calibri,=
 sans-serif; ">Minor issues:<o:p></o:p></span></p><p class=3D"MsoNormal">In=
 section 6.1 =93 If specified more than once, instances preceding the first=
 will be ignored and condition SHOULD be logged for possible action by the =
network operator.=94&nbsp; I am not sure what is meant by preceding the fir=
st.<o:p></o:p></p><p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p><p class=3D"M=
soPlainText"><span style=3D"font-size: 11pt; font-family: Calibri, sans-ser=
if; "><o:p>&nbsp;</o:p></span></p><p class=3D"MsoPlainText"><span style=3D"=
font-size: 11pt; font-family: Calibri, sans-serif; ">Nits/editorial comment=
s:<o:p></o:p></span></p><p class=3D"MsoPlainText"><span style=3D"font-size:=
 11pt; font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></span></p><ol =
style=3D"margin-top:0in" start=3D"1" type=3D"1"><li class=3D"MsoNormal" sty=
le=3D"mso-list:l0 level1 lfo1">The following note appears in section 10.1, =
10.2 and 10.3. =93Note that the same values for the Inter-RA Export Upward =
sub-TLV and the Inter-RA Export Downward Sub-TLV MUST be used when they app=
ear in the
 Link TLV, Node Attribute TLV, and Router Address TLV.=94 =96 why not have =
it in section 10 before section 10.1.<o:p></o:p></li><li class=3D"MsoNormal=
" style=3D"mso-list:l0 level1 lfo1">I saw in appendix&nbsp; B that one of t=
he changes from RFC 5787 was to clarify the terminology before defining ext=
ensions, I would have found it easier to read if the ASON hierarchy and the=
 relation to OSPF in
 section 2 were presented in figures. This was more an issue to me as a rea=
der not familiar with the terminology and I would like to think that the mo=
re familiar reader will not have problem.<o:p></o:p></li></ol><p class=3D"M=
soPlainText"><span style=3D"font-size: 11pt; font-family: Calibri, sans-ser=
if; "><o:p></o:p></span></p><p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p></d=
iv></div></div></span></body></html>

--_000_CC98C05A2FC85andrewgmalisoneverizoncom_--

From suresh.krishnan@ericsson.com  Mon Oct  8 22:28:27 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 0D62621F8510 for <gen-art@ietfa.amsl.com>; Mon,  8 Oct 2012 22:28:27 -0700 (PDT)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LPl14BNv+MC6 for <gen-art@ietfa.amsl.com>; Mon,  8 Oct 2012 22:28:26 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 2BBE121F84C4 for <gen-art@ietf.org>; Mon,  8 Oct 2012 22:28:26 -0700 (PDT)
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 q995T4qX014732; Tue, 9 Oct 2012 00:29:05 -0500
Received: from [164.48.125.14] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.181) with Microsoft SMTP Server (TLS) id 8.3.279.1; Tue, 9 Oct 2012 01:28:17 -0400
Message-ID: <5073B5E6.407@ericsson.com>
Date: Tue, 9 Oct 2012 01:28:06 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0
MIME-Version: 1.0
To: <draft-ietf-abfab-gss-eap-naming.all@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>
X-Enigmail-Version: 1.4.4
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: [Gen-art] Gen-ART Telechat review of draft-ietf-abfab-gss-eap-naming-06.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Oct 2012 05:28:27 -0000

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

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

Document: draft-ietf-abfab-gss-eap-naming-06.txt
Reviewer: Suresh Krishnan
Review Date: 2012/10/08
IESG Telechat date: 2012/10/11

Summary: This document is ready for publication as a Proposed Standard.
I do have some minor comments you may wish to address.

Minor
=====

* Section 6.1:

This sentence is a bit difficult to read.

"This attribute is returned with the authenticated output of
GSS_Get_name_attribute true only when the mechanism can successfully
authenticated the SAML statement."

Suggest rewording to

"When GSS_Get_name_attribute is called, this attribute will be returned
with the authenticated output set to true only if the mechanism can
successfully authenticate the SAML statement."

(Is my interpretation correct?)

* Section 6.2:

s/encoding as "%20"/encoded as "%20"/

Thanks
Suresh



From wassim.haddad@ericsson.com  Mon Oct  8 23:18: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 3415621F8843 for <gen-art@ietfa.amsl.com>; Mon,  8 Oct 2012 23:18:06 -0700 (PDT)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tQP9iYxf94Eq for <gen-art@ietfa.amsl.com>; Mon,  8 Oct 2012 23:18:05 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 98AF021F883D for <gen-art@ietf.org>; Mon,  8 Oct 2012 23:18:05 -0700 (PDT)
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 q996IiL7015874; Tue, 9 Oct 2012 01:18:46 -0500
Received: from [164.48.125.29] (147.117.20.214) by eusaamw0706.eamcs.ericsson.se (147.117.20.91) with Microsoft SMTP Server id 8.3.279.1; Tue, 9 Oct 2012 02:17:57 -0400
From: Wassim Haddad <wassim.haddad@ericsson.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 8 Oct 2012 23:17:54 -0700
Message-ID: <BB3EAA89-9A01-4B98-81E5-BCE606C440C3@ericsson.com>
To: Gen-art <gen-art@ietf.org>
MIME-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
Cc: draft-ietf-avtext-splicing-for-rtp.all@tools.ietf.org
Subject: [Gen-art]  Gen-ART Review of draft-ietf-avtext-splicing-for-rtp
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, 09 Oct 2012 06:18:06 -0000

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

Document: draft-ietf-avtext-splicing-for-rtp-09
Reviewer:  Wassim Haddad
Review Date:  08 Oct 2012
IETF LC End Date: 03 Apr 2012
IETF Telechat Date: 11 Oct 2012

Summary:  This draft is ready for publication as informational standard.

- Major Issues: None

- Minor Issues: None


Regards,

Wassim H.






From hartmans@mit.edu  Tue Oct  9 04:24:00 2012
Return-Path: <hartmans@mit.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 346AE21F88E6 for <gen-art@ietfa.amsl.com>; Tue,  9 Oct 2012 04:24:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.755
X-Spam-Level: 
X-Spam-Status: No, score=-96.755 tagged_above=-999 required=5 tests=[AWL=-1.043, BAYES_00=-2.599, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L8SaCvPCjOb2 for <gen-art@ietfa.amsl.com>; Tue,  9 Oct 2012 04:23:59 -0700 (PDT)
Received: from ec2-23-21-227-93.compute-1.amazonaws.com (ec2-23-21-227-93.compute-1.amazonaws.com [23.21.227.93]) by ietfa.amsl.com (Postfix) with ESMTP id B0D0F21F88E5 for <gen-art@ietf.org>; Tue,  9 Oct 2012 04:23:59 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (c-98-217-126-210.hsd1.ma.comcast.net [98.217.126.210]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id 680962027D; Tue,  9 Oct 2012 07:23:44 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 017D74AD5; Tue,  9 Oct 2012 07:23:55 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
References: <5073B5E6.407@ericsson.com>
Date: Tue, 09 Oct 2012 07:23:55 -0400
In-Reply-To: <5073B5E6.407@ericsson.com> (Suresh Krishnan's message of "Tue, 9 Oct 2012 01:28:06 -0400")
Message-ID: <tslk3uz51o4.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-abfab-gss-eap-naming.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART Telechat review of draft-ietf-abfab-gss-eap-naming-06.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Oct 2012 11:24:00 -0000

>>>>> "Suresh" == Suresh Krishnan <suresh.krishnan@ericsson.com> writes:


    Suresh> "When GSS_Get_name_attribute is called, this attribute will
    Suresh> be returned with the authenticated output set to true only
    Suresh> if the mechanism can successfully authenticate the SAML
    Suresh> statement."

    Suresh> (Is my interpretation correct?)

Your interpretation is correct and the reword helps.

Stephen, so far, I'm aware of this comment and the last call discussion
between Simon and scott regarding what it means to be a well-formed XML
serialization that might require addressing.

From vincent.roca@inria.fr  Tue Oct  9 06:23:02 2012
Return-Path: <vincent.roca@inria.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 91CFE11E8106; Tue,  9 Oct 2012 06:23:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.249
X-Spam-Level: 
X-Spam-Status: No, score=-111.249 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, GB_I_LETTER=-2, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ElDZFibddkBW; Tue,  9 Oct 2012 06:23:01 -0700 (PDT)
Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by ietfa.amsl.com (Postfix) with ESMTP id 32DAD11E80F8; Tue,  9 Oct 2012 06:23:01 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.80,560,1344204000"; d="scan'208";a="176466501"
Received: from geve.inrialpes.fr ([194.199.24.116]) by mail1-relais-roc.national.inria.fr with ESMTP/TLS/AES128-SHA; 09 Oct 2012 15:22:59 +0200
From: Vincent Roca <vincent.roca@inria.fr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Tue, 9 Oct 2012 15:22:59 +0200
Message-Id: <7DB3D313-2756-440D-83FB-8220CA87D9AB@inria.fr>
To: meral.shirazipour@ericsson.com, The IESG <iesg@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Cc: draft-ietf-fecframe-ldpc-all@tools.ietf.org, gen-art@ietf.org
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-fecframe-ldpc-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: Tue, 09 Oct 2012 13:23:02 -0000

Hello Meral,

Thanks a lot for your review. Please, find our answers below.

> Document: draft-ietf-fecframe-ldpc-02
> Reviewer: Meral Shirazipour
> Review Date: 2012-10-01
> IETF LC End Date: 2012-10-01
> IESG Telechat date: NA
>
>
> Summary:
> This draft is almost ready for publication as a standard track RFC, =
but I have some comments.
>
> Nits/editorial comments:
> [Page 3], Section 1, "ALC [RFC5775]", please spell out ALC: =
"Asynchronous Layered Coding (ALC)"

Done.


> [Page 3], Section 1, "NORM [RFC5740]", please spell out NORM: =
"NACK-Oriented Reliable Multicast (NORM)"

Done.


> [Page 4], line 3, ALU is first used, please spell out: "Application =
Data Unit (ADU)", or move section "3.3 Abbreviations" to the beginning.

Done.


> [Page 4], Section "3.1.  Definitions", after the ":" for all =
definitions, please start with capital letters or with lower case (for =
consistency please choose one)

Right, this is not consistent. Moved everything to lower case letters.


> [Page 5], for "ADU Block", it would clearer to have Flow ID, Length =
and Padding fields in parenthesis next to F[], L[], and Pad[] =
respectively.

Done.
I also realized we were using the term FID[i] twice to denote the F[i] =
field in section 4.3 "Source block creation".
We corrected to use F[] throughout the document.

NEW:
  ADU Block:  a set of ADUs that are considered together by the
      FECFRAME instance for the purpose of the FEC scheme.  Along with
      the flow ID (F[]), length (L[]), and padding (Pad[]) fields, they
      form the set of source symbols over which FEC encoding will be
      performed.

> [Page 5], after "FEC Framework Configuration Information" please add =
"(FFCI)".

Done.


> [Page 5], section 4.1, "G MUST be equal..", please define G in section =
"3.2.  Notations".

Added.


> [Page 9], last sentence, "Each ADUI contributes to exactly one source =
symbol to the source block.", it is clearer to say "...of the source =
block."

Done


> [Page 15], Section 6.1.1, "(e.g., before versus after FEC protection, =
and within the end-system versus in a middlebox)", please rephrase if =
possible, this is not very clear.

Done.

NEW:

   (e.g., is encryption applied before or after FEC protection, within =
the end-system or in a middlebox)


> [Page 19], reference [SIMPLE_RS] is now at version 03.

Now in version -04. Updated.


> [Page 19], reference [RFC5053]: title is missing "for Object Delivery"

Exact! Fixed.


> -Overall for clarity, please adapt one method for spelling out =
acronyms (either in one section in intro, or throughout the text as they =
are first used; but not both).

I think it's homogeneous now.


> -Overall for clarity, some line feed would be useful in section 5. =20

I've added the <?rfc rfcedstyle=3D"yes"?> magic directive, and now lists =
are much more readable.
I've also changed the style of lists for "symbols", and it also helps =
making it more readable.

>
> Best Regards,
> Meral
>
> ---
> Meral Shirazipour
> Ericsson Research
> www.ericsson.com
>=20
> --

Cheers,

   Vincent, on behalf of the authors


From dromasca@avaya.com  Tue Oct  9 07:22:17 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 6CEE21F0C72 for <gen-art@ietfa.amsl.com>; Tue,  9 Oct 2012 07:22:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.821
X-Spam-Level: 
X-Spam-Status: No, score=-102.821 tagged_above=-999 required=5 tests=[AWL=-0.222, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VVnFys5NyyEF for <gen-art@ietfa.amsl.com>; Tue,  9 Oct 2012 07:22:16 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 4797A1F0C42 for <gen-art@ietf.org>; Tue,  9 Oct 2012 07:22:15 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAHgydFCHCzI1/2dsb2JhbABFvy6BCIIgAQEBAQIBEh4KMQMQDQEVBw4GDAwHVwEEEwgMDoddBguaFIQljFmQPY4rgkFgA5Z/hG+KLIJv
X-IronPort-AV: E=Sophos;i="4.80,561,1344225600"; d="scan'208";a="30563189"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 09 Oct 2012 10:14:46 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 09 Oct 2012 10:00:02 -0400
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 9 Oct 2012 16:22:09 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A040822F948@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: GEN-ART telechat review of draft-ietf-dnsext-rfc6195bis-04.txt
Thread-Index: Ac2mKXe8zInd18z9SsG1+nqpJVL+MA==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <gen-art@ietf.org>
Subject: [Gen-art] GEN-ART telechat review of draft-ietf-dnsext-rfc6195bis-04.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Oct 2012 14:22: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>=20
Please wait for direction from your document shepherd or AD before
posting a new version of the draft.=20


Document: draft-ietf-dnsext-rfc6195bis-04.txt=20
Reviewer: Dan Romascanu
Review Date: 2012/10/09
IESG Telechat date: 2012/10/11

This draft is basically ready for publication, but has nits that should
be fixed before publication.


Minor Comments:=20


1. RFC 6195 was published only a year and a half ago. It would be good
to explain in a sentence in the introduction the reasons of obsolescing
it so soon by a new RFC. Is this because of the publication of
[RFC2671bis], or because problems with the IANA registries and processes
that needed to be fixed, or both?=20

2.  Section 2:=20

> The header for DNS queries and responses contains field/bits in the
   following diagram taken from [RFC2136] and [RFC6195]:

I think you should drop the mention to [RFC6195]. As this document will
obsolete RFC6195 there is no need to mention that the diagram is taken
from there

3. Section 2.2:=20

> New OpCode assignments require a Standards Action
   as modified by [RFC4020].


This sentence seems to have a historical flavor. I suggest
s/modified/defined/

4. Section 3.1.1:=20

> RRTYPEs that do not meet the requirements below may nonetheless be
   allocated by a Standards Action as modified by [RFC4020].

Same comment and suggestion as above

5. Section 3.1.1:=20

> If the Expert does not approve the
   application within this period, it is considered rejected.

I believe it would be good to recommend that an explanation be returned
to the supplicants about the reasons of the rejection, with possible
suggestions to complete or fix the problems that led to the allocation
request to be rejected.=20

6. Section 3.1.2:=20

Is not duplicated mnemonic another reason for rejecting an RRTYPE
allocation request that should be listed?=20

7. Section 5:=20

> The dnsext@ietf.org mailing list is for community discussion and
comment.=20

I do not believe that this statement belongs in the IANA considerations
section, there is no indication for an IANA action, but rather a
recommendation to the supplicant to prepare their request and get
community input by sharing it on the dnsext list.=20

8. Appendix B:=20

> Note that this can be
   considered to update [RFC2845] and [RFC2930].

No room for conditional language, as the update is mentioned in the
header of the document.=20

I suggest: s/can be considered/is considered/

9. id-nits flags the downref dependency on the approval of [RFC2671bis]
- I guess that this was taken into consideration by the WG.=20


Regards,

Dan


From meral.shirazipour@ericsson.com  Tue Oct  9 07:59:29 2012
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAC311F0C7E; Tue,  9 Oct 2012 07:59:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.799
X-Spam-Level: 
X-Spam-Status: No, score=-7.799 tagged_above=-999 required=5 tests=[AWL=0.800,  BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NxtMnsqQJxAA; Tue,  9 Oct 2012 07:59:29 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id BCEAC1F0C95; Tue,  9 Oct 2012 07:59:28 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id q99ExH5r001545 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 9 Oct 2012 09:59:27 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.205]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Tue, 9 Oct 2012 10:59:17 -0400
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: Vincent Roca <vincent.roca@inria.fr>
Date: Tue, 9 Oct 2012 10:59:16 -0400
Thread-Topic: Gen-ART Last Call review of draft-ietf-fecframe-ldpc-02
Thread-Index: Ac2mITW4ZE6W4oPpTqmS/ntwkWL6EAACvRUg
Message-ID: <25DC600D0CC1F2479C7053ADEB93004E6DF7D49770@EUSAACMS0703.eamcs.ericsson.se>
References: <7DB3D313-2756-440D-83FB-8220CA87D9AB@inria.fr>
In-Reply-To: <7DB3D313-2756-440D-83FB-8220CA87D9AB@inria.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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-ietf-fecframe-ldpc-all@tools.ietf.org" <draft-ietf-fecframe-ldpc-all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, The IESG <iesg@ietf.org>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-fecframe-ldpc-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: Tue, 09 Oct 2012 14:59:29 -0000

Hi,
   Thank you for the changes and v04. I also assume the changes v02->v03 in=
 Section 7.1's examples were based on LC reviews.

Best Regards,
Meral

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

=20

> -----Original Message-----
> From: Vincent Roca [mailto:vincent.roca@inria.fr]
> Sent: October-09-12 09:23
> To: Meral Shirazipour; The IESG
> Cc: draft-ietf-fecframe-ldpc-all@tools.ietf.org; gen-art@ietf.org
> Subject: Re: Gen-ART Last Call review of draft-ietf-fecframe-ldpc-02
>=20
> Hello Meral,
>=20
> Thanks a lot for your review. Please, find our answers below.
>=20
> > Document: draft-ietf-fecframe-ldpc-02
> > Reviewer: Meral Shirazipour
> > Review Date: 2012-10-01
> > IETF LC End Date: 2012-10-01
> > IESG Telechat date: NA
> >
> >
> > Summary:
> > This draft is almost ready for publication as a standard track RFC, but=
 I have
> some comments.
> >
> > Nits/editorial comments:
> > [Page 3], Section 1, "ALC [RFC5775]", please spell out ALC: "Asynchrono=
us
> Layered Coding (ALC)"
>=20
> Done.
>=20
>=20
> > [Page 3], Section 1, "NORM [RFC5740]", please spell out NORM: "NACK-
> Oriented Reliable Multicast (NORM)"
>=20
> Done.
>=20
>=20
> > [Page 4], line 3, ALU is first used, please spell out: "Application Dat=
a Unit
> (ADU)", or move section "3.3 Abbreviations" to the beginning.
>=20
> Done.
>=20
>=20
> > [Page 4], Section "3.1.  Definitions", after the ":" for all definition=
s, please
> start with capital letters or with lower case (for consistency please cho=
ose one)
>=20
> Right, this is not consistent. Moved everything to lower case letters.
>=20
>=20
> > [Page 5], for "ADU Block", it would clearer to have Flow ID, Length and
> Padding fields in parenthesis next to F[], L[], and Pad[] respectively.
>=20
> Done.
> I also realized we were using the term FID[i] twice to denote the F[i] fi=
eld in
> section 4.3 "Source block creation".
> We corrected to use F[] throughout the document.
>=20
> NEW:
>   ADU Block:  a set of ADUs that are considered together by the
>       FECFRAME instance for the purpose of the FEC scheme.  Along with
>       the flow ID (F[]), length (L[]), and padding (Pad[]) fields, they
>       form the set of source symbols over which FEC encoding will be
>       performed.
>=20
> > [Page 5], after "FEC Framework Configuration Information" please add
> "(FFCI)".
>=20
> Done.
>=20
>=20
> > [Page 5], section 4.1, "G MUST be equal..", please define G in section =
"3.2.
> Notations".
>=20
> Added.
>=20
>=20
> > [Page 9], last sentence, "Each ADUI contributes to exactly one source s=
ymbol
> to the source block.", it is clearer to say "...of the source block."
>=20
> Done
>=20
>=20
> > [Page 15], Section 6.1.1, "(e.g., before versus after FEC protection, a=
nd within
> the end-system versus in a middlebox)", please rephrase if possible, this=
 is not
> very clear.
>=20
> Done.
>=20
> NEW:
>=20
>    (e.g., is encryption applied before or after FEC protection, within th=
e end-
> system or in a middlebox)
>=20
>=20
> > [Page 19], reference [SIMPLE_RS] is now at version 03.
>=20
> Now in version -04. Updated.
>=20
>=20
> > [Page 19], reference [RFC5053]: title is missing "for Object Delivery"
>=20
> Exact! Fixed.
>=20
>=20
> > -Overall for clarity, please adapt one method for spelling out acronyms
> (either in one section in intro, or throughout the text as they are first=
 used; but
> not both).
>=20
> I think it's homogeneous now.
>=20
>=20
> > -Overall for clarity, some line feed would be useful in section 5.
>=20
> I've added the <?rfc rfcedstyle=3D"yes"?> magic directive, and now lists =
are much
> more readable.
> I've also changed the style of lists for "symbols", and it also helps mak=
ing it
> more readable.
>=20
> >
> > Best Regards,
> > Meral
> >
> > ---
> > Meral Shirazipour
> > Ericsson Research
> > www.ericsson.com
> >
> > --
>=20
> Cheers,
>=20
>    Vincent, on behalf of the authors


From vincent.roca@inria.fr  Tue Oct  9 08:07:48 2012
Return-Path: <vincent.roca@inria.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 5ACEB21F8575; Tue,  9 Oct 2012 08:07:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.392
X-Spam-Level: 
X-Spam-Status: No, score=-111.392 tagged_above=-999 required=5 tests=[AWL=0.857, BAYES_00=-2.599, GB_I_LETTER=-2, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FXFzqOEdzWHi; Tue,  9 Oct 2012 08:07:47 -0700 (PDT)
Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by ietfa.amsl.com (Postfix) with ESMTP id A5E3B21F8540; Tue,  9 Oct 2012 08:07:46 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.80,560,1344204000"; d="scan'208";a="176487610"
Received: from geve.inrialpes.fr ([194.199.24.116]) by mail1-relais-roc.national.inria.fr with ESMTP/TLS/AES128-SHA; 09 Oct 2012 17:07:40 +0200
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Vincent Roca <vincent.roca@inria.fr>
In-Reply-To: <25DC600D0CC1F2479C7053ADEB93004E6DF7D49770@EUSAACMS0703.eamcs.ericsson.se>
Date: Tue, 9 Oct 2012 17:07:39 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <9D3B5666-01AB-4666-ABBF-99A778B24326@inria.fr>
References: <7DB3D313-2756-440D-83FB-8220CA87D9AB@inria.fr> <25DC600D0CC1F2479C7053ADEB93004E6DF7D49770@EUSAACMS0703.eamcs.ericsson.se>
To: Meral Shirazipour <meral.shirazipour@ericsson.com>
X-Mailer: Apple Mail (2.1085)
Cc: "draft-ietf-fecframe-ldpc-all@tools.ietf.org" <draft-ietf-fecframe-ldpc-all@tools.ietf.org>, Vincent Roca <vincent.roca@inria.fr>, "gen-art@ietf.org" <gen-art@ietf.org>, The IESG <iesg@ietf.org>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-fecframe-ldpc-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: Tue, 09 Oct 2012 15:07:48 -0000

Hello,

The -02 to -03 changes are the result of comments from IANA and Barry =
Leiba.

Concerning Section 7.1 "Operational Recommendations", changes were =
essentially
motivated by recent advances with our LDPC-Staircase codec (new =
figures), and
a comment from Barry concerning the inappropriate use of MAY.=20

Hope it clarifies.
Cheers,

   Vincent


> Hi,
>   Thank you for the changes and v04. I also assume the changes =
v02->v03 in Section 7.1's examples were based on LC reviews.
>=20
> Best Regards,
> Meral
>=20
> ---
> Meral Shirazipour
> Ericsson Research
> www.ericsson.com
>=20
>=20
>=20
>> -----Original Message-----
>> From: Vincent Roca [mailto:vincent.roca@inria.fr]
>> Sent: October-09-12 09:23
>> To: Meral Shirazipour; The IESG
>> Cc: draft-ietf-fecframe-ldpc-all@tools.ietf.org; gen-art@ietf.org
>> Subject: Re: Gen-ART Last Call review of draft-ietf-fecframe-ldpc-02
>>=20
>> Hello Meral,
>>=20
>> Thanks a lot for your review. Please, find our answers below.
>>=20
>>> Document: draft-ietf-fecframe-ldpc-02
>>> Reviewer: Meral Shirazipour
>>> Review Date: 2012-10-01
>>> IETF LC End Date: 2012-10-01
>>> IESG Telechat date: NA
>>>=20
>>>=20
>>> Summary:
>>> This draft is almost ready for publication as a standard track RFC, =
but I have
>> some comments.
>>>=20
>>> Nits/editorial comments:
>>> [Page 3], Section 1, "ALC [RFC5775]", please spell out ALC: =
"Asynchronous
>> Layered Coding (ALC)"
>>=20
>> Done.
>>=20
>>=20
>>> [Page 3], Section 1, "NORM [RFC5740]", please spell out NORM: "NACK-
>> Oriented Reliable Multicast (NORM)"
>>=20
>> Done.
>>=20
>>=20
>>> [Page 4], line 3, ALU is first used, please spell out: "Application =
Data Unit
>> (ADU)", or move section "3.3 Abbreviations" to the beginning.
>>=20
>> Done.
>>=20
>>=20
>>> [Page 4], Section "3.1.  Definitions", after the ":" for all =
definitions, please
>> start with capital letters or with lower case (for consistency please =
choose one)
>>=20
>> Right, this is not consistent. Moved everything to lower case =
letters.
>>=20
>>=20
>>> [Page 5], for "ADU Block", it would clearer to have Flow ID, Length =
and
>> Padding fields in parenthesis next to F[], L[], and Pad[] =
respectively.
>>=20
>> Done.
>> I also realized we were using the term FID[i] twice to denote the =
F[i] field in
>> section 4.3 "Source block creation".
>> We corrected to use F[] throughout the document.
>>=20
>> NEW:
>>  ADU Block:  a set of ADUs that are considered together by the
>>      FECFRAME instance for the purpose of the FEC scheme.  Along with
>>      the flow ID (F[]), length (L[]), and padding (Pad[]) fields, =
they
>>      form the set of source symbols over which FEC encoding will be
>>      performed.
>>=20
>>> [Page 5], after "FEC Framework Configuration Information" please add
>> "(FFCI)".
>>=20
>> Done.
>>=20
>>=20
>>> [Page 5], section 4.1, "G MUST be equal..", please define G in =
section "3.2.
>> Notations".
>>=20
>> Added.
>>=20
>>=20
>>> [Page 9], last sentence, "Each ADUI contributes to exactly one =
source symbol
>> to the source block.", it is clearer to say "...of the source block."
>>=20
>> Done
>>=20
>>=20
>>> [Page 15], Section 6.1.1, "(e.g., before versus after FEC =
protection, and within
>> the end-system versus in a middlebox)", please rephrase if possible, =
this is not
>> very clear.
>>=20
>> Done.
>>=20
>> NEW:
>>=20
>>   (e.g., is encryption applied before or after FEC protection, within =
the end-
>> system or in a middlebox)
>>=20
>>=20
>>> [Page 19], reference [SIMPLE_RS] is now at version 03.
>>=20
>> Now in version -04. Updated.
>>=20
>>=20
>>> [Page 19], reference [RFC5053]: title is missing "for Object =
Delivery"
>>=20
>> Exact! Fixed.
>>=20
>>=20
>>> -Overall for clarity, please adapt one method for spelling out =
acronyms
>> (either in one section in intro, or throughout the text as they are =
first used; but
>> not both).
>>=20
>> I think it's homogeneous now.
>>=20
>>=20
>>> -Overall for clarity, some line feed would be useful in section 5.
>>=20
>> I've added the <?rfc rfcedstyle=3D"yes"?> magic directive, and now =
lists are much
>> more readable.
>> I've also changed the style of lists for "symbols", and it also helps =
making it
>> more readable.
>>=20
>>>=20
>>> Best Regards,
>>> Meral
>>>=20
>>> ---
>>> Meral Shirazipour
>>> Ericsson Research
>>> www.ericsson.com
>>>=20
>>> --
>>=20
>> Cheers,
>>=20
>>   Vincent, on behalf of the authors
>=20


From meral.shirazipour@ericsson.com  Tue Oct  9 08:08:59 2012
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F03B21F851B; Tue,  9 Oct 2012 08:08:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.932
X-Spam-Level: 
X-Spam-Status: No, score=-7.932 tagged_above=-999 required=5 tests=[AWL=0.667,  BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tCyyHNOoRvaZ; Tue,  9 Oct 2012 08:08:58 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 6ED2321F8518; Tue,  9 Oct 2012 08:08:58 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q99F9axs002799; Tue, 9 Oct 2012 10:09:42 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.205]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Tue, 9 Oct 2012 11:08:56 -0400
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: Vincent Roca <vincent.roca@inria.fr>
Date: Tue, 9 Oct 2012 11:08:54 -0400
Thread-Topic: Gen-ART Last Call review of draft-ietf-fecframe-ldpc-02
Thread-Index: Ac2mL9ge9JBRyDJrRkO8nMCaOaBJVQAABCDg
Message-ID: <25DC600D0CC1F2479C7053ADEB93004E6DF7D497AB@EUSAACMS0703.eamcs.ericsson.se>
References: <7DB3D313-2756-440D-83FB-8220CA87D9AB@inria.fr> <25DC600D0CC1F2479C7053ADEB93004E6DF7D49770@EUSAACMS0703.eamcs.ericsson.se> <9D3B5666-01AB-4666-ABBF-99A778B24326@inria.fr>
In-Reply-To: <9D3B5666-01AB-4666-ABBF-99A778B24326@inria.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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-ietf-fecframe-ldpc-all@tools.ietf.org" <draft-ietf-fecframe-ldpc-all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, The IESG <iesg@ietf.org>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-fecframe-ldpc-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: Tue, 09 Oct 2012 15:08:59 -0000

Hi,
  That is great, thank you for the quick reply.

Best,
Meral

> -----Original Message-----
> From: Vincent Roca [mailto:vincent.roca@inria.fr]
> Sent: October-09-12 11:08
> To: Meral Shirazipour
> Cc: Vincent Roca; draft-ietf-fecframe-ldpc-all@tools.ietf.org; gen-art@ie=
tf.org;
> The IESG
> Subject: Re: Gen-ART Last Call review of draft-ietf-fecframe-ldpc-02
>=20
> Hello,
>=20
> The -02 to -03 changes are the result of comments from IANA and Barry Lei=
ba.
>=20
> Concerning Section 7.1 "Operational Recommendations", changes were
> essentially motivated by recent advances with our LDPC-Staircase codec (n=
ew
> figures), and a comment from Barry concerning the inappropriate use of MA=
Y.
>=20
> Hope it clarifies.
> Cheers,
>=20
>    Vincent
>=20
>=20
> > Hi,
> >   Thank you for the changes and v04. I also assume the changes v02->v03=
 in
> Section 7.1's examples were based on LC reviews.
> >
> > Best Regards,
> > Meral
> >
> > ---
> > Meral Shirazipour
> > Ericsson Research
> > www.ericsson.com
> >
> >
> >
> >> -----Original Message-----
> >> From: Vincent Roca [mailto:vincent.roca@inria.fr]
> >> Sent: October-09-12 09:23
> >> To: Meral Shirazipour; The IESG
> >> Cc: draft-ietf-fecframe-ldpc-all@tools.ietf.org; gen-art@ietf.org
> >> Subject: Re: Gen-ART Last Call review of draft-ietf-fecframe-ldpc-02
> >>
> >> Hello Meral,
> >>
> >> Thanks a lot for your review. Please, find our answers below.
> >>
> >>> Document: draft-ietf-fecframe-ldpc-02
> >>> Reviewer: Meral Shirazipour
> >>> Review Date: 2012-10-01
> >>> IETF LC End Date: 2012-10-01
> >>> IESG Telechat date: NA
> >>>
> >>>
> >>> Summary:
> >>> This draft is almost ready for publication as a standard track RFC,
> >>> but I have
> >> some comments.
> >>>
> >>> Nits/editorial comments:
> >>> [Page 3], Section 1, "ALC [RFC5775]", please spell out ALC:
> >>> "Asynchronous
> >> Layered Coding (ALC)"
> >>
> >> Done.
> >>
> >>
> >>> [Page 3], Section 1, "NORM [RFC5740]", please spell out NORM: "NACK-
> >> Oriented Reliable Multicast (NORM)"
> >>
> >> Done.
> >>
> >>
> >>> [Page 4], line 3, ALU is first used, please spell out: "Application
> >>> Data Unit
> >> (ADU)", or move section "3.3 Abbreviations" to the beginning.
> >>
> >> Done.
> >>
> >>
> >>> [Page 4], Section "3.1.  Definitions", after the ":" for all
> >>> definitions, please
> >> start with capital letters or with lower case (for consistency please
> >> choose one)
> >>
> >> Right, this is not consistent. Moved everything to lower case letters.
> >>
> >>
> >>> [Page 5], for "ADU Block", it would clearer to have Flow ID, Length
> >>> and
> >> Padding fields in parenthesis next to F[], L[], and Pad[] respectively=
.
> >>
> >> Done.
> >> I also realized we were using the term FID[i] twice to denote the
> >> F[i] field in section 4.3 "Source block creation".
> >> We corrected to use F[] throughout the document.
> >>
> >> NEW:
> >>  ADU Block:  a set of ADUs that are considered together by the
> >>      FECFRAME instance for the purpose of the FEC scheme.  Along with
> >>      the flow ID (F[]), length (L[]), and padding (Pad[]) fields, they
> >>      form the set of source symbols over which FEC encoding will be
> >>      performed.
> >>
> >>> [Page 5], after "FEC Framework Configuration Information" please add
> >> "(FFCI)".
> >>
> >> Done.
> >>
> >>
> >>> [Page 5], section 4.1, "G MUST be equal..", please define G in sectio=
n "3.2.
> >> Notations".
> >>
> >> Added.
> >>
> >>
> >>> [Page 9], last sentence, "Each ADUI contributes to exactly one
> >>> source symbol
> >> to the source block.", it is clearer to say "...of the source block."
> >>
> >> Done
> >>
> >>
> >>> [Page 15], Section 6.1.1, "(e.g., before versus after FEC
> >>> protection, and within
> >> the end-system versus in a middlebox)", please rephrase if possible,
> >> this is not very clear.
> >>
> >> Done.
> >>
> >> NEW:
> >>
> >>   (e.g., is encryption applied before or after FEC protection, within
> >> the end- system or in a middlebox)
> >>
> >>
> >>> [Page 19], reference [SIMPLE_RS] is now at version 03.
> >>
> >> Now in version -04. Updated.
> >>
> >>
> >>> [Page 19], reference [RFC5053]: title is missing "for Object Delivery=
"
> >>
> >> Exact! Fixed.
> >>
> >>
> >>> -Overall for clarity, please adapt one method for spelling out
> >>> acronyms
> >> (either in one section in intro, or throughout the text as they are
> >> first used; but not both).
> >>
> >> I think it's homogeneous now.
> >>
> >>
> >>> -Overall for clarity, some line feed would be useful in section 5.
> >>
> >> I've added the <?rfc rfcedstyle=3D"yes"?> magic directive, and now
> >> lists are much more readable.
> >> I've also changed the style of lists for "symbols", and it also helps
> >> making it more readable.
> >>
> >>>
> >>> Best Regards,
> >>> Meral
> >>>
> >>> ---
> >>> Meral Shirazipour
> >>> Ericsson Research
> >>> www.ericsson.com
> >>>
> >>> --
> >>
> >> Cheers,
> >>
> >>   Vincent, on behalf of the authors
> >


From meral.shirazipour@ericsson.com  Tue Oct  9 08:12:25 2012
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C61C21F8550 for <gen-art@ietfa.amsl.com>; Tue,  9 Oct 2012 08:12:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.028
X-Spam-Level: 
X-Spam-Status: No, score=-7.028 tagged_above=-999 required=5 tests=[AWL=-0.429, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 93g2op3okKWr for <gen-art@ietfa.amsl.com>; Tue,  9 Oct 2012 08:12:24 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 81A3E21F8480 for <gen-art@ietf.org>; Tue,  9 Oct 2012 08:12:24 -0700 (PDT)
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 q99FD2VT003750; Tue, 9 Oct 2012 10:13:08 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.205]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Tue, 9 Oct 2012 11:12:18 -0400
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "draft-ietf-fecframe-ldpc-all@tools.ietf.org" <draft-ietf-fecframe-ldpc-all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Date: Tue, 9 Oct 2012 11:12:17 -0400
Thread-Topic: Gen-ART Telechat Call review of draft-ietf-fecframe-ldpc-04
Thread-Index: Ac2mMHecExy41fJHSZO7kPcKxIFjkQ==
Message-ID: <25DC600D0CC1F2479C7053ADEB93004E6DF7D497BA@EUSAACMS0703.eamcs.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
Cc: "draft-ietf-fecframe-ldpc@tools.ietf.org" <draft-ietf-fecframe-ldpc@tools.ietf.org>, "fecframe-chairs@tools.ietf.org" <fecframe-chairs@tools.ietf.org>
Subject: [Gen-art] Gen-ART Telechat Call review of draft-ietf-fecframe-ldpc-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, 09 Oct 2012 15:12:25 -0000

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

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

Document: draft-ietf-fecframe-ldpc-04
Reviewer: Meral Shirazipour
Review Date: 2012-10-09
IETF LC End Date: 2012-10-01
IESG Telechat date: 2012-10-11

Summary: This draft is ready for publication as a Proposed Standard.

Major issues:
-none

Minor issues:
-none

Nits/editorial comments:
-none


Best Regards,
Meral
---
Meral Shirazipour
Ericsson Research
www.ericsson.com

From ron.even.tlv@gmail.com  Tue Oct  9 08:34:19 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 3F97011E8122; Tue,  9 Oct 2012 08:34:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5NtyCo0kLeGl; Tue,  9 Oct 2012 08:34:17 -0700 (PDT)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id EF06311E811B; Tue,  9 Oct 2012 08:34:14 -0700 (PDT)
Received: by mail-wg0-f44.google.com with SMTP id dr13so3201699wgb.13 for <multiple recipients>; Tue, 09 Oct 2012 08:34:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:x-mailer:thread-index:content-language; bh=0qVn/xc+rCq0iNf6yObispYPcD2cGMa2Hx5zaY+uFsU=; b=xrvcPi3JCSGRf0p8poYyCU2RVwiccYrG/xYGbcFSs7HYSG9ufpiOLjElfKEwS8eAv3 Q+ojDa06vjyVIoQ9sYIAf5y4UewzVzMVHgHkbqfVirsqpwfaDAD1wcTB2c3jW6aNdW1V 5XGwjxkB/lwzGc3RR/QBmU/Rt0s7oNa6xFEVdO85Z2s9iz9uq3WakZgSyhbuc1UWz5uq xcc5sWrDWwX5JOej/uiHtVL6Ip85ueys7B3gWQ017OfjEJU6AVjdqYeLr09jwkSgIkS/ dFXVpWY85+wGmF+u/3rA2kzGMqzRlbrGpuTv981imYN+me7uSCKT7o1MWudrkxcJq4Uq abRA==
Received: by 10.216.205.166 with SMTP id j38mr12921619weo.186.1349796854115; Tue, 09 Oct 2012 08:34:14 -0700 (PDT)
Received: from RoniE (bzq-79-176-243-9.red.bezeqint.net. [79.176.243.9]) by mx.google.com with ESMTPS id f1sm25382469wiy.2.2012.10.09.08.34.11 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 09 Oct 2012 08:34:13 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Malis, Andrew G \(Andy\)'" <andrew.g.malis@verizon.com>, <draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org>
References: <002101cd7997$a5204330$ef60c990$@gmail.com> <CC98C05A.2FC85%andrew.g.malis@one.verizon.com>
In-Reply-To: <CC98C05A.2FC85%andrew.g.malis@one.verizon.com>
Date: Tue, 9 Oct 2012 17:32:17 +0200
Message-ID: <011a01cda633$45b69930$d123cb90$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_011B_01CDA644.0940EFD0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKvrrCCYTySHJIE6oYZ/BaFSZDU3pXtCQqA
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-ccamp-rfc5787bis-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Oct 2012 15:34:19 -0000

This is a multipart message in MIME format.

------=_NextPart_000_011B_01CDA644.0940EFD0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Andy,

Thanks,

I am OK

Roni

 

From: Malis, Andrew G (Andy) [mailto:andrew.g.malis@verizon.com] 
Sent: 09 October, 2012 2:55 AM
To: Roni Even; draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org
Cc: ietf@ietf.org; gen-art@ietf.org; Malis, Andrew G (Andy)
Subject: Re: Gen-ART LC review of draft-ietf-ccamp-rfc5787bis-05

 

Roni,

 

Thanks for your review, and sorry for the delay on the response, but we've
also been working on incorporating other changes to the draft as well. 

 

To answer your question on section 6.1, that was a good catch. That should
have said "other than the first", rather than "preceding the first". This
will be corrected.

 

To answer your question on section 10, the text is repeated in the
subsections to make life easier for IANA, since they would probably have
replicated it themselves anyway in the three registry listings.

 

On your last comment, we agree with you that the more familiar reader will
not have a problem.

 

Thanks again,

Andy

 

From: Roni Even <ron.even.tlv@gmail.com>
Date: Monday, August 13, 2012 14:07 
To: "draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org"
<draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org>
Cc: "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Gen-ART LC review of draft-ietf-ccamp-rfc5787bis-05
Resent-To: <acee.lindem@ericsson.com>, Adrian Farrell <adrian@olddog.co.uk>,
Andrew Malis <andrew.g.malis@verizon.com>, <dbrungard@att.com>,
<dimitri.papadimitriou@alcatel-lucent.com>, <lberger@labn.net>

 

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-ccamp-rfc5787bis-05.

Reviewer: Roni Even

Review Date:2012-8-12

IETF LC End Date: 2012-8-17

IESG Telechat date:

 

Summary: This draft is almost ready for publication as a standard track RFC.

 

 

Major issues:

 

Minor issues:

In section 6.1 " If specified more than once, instances preceding the first
will be ignored and condition SHOULD be logged for possible action by the
network operator."  I am not sure what is meant by preceding the first.

 

 

Nits/editorial comments:

 

1.	The following note appears in section 10.1, 10.2 and 10.3. "Note
that the same values for the Inter-RA Export Upward sub-TLV and the Inter-RA
Export Downward Sub-TLV MUST be used when they appear in the Link TLV, Node
Attribute TLV, and Router Address TLV." - why not have it in section 10
before section 10.1.
2.	I saw in appendix  B that one of the changes from RFC 5787 was to
clarify the terminology before defining extensions, I would have found it
easier to read if the ASON hierarchy and the relation to OSPF in section 2
were presented in figures. This was more an issue to me as a reader not
familiar with the terminology and I would like to think that the more
familiar reader will not have problem.

 


------=_NextPart_000_011B_01CDA644.0940EFD0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:337274288;
	mso-list-template-ids:-764756284;}
@list l1
	{mso-list-id:715087181;
	mso-list-type:hybrid;
	mso-list-template-ids:-1205706658 -1668626108 67698713 67698715 =
67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-bidi-font-family:Calibri;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Andy,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Thanks,<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>I am =
OK<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Roni<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Malis, Andrew G (Andy) [mailto:andrew.g.malis@verizon.com] =
<br><b>Sent:</b> 09 October, 2012 2:55 AM<br><b>To:</b> Roni Even; =
draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org<br><b>Cc:</b> =
ietf@ietf.org; gen-art@ietf.org; Malis, Andrew G =
(Andy)<br><b>Subject:</b> Re: Gen-ART LC review of =
draft-ietf-ccamp-rfc5787bis-05<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'>Roni,<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'><o:p>&nbsp;</o:p></span></p></div><div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'>Thanks for your review, and sorry for the delay on =
the response, but we've&nbsp;also been working on incorporating other =
changes to the draft as =
well.&nbsp;<o:p></o:p></span></p></div></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'>To answer your question on section 6.1, that was a =
good catch. That should have said &quot;other than the first&quot;, =
rather than &quot;preceding the first&quot;. This will be =
corrected.<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'>To answer your question on section 10, the text is =
repeated in the subsections to make life easier for IANA, since they =
would probably have replicated it themselves anyway in the three =
registry listings.<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'>On your last comment, we agree with you that the =
more familiar reader will not have a =
problem.<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'>Thanks again,<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'>Andy<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'><o:p>&nbsp;</o:p></span></p></div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Tahoma","sans-ser=
if";color:black'>From: </span></b><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Tahoma","sans-ser=
if";color:black'>Roni Even &lt;<a =
href=3D"mailto:ron.even.tlv@gmail.com">ron.even.tlv@gmail.com</a>&gt;<br>=
<b>Date: </b>Monday, August 13, 2012 14:07 <br><b>To: </b>&quot;<a =
href=3D"mailto:draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org">draft-ietf=
-ccamp-rfc5787bis.all@tools.ietf.org</a>&quot; &lt;<a =
href=3D"mailto:draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org">draft-ietf=
-ccamp-rfc5787bis.all@tools.ietf.org</a>&gt;<br><b>Cc: </b>&quot;<a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&quot; &lt;<a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;, &quot;<a =
href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a>&quot; &lt;<a =
href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a>&gt;<br><b>Subject: =
</b>Gen-ART LC review of draft-ietf-ccamp-rfc5787bis-05<br><b>Resent-To: =
</b>&lt;<a =
href=3D"mailto:acee.lindem@ericsson.com">acee.lindem@ericsson.com</a>&gt;=
, Adrian Farrell &lt;<a =
href=3D"mailto:adrian@olddog.co.uk">adrian@olddog.co.uk</a>&gt;, Andrew =
Malis &lt;<a =
href=3D"mailto:andrew.g.malis@verizon.com">andrew.g.malis@verizon.com</a>=
&gt;, &lt;<a =
href=3D"mailto:dbrungard@att.com">dbrungard@att.com</a>&gt;, &lt;<a =
href=3D"mailto:dimitri.papadimitriou@alcatel-lucent.com">dimitri.papadimi=
triou@alcatel-lucent.com</a>&gt;, &lt;<a =
href=3D"mailto:lberger@labn.net">lberger@labn.net</a>&gt;<o:p></o:p></spa=
n></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'><o:p>&nbsp;</o:p></span></p></div><div><div><p =
class=3DMsoNormal><span style=3D'color:#08003F'>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></span></p><p class=3DMsoNormal><span =
style=3D'color:#08003F'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#08003F'>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>&nbsp;</span><span style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>Document: </span><span =
style=3D'color:#08003F'>draft-ietf-ccamp-rfc5787bis-05.<o:p></o:p></span>=
</p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>Reviewer: Roni Even</span><span =
style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>Review Date:2012&#8211;8&#8211;12</span><span =
style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>IETF LC End Date: 2012&#8211;8&#8211;17</span><span =
style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>IESG Telechat date:</span><span =
style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>&nbsp;</span><span style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>Summary: This draft is almost ready for publication as a standard =
track RFC.</span><span style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>&nbsp;</span><span style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>&nbsp;</span><span style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>Major issues:</span><span =
style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>&nbsp;</span><span style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>Minor issues:</span><span =
style=3D'color:#08003F'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#08003F'>In section 6.1 &#8220; If specified more than =
once, instances preceding the first will be ignored and condition SHOULD =
be logged for possible action by the network operator.&#8221;&nbsp; I am =
not sure what is meant by preceding the first.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#08003F'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>&nbsp;</span><span style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>Nits/editorial comments:</span><span =
style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>&nbsp;</span><span style=3D'color:#08003F'><o:p></o:p></span></p><ol =
style=3D'margin-top:0in' start=3D1 type=3D1><li class=3DMsoNormal =
style=3D'color:#08003F;mso-list:l1 level1 lfo3'>The following note =
appears in section 10.1, 10.2 and 10.3. &#8220;Note that the same values =
for the Inter-RA Export Upward sub-TLV and the Inter-RA Export Downward =
Sub-TLV MUST be used when they appear in the Link TLV, Node Attribute =
TLV, and Router Address TLV.&#8221; &#8211; why not have it in section =
10 before section 10.1.<o:p></o:p></li><li class=3DMsoNormal =
style=3D'color:#08003F;mso-list:l1 level1 lfo3'>I saw in appendix&nbsp; =
B that one of the changes from RFC 5787 was to clarify the terminology =
before defining extensions, I would have found it easier to read if the =
ASON hierarchy and the relation to OSPF in section 2 were presented in =
figures. This was more an issue to me as a reader not familiar with the =
terminology and I would like to think that the more familiar reader will =
not have problem.<o:p></o:p></li></ol><p class=3DMsoNormal><span =
style=3D'color:#08003F'>&nbsp;<o:p></o:p></span></p></div></div></div></b=
ody></html>
------=_NextPart_000_011B_01CDA644.0940EFD0--


From kathleen.moriarty@emc.com  Tue Oct  9 14:35:41 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 1BD7911E80E0; Tue,  9 Oct 2012 14:35:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.389
X-Spam-Level: 
X-Spam-Status: No, score=-2.389 tagged_above=-999 required=5 tests=[AWL=0.210,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ju21hPQfQkAp; Tue,  9 Oct 2012 14:35:40 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 285AD11E80DF; Tue,  9 Oct 2012 14:35:39 -0700 (PDT)
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 q99LZb8d007229 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Oct 2012 17:35:37 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd01.lss.emc.com [10.254.221.251]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Tue, 9 Oct 2012 17:35:31 -0400
Received: from mxhub14.corp.emc.com (mxhub14.corp.emc.com [128.222.70.235]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q99LZTYo009379; Tue, 9 Oct 2012 17:35:29 -0400
Received: from mx15a.corp.emc.com ([169.254.1.83]) by mxhub14.corp.emc.com ([128.222.70.235]) with mapi; Tue, 9 Oct 2012 17:35:28 -0400
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: "Black, David" <david.black@emc.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-storm-iscsi-cons.all@tools.ietf.org" <draft-ietf-storm-iscsi-cons.all@tools.ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Date: Tue, 9 Oct 2012 17:35:27 -0400
Thread-Topic: Gen-art review of draft-ietf-storm-iscsi-cons-06
Thread-Index: AQHNidZYJ+9C2EyAdkGmkvHgtBPaPJeMEQqQgCWA8nA=
Message-ID: <F5063677821E3B4F81ACFB7905573F2409595325@MX15A.corp.emc.com>
References: <F5063677821E3B4F81ACFB7905573F24057415D7@MX15A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE7120DCD1588@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7120DCD1588@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "cbm@chadalapaka.com" <cbm@chadalapaka.com>, "julians@infinidat.com" <julians@infinidat.com>, "julian@satran.net" <julian@satran.net>, "meth@il.ibm.com" <meth@il.ibm.com>
Subject: Re: [Gen-art] Gen-art review of draft-ietf-storm-iscsi-cons-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, 09 Oct 2012 21:35:41 -0000

Thank you for the clarification and to Mallikarjun for making the requested=
 updates to the latest version (-07).  I have looked through the document a=
nd agree that the comments have been addressed satisfactorily.  Not all of =
the nits were corrected, but the ones that were not were more of suggestion=
s.=20

Thank you!
Kathleen

-----Original Message-----
From: Black, David=20
Sent: Saturday, September 15, 2012 6:42 PM
To: Moriarty, Kathleen; gen-art@ietf.org; draft-ietf-storm-iscsi-cons.all@t=
ools.ietf.org; iesg@ietf.org
Cc: cbm@chadalapaka.com; julians@infinidat.com; julian@satran.net; meth@il.=
ibm.com; Black, David
Subject: RE: Gen-art review of draft-ietf-storm-iscsi-cons-06

Kathleen,

Thank you for the review.  I wanted to follow up on one of the comments
that could be more than editorial - the comment is in fact editorial,
which is how it was classified in the review:

> Section 3.5:
> Should the shall and shall not be in caps?

Nope - those words occur in text describing the ASCII-fied UML notation
used in this draft, so lower case is appropriate, as this draft is not
a normative specification of UML:

  The preceding diagram is an example where Class whole is an
  aggregate that contains Class part where Class part shall only
  belong to one Class whole, and the Class part shall not continue
  to exist if the Class whole is removed (i.e., read as "the whole
  contains the part").

For clarity, the "shall" on the second line should just be removed:
	shall only belong -> only belongs

Similarly, the "shall not" on the third line should be reworded:
	shall not continue to exist -> does not continue to exist

Thanks,
--David


> -----Original Message-----
> From: Moriarty, Kathleen
> Sent: Monday, September 03, 2012 9:17 AM
> To: gent-art@ietf.org; draft-ietf-storm-iscsi-cons.all@tools.ietf.org;
> iesg@ietf.org
> Cc: cbm@chadalapaka.com; julians@infinidat.com; julian@satran.net;
> meth@il.ibm.com; Black, David
> Subject: Gen-art review of draft-ietf-storm-iscsi-cons-06
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq> .
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document:  draft-ietf-storm-iscsi-cons-06
> Reviewer: Kathleen Moriarty
> Review Date: September 3, 2012
> IETF LC End Date:  Unsure, it was delayed
> IESG Telechat date: (if known)
>=20
> Summary:  draft-ietf-storm-iscsi-cons-06 combines and updates several RFC=
s.
> The document is ready with nits.
>=20
> This document describes a transport protocol for SCSI that works on top o=
f
> TCP. The iSCSI protocol aims to be fully compliant with the standardized =
SCSI
> Architecture Model (SAM-2).  This document obsoletes RFCs 3720, 3980, 485=
0 and
> 5048 by consolidating them into a single document and making additional
> updates to the consolidated specification. This document also updates RFC=
 3721
> and RFC 3723.
>=20
> Major issues:
>=20
> Minor issues:
>=20
> Nits/editorial comments:
> IDNits does not come up clean.  Please review the output and correct the
> updates/obsoletes as appropriate in the header.  IDnits is looking for RF=
C#
> and the draft just includes the #.  Additionally, Updates does not includ=
e
> RFC5048 and RFC4850 in the header.
>=20
> Section 2.3 first bullet:
> replace 'consolidated' with 'consolidates'
> bullet #8 - don't need a comma
>=20
> Section 3.5:
> Should the shall and shall not be in caps?
>=20
> Section 4.1:
> Second sentence: I believe "Section" should be lower case as it is not
> referring to a section number, but informally stating 'this section'.
>=20
>=20
> Section 4.2.2.3.4.:
> Reword first sentence, should snot end with 'with'.
>=20
>=20
> Section 9.2, 4th paragraph, for consistency with similar section referenc=
es
> start in this section and continue through the document.  In most cases, =
there
> is a dash with a space after a section number.  If that is the preferred
> format for consistency, here are a few places this shows up, although a s=
earch
> should be made to make this consistent.
> "12.1.3- "Challenge" should be "12.1.3 - "Challenge"
> and in paragraph 5:
> "12.1.2- "Secure" should be "12.1.2 - "Secure"
> Section 9.2.1, forth paragraph:"12.1.3-" should be "12.1.3 -"
> Section 10 contains more examples that do not contain a space, so the bet=
ter
> approach may be to change the ones with a space to no space after the sec=
tion
> number.
> Section 11.3.6 - goes back to using a space following the section number
> reference.
>=20
> Section 14, #3, I don't think it is necessary to say "under the new IETF
> Review registration procedures", rather just, "under the IETF Review
> registration procedures".  They could change again.
>=20
> Thank you,
> Kathleen

From wassim.haddad@ericsson.com  Wed Oct 10 05:25:35 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 107DC21F86CE for <gen-art@ietfa.amsl.com>; Wed, 10 Oct 2012 05:25:35 -0700 (PDT)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SuJ-ZVWNL9D6 for <gen-art@ietfa.amsl.com>; Wed, 10 Oct 2012 05:25:34 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 7816F21F86C9 for <gen-art@ietf.org>; Wed, 10 Oct 2012 05:25:34 -0700 (PDT)
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 q9ACQPQU019212; Wed, 10 Oct 2012 07:26:26 -0500
Received: from [164.48.125.59] (147.117.20.214) by eusaamw0712.eamcs.ericsson.se (147.117.20.182) with Microsoft SMTP Server id 8.3.279.1; Wed, 10 Oct 2012 08:25:27 -0400
From: Wassim Haddad <wassim.haddad@ericsson.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 10 Oct 2012 13:25:25 +0100
Message-ID: <ABF9F1B9-9BBD-457E-88CC-52D79DB0F340@ericsson.com>
To: Gen-art <gen-art@ietf.org>
MIME-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
Cc: draft-ietf-manet-olsrv2.all@tools.ietf.org
Subject: [Gen-art]  Gen-ART Review of draft-ietf-manet-olsrv2-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: Wed, 10 Oct 2012 12:25:35 -0000

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

Document: draft-ietf-manet-olsrv2-16
Reviewer:  Wassim Haddad
Review Date:  10 Oct 2012
IETF LC End Date: 22 Aug 2012
IETF Telechat Date: 11 Oct 2012

Summary:  This draft is ready for publication as proposed standard.

- Major Issues: None

- Minor Issues: None


Regards,

Wassim H.


From mahoney@nostrum.com  Thu Oct 11 14:46:14 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 F0B3C11E8097 for <gen-art@ietfa.amsl.com>; Thu, 11 Oct 2012 14:46:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IB8jhH3S3CcM for <gen-art@ietfa.amsl.com>; Thu, 11 Oct 2012 14:46:14 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 6077D21F852D for <gen-art@ietf.org>; Thu, 11 Oct 2012 14:46:14 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local ([4.30.77.1]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id q9BLkBRX012003 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 11 Oct 2012 16:46:11 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <50773E23.8090508@nostrum.com>
Date: Thu, 11 Oct 2012 16:46:11 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:15.0) Gecko/20120907 Thunderbird/15.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: 4.30.77.1 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2012-10-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: Thu, 11 Oct 2012 21:46:15 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end        Draft

Mary Barnes       2012-10-19    draft-ietf-ccamp-gmpls-ted-mib-14 *

Martin Thomson    2012-10-19    draft-ietf-appsawg-media-type-suffix-regs-06 *

Meral Shirazipour 2012-11-02    RFC 5011 **

Miguel Garcia     2012-10-22    draft-ietf-fecframe-simple-rs-04

Peter McCann      2012-10-22    draft-ietf-storm-iser-12

Peter Yee         2012-10-22    draft-ietf-nfsv4-federated-fs-protocol-13

Richard Barnes    2012-10-22    draft-ietf-mediactrl-mrb-15

Roni Even         2012-11-06    draft-leiba-5322upd-from-group-06

Vijay Gurbani     2012-10-23    draft-ietf-precis-problem-statement-08

Wassim Haddad     2012-10-24    draft-ietf-xrblock-rtcp-xr-delay-10

* On the Oct 25 telechat

I have made the assignments in the review tool:
** except for RFC 5011, which isn't in the review tool queue
http://art.tools.ietf.org/tools/art/genart/

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


The standard template is included below.

Thanks,

Jean

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

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

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

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

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

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

From martin.thomson@gmail.com  Fri Oct 12 11:58:35 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 BC7AA21F859A for <gen-art@ietfa.amsl.com>; Fri, 12 Oct 2012 11:58:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.899
X-Spam-Level: 
X-Spam-Status: No, score=-4.899 tagged_above=-999 required=5 tests=[AWL=0.700,  BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MlMMQ+du85Ww for <gen-art@ietfa.amsl.com>; Fri, 12 Oct 2012 11:58:35 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 81F6A21F8574 for <gen-art@ietf.org>; Fri, 12 Oct 2012 11:58:34 -0700 (PDT)
Received: by mail-lb0-f172.google.com with SMTP id k13so2525645lbo.31 for <gen-art@ietf.org>; Fri, 12 Oct 2012 11:58:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=u4YTPD6VzCaGTrqM94Wk4uve851K17W46D/PoXh+vqU=; b=CSLw53QsyGH6acAiNejiwYbMx1+HWCIMRS/w2XYq+C6n8hoKuEUG1RJVpnJJBYCv5/ u8mXi74TRJK+yqLZbq0wn3nka8BuXjeGA0h+r4afhE7bHHrr806VbWeKEYwGMQzvJZmN +Gr6blUkQOWyZbw9CDAtz9bq95Sc/qVNOQ28SlCBLVmxt3biud/ECh9xeNDqtpnA4gjs vYGuaH23JPZrqphhg0N68g6uIM9+9tofJfkwknMnE0bv+gdrFxR7k3ysR6GKfROj/qG4 kN+901CKN+Rlc4UgqLbwsnRt7nKa2tXg7b1pD3ok9FH4U6BPNPRTSCc2NfcVkuI1tE3W pQXw==
MIME-Version: 1.0
Received: by 10.112.47.228 with SMTP id g4mr1897421lbn.21.1350068313500; Fri, 12 Oct 2012 11:58:33 -0700 (PDT)
Received: by 10.112.83.2 with HTTP; Fri, 12 Oct 2012 11:58:33 -0700 (PDT)
In-Reply-To: <CABkgnnU7--Ad+YU3_puVkVfsoAjRCrqn0wd7BJ5j+GBWwPVcuw@mail.gmail.com>
References: <CABkgnnU7--Ad+YU3_puVkVfsoAjRCrqn0wd7BJ5j+GBWwPVcuw@mail.gmail.com>
Date: Fri, 12 Oct 2012 11:58:33 -0700
Message-ID: <CABkgnnUbBZpN1KHxzW91WGrPGhi2Dd=mNSaeUM=xRi1Weonagw@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: gen-art@ietf.org, draft-snell-http-prefer.all@tools.ietf.org
Content-Type: text/plain; charset=UTF-8
Subject: Re: [Gen-art] Gen-ART review of draft-snell-http-prefer-14
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Oct 2012 18:58:35 -0000

I have reviewed -15 of this draft and my major issues have been
resolved.  This document is ready.

On 21 September 2012 16:43, Martin Thomson <martin.thomson@gmail.com> wrote:
> Lucky you.  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-http-prefer-14
> Reviewer: Martin Thomson
> Review Date: 2012-09-21
> IETF LC End Date: 2012-10-12
>
> Summary: This document is in pretty good shape.  I have a concern over
> how Prefer: wait might be implemented that I believe needs to be
> addressed prior to publication as Proposed Standard.  There are also a
> number of additional concerns, though nothing particularly serious.
>
> Major issues:
>
> Section 3.4 specifies timing requirements that a server has to act
> upon with no good way of gaining the information it needs.  It assumes
> clock synchronization. Given that terrible clock synchronization is
> the default mode of operation for internet hosts, this seems to be a
> poor choice.
>
> In any case, this design forces a server to wait less than the allowed
> time in all cases, but gives the server no good information to choose
> an appropriate time adjustment.  A server has to assume that the
> client has already expended some period waiting.  Assuming that the
> client is going to abandon the request at the identified time, then
> the server is obliged to wait less than the entire period, lest the
> response be wasted.  Even if we assume that clocks are synchronized,
> the resolution of Date and wait are capped at a second, so worst case
> we have a 1 second window of uncertainty on when the request was sent.
>  This is worse if there are clock errors, particularly if the client
> clock runs ahead of the server.
>
> I can't see how I would implement this feature so that it behaves
> reliably for arbitrary hosts.
>
> On the other hand, the client has the ability to make its own
> determination about clock synchronization and network transit delays.
> A single request with wait=0 would provide a good measurement of total
> non-server delays, without any quantization noise (Date is rounded or
> trimmed to the second, which makes this determination difficult).  The
> client could then adjust the value of the wait preference to account
> for what it learns, with the server being able to then concentrate on
> the time elapsed between receipt and sending.  Clock differences are
> then irrelevant.
>
> Minor comments:
>
> In Section 3.2:
>
>    When honoring the "return-representation" preference, the server MUST
>    include a Content-Location header field specifying the URI of the
>    resource representation being returned.
>
> This is a requirement that could be inadvertently violated by servers.
>  This really isn't what you are intending here.  The idea is to ensure
> that the returned representation doesn't get mistaken for a
> representation of the request URI, *when it is not*.  This does not
> require 2119 language to convey, though I would agree that a reminder
> is necessary here.  How about:
>
>    The returned representation might not be a representation for the
> effective request
>    URI [[this is the term du jour, I believe]] when the request
> affects another resource.
>    The Content-Location header can be used to identify the URI of the returned
>    representation.
>
> (I'd note that return-representation is less useful for PUT than POST
> or PATCH.  You don't mention PATCH at all.)
>
> In Sections 3.2 and 3.3, the mutual exclusivity of these parameters is
> handled differently to the strict/lenient parameters.  Instead of all
> the 2119 stuff, how about:
>
>    The "return-minimal" and "return-representation" preferences are
>    mutually exclusive directives.  A request that contains both preferences
>    can be treated as though neither were specified.
>
> Alternatively, did you consider specifying a single preference here?
> i.e., Prefer: return=minimal and Prefer: return=representation
>
> Section 3.5, is it useful to observe that the "strict" preference is
> useful for ensuring that all aspects of a request are handled, so that
> recoverable errors don't result in important parts of a request being
> "missed" by a server?
>
> Did you consider a single preference here?  i.e., Prefer:
> processing=strict or Prefer: processing=lenient
>
> Regarding Section 3.5, which do we assume to be the existing behavior
> for a server?  strict or lenient?
>
> I'd ask an IANA considerations expert to look at Section 4.1.  Did you
> want something other than the strict letter of "Specification
> Required"?
>
> Nits:
>
> The wording of Section 2.1 is a little contorted.  The second
> paragraph is a single sentence.  "event just potentially" is a little
> redundant.  Suggest a reword to cover just the key points:
>  - Prefer is not intended to affect content negotiation.
>  - If a preference could affect what a cache stores or how it stores
> it [httpbis-p6], then the server MUST use Vary: Prefer.  This applies
> even if the request does not include Prefer.
> Caution is always good, but advising its application doesn't improve
> the probability of it being applied.
>
> Example 3 in Section 2.2 implies semantics for the undefined "status"
> argument.  Doing this begs the question about whether this should have
> been specified.  Rather than invite such questions, try using a
> generic argument with a nonsensical name.  (Priority in the previous
> example is OK, because it's inherently meaningless anyway.)
>
> You have a few references that aren't really necessary.  I don't see
> much relevance in httpbis-p7, for example.

From david.black@emc.com  Mon Oct 15 16:10:49 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 1556D1F0381; Mon, 15 Oct 2012 16:10:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.56
X-Spam-Level: 
X-Spam-Status: No, score=-102.56 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fZUtUaVgLuuL; Mon, 15 Oct 2012 16:10:48 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id E87021F042A; Mon, 15 Oct 2012 16:10:47 -0700 (PDT)
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 q9FNAi2T011614 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Oct 2012 19:10:44 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.129]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Mon, 15 Oct 2012 19:10:30 -0400
Received: from mxhub36.corp.emc.com (mxhub36.corp.emc.com [10.254.93.84]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q9FNASNs008636; Mon, 15 Oct 2012 19:10:28 -0400
Received: from mx15a.corp.emc.com ([169.254.1.83]) by mxhub36.corp.emc.com ([::1]) with mapi; Mon, 15 Oct 2012 19:10:28 -0400
From: "Black, David" <david.black@emc.com>
To: "yiu_lee@cable.comcast.com" <yiu_lee@cable.comcast.com>, "roberta.maglione@telecomitalia.it" <roberta.maglione@telecomitalia.it>, "carlw@mcsr-labs.org" <carlw@mcsr-labs.org>, "christian.jacquenet@orange.com" <christian.jacquenet@orange.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Date: Mon, 15 Oct 2012 19:10:27 -0400
Thread-Topic: Gen-ART review of draft-ietf-softwire-dslite-deployment-06
Thread-Index: Ac2rKkPgDErjXyHISiSTlQ/jGKFZIg==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7120DFAEF29@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "softwires@ietf.org" <softwires@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: [Gen-art] Gen-ART review of draft-ietf-softwire-dslite-deployment-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: Mon, 15 Oct 2012 23:10:49 -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-softwire-dslite-deployment-06
Reviewer: David L. Black
Review Date: October 15, 2012
IETF LC End Date: October 16, 2012
IESG Telechat Date: October 25, 2012

Summary:

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

This is a generally well-written draft that expands considerably on the bri=
ef
deployment considerations for DS-Lite in Appendix A of RFC 6333.  The draft
is clear and reasonably well-written, and a significant improvement on that
RFC 6333 Appendix, although an understanding of RFC 6333 is necessary to
understand this draft, which seems completely reasonable.

The B4 and AFTR acronyms are clever - kudos to whomever came up with those.

I found five open issues, all of which are minor.

Minor Issues:

[1] Ironically, the first issue is that something should be said about
the relationship of this draft to Appendix A of RFC 6333.  It probably
suffices to say that this draft expands on the material in that Appendix,
as I see no need to specify that this draft updates RFC 6333 solely to
change non-normative material in an Appendix.

[2] The MTU increase technique in Section 2.2 is a "may", which is
consistent with Section 5.3 of RFC 6333.  OTOH, Section 2.2 of this
draft should also discuss the AFTR resource exhaustion concern that
described in Section 6.3 of RFC 6333, as that is a potential
operational reason for an ISP to increase MTU size (e.g., if customer
sourcing of large IPv4 packets is not sufficiently rare).

[3] Section 2.7 refers to "the AFTR's internal interface".  There may be
two internal interfaces, the physical IPv6 interface (outer header) and
the tunnel's IPv4 interface (inner header).  The text should be clarified
to indicate which interface is involved - it appears that the AFTR's
physical IPv6 interface is intended in this section.

[4] Section 2.7 cites RFC 6333 for use of DHCPv6 with DS-Lite.  RFC 6334
should be cited - either in addition to or instead of RFC 6333.

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

Nits:

Section 2.3 on MTU Considerations could usefully mention MTU discovery
techniques, as possibilities for customer IPv4 traffic to adapt to a
smaller IPv4 MTU.  If this is done, it would be useful to mention
RFC 4821 in addition to the mention of RFC 1191 in RFC 6333.

Section 2.4 should define "lawful intercept".  It would be helpful to
cite a reference for this concept if something appropriate can be found.

Section 2.5:
- Are one or both types of logging recommended?
- Last paragraph on p.4, "timestamped log" is not a good verb phrase.
	"maintain a timestamped log of" would be a better replacement.
- Last paragraph in section, where is the batch file sent?

In Section 2.7, I'm having a hard time understanding which traffic is
intended to be subject to the Outgoing Policies and the Incoming Policies.
Expanding each of those two bullets to explain what traffic is subject
to each class of policies would help.

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

idnits 2.12.13 found a tiny nit - draft-ietf-pcp-base is now at
version 28.

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 vkg@bell-labs.com  Tue Oct 16 06:28:05 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 601D321F897F for <gen-art@ietfa.amsl.com>; Tue, 16 Oct 2012 06:28:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.17
X-Spam-Level: 
X-Spam-Status: No, score=-107.17 tagged_above=-999 required=5 tests=[AWL=-0.571, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kgmEZBgq3gP0 for <gen-art@ietfa.amsl.com>; Tue, 16 Oct 2012 06:28:04 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 33ED921F898A for <gen-art@ietf.org>; Tue, 16 Oct 2012 06:28:04 -0700 (PDT)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id q9GDS2gZ016236 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 16 Oct 2012 08:28:02 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q9GDS0bB007112 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 16 Oct 2012 08:28:00 -0500
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q9GDRuBa019769; Tue, 16 Oct 2012 08:27:56 -0500 (CDT)
Message-ID: <507D6117.9000003@bell-labs.com>
Date: Tue, 16 Oct 2012 08:28:55 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20120605 Thunderbird/13.0
MIME-Version: 1.0
To: draft-ietf-precis-problem-statement@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.10
Cc: Marc.Blanchet@viagenie.ca, General Area Review Team <gen-art@ietf.org>, yoshiro.yoneya@jprs.co.jp, presnick@qti.qualcomm.com
Subject: [Gen-art] Gen-ART review of draft-ietf-precis-problem-statement-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, 16 Oct 2012 13:28: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-precis-problem-statement-08
Reviewer: Vijay K. Gurbani
Review Date: Oct-16-2012
IETF LC End Date: Oct-23-2012
IESG Telechat date: Not known

Summary: This draft is ready as an Informational.

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 vkg@bell-labs.com  Tue Oct 16 07:24:16 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 CF21D21F8753 for <gen-art@ietfa.amsl.com>; Tue, 16 Oct 2012 07:24:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.043
X-Spam-Level: 
X-Spam-Status: No, score=-109.043 tagged_above=-999 required=5 tests=[AWL=1.556, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YMigDa8OaJV1 for <gen-art@ietfa.amsl.com>; Tue, 16 Oct 2012 07:24:16 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 0114921F8748 for <gen-art@ietf.org>; Tue, 16 Oct 2012 07:24:15 -0700 (PDT)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id q9GENjk8008803 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 16 Oct 2012 09:23:46 -0500 (CDT)
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 q9GENi4x004979 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 16 Oct 2012 09:23:45 -0500
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q9GENgfx025309; Tue, 16 Oct 2012 09:23:42 -0500 (CDT)
Message-ID: <507D6E29.5050801@bell-labs.com>
Date: Tue, 16 Oct 2012 09:24:41 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20120605 Thunderbird/13.0
MIME-Version: 1.0
To: draft-ietf-pkix-rfc5280-clarifications@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Cc: General Area Review Team <gen-art@ietf.org>, Stephen Kent <kent@bbn.com>
Subject: [Gen-art] Gen-ART review of draft-ietf-pkix-rfc5280-clarifications-10
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, 16 Oct 2012 14:24: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 resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-pkix-rfc5280-clarifications-10
Reviewer: Vijay K. Gurbani
Review Date: Oct-16-2012
IETF LC End Date: Not known
IESG Telechat date: Oct-25-2012

This document is ready as a Proposed Standard.

Major: 0
Minor: 0
Nits: 2

Nits:

- S1: The fourth paragraph should be put right underneath the second
  paragraph since the former continues discussion started by the latter.

- S1: Last paragraph --- it will be good to provide some documentation
  regarding the "observed attacks".  Especially a link to relevant papers
  of archival quality discussing the attacks will be helpful.  If the
  attacks are related to the Diginotar and Comodo break-ins, then there
  is an archival paper [1] at a reasonably high level from IEEE that
  discusses this and provides a starting point for those who want to
  learn more.

[1] Neal Leavitt, "Internet security under attack: The undermining of
  digital certificates," pp. 17-20, IEEE Computer, December 2011.

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 mahoney@nostrum.com  Tue Oct 16 14:10:50 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 8587621F86C5 for <gen-art@ietfa.amsl.com>; Tue, 16 Oct 2012 14:10:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.592
X-Spam-Level: 
X-Spam-Status: No, score=-2.592 tagged_above=-999 required=5 tests=[AWL=0.008,  BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sq30eUQNOatV for <gen-art@ietfa.amsl.com>; Tue, 16 Oct 2012 14:10:49 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 88EDB21F86C4 for <gen-art@ietf.org>; Tue, 16 Oct 2012 14:10:49 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-57-93-208.dllstx.fios.verizon.net [173.57.93.208]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id q9GLAmgN068165 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Tue, 16 Oct 2012 16:10:48 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <507DCD58.3030204@nostrum.com>
Date: Tue, 16 Oct 2012 16:10:48 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:15.0) Gecko/20120907 Thunderbird/15.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.93.208 is authenticated by a trusted mechanism)
Subject: [Gen-art] Assignments for the 2012-10-25 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: Tue, 16 Oct 2012 21:10:50 -0000

Hi all,

Note: Since these assignments are being made two days before the 
telechat agenda
       is finalized, please consider this list a first pass. Other 
documents may
       be added to the agenda between now and Thursday afternoon CDT.
       You can follow the agenda here: 
https://datatracker.ietf.org/iesg/agenda/

The following reviewers have assignments:

Reviewer             LC end       Draft

David Black          2012-10-16   draft-ietf-softwire-dslite-deployment-06 **

Francis Dupont       2012-10-17   draft-ietf-dhc-client-id-06

Joel Halpern         2012-10-17   draft-ietf-softwire-stateless-4v6-motivation-04 **

Mary Barnes          2012-10-19   draft-ietf-ccamp-gmpls-ted-mib-14

Martin Thomson       2012-08-13   draft-ietf-storm-iscsi-sam-06 **, ***
Martin Thomson       2012-10-19   draft-ietf-appsawg-media-type-suffix-regs-06
Martin Thomson       2012-10-12   draft-snell-http-prefer-15 *

Roni Even            2012-08-17   draft-ietf-ccamp-rfc5787bis-06 *

Vijay Gurbani        2012-09-05   draft-ietf-pkix-rfc5280-clarifications-10 **

Wassim Haddad        2012-10-04   draft-ietf-geopriv-local-civic-07

* Earlier draft reviewed
** Already reviewed
*** This document is in the "For Action" state on the agenda,
     which is a rather unusual state. Please check
     https://datatracker.ietf.org/iesg/agenda/ for updates.

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

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

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

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

Jean

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

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

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

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

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

From martin.thomson@gmail.com  Tue Oct 16 14:48:03 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 0138B21F8775 for <gen-art@ietfa.amsl.com>; Tue, 16 Oct 2012 14:48:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.878
X-Spam-Level: 
X-Spam-Status: No, score=-3.878 tagged_above=-999 required=5 tests=[AWL=-0.279, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id baUxvrYF35An for <gen-art@ietfa.amsl.com>; Tue, 16 Oct 2012 14:48:02 -0700 (PDT)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0763D21F8773 for <gen-art@ietf.org>; Tue, 16 Oct 2012 14:48:01 -0700 (PDT)
Received: by mail-la0-f44.google.com with SMTP id b11so5140412lam.31 for <gen-art@ietf.org>; Tue, 16 Oct 2012 14:48:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=o3Vivqq5MxRVbXBtnOwx/8pQ054cdcGF5TLTDFZQHBI=; b=eA4xW3cD4y80hsoUyCuDlhR9KPYDlnXCk1r1V0X8ErR5gZJFQEgH7Z6S4XdUazxsYv Cd6J8A7kGjMk0ex0jU77vhhtuzrnN33ufhxLG6wvIQGtmBco20W/7qi+KofGnNktpzuh bb9gEozb5QBWO7GRgZUZYvkddGKfxibkRsSPWMg+kVH2ke9GSZRuUJVV/fcYKvkj6SPs KckytbMBF8w1ljI7XRGL1D97tEhVFdJvEsUk2hTtLtPdBirmkE6aKENmPZTwBbJfVuRX bz5SDdaoUdfr+r0zs0ERBKX5Oe9Fvrmdhngk9tLYemaSFX4PR2X+XI8IPfkLs3ny+tLZ Jmrw==
MIME-Version: 1.0
Received: by 10.112.102.132 with SMTP id fo4mr5837226lbb.111.1350424080957; Tue, 16 Oct 2012 14:48:00 -0700 (PDT)
Received: by 10.112.83.2 with HTTP; Tue, 16 Oct 2012 14:48:00 -0700 (PDT)
Date: Tue, 16 Oct 2012 14:48:00 -0700
Message-ID: <CABkgnnX11-NWygv3xzzcVRs=-nUJH7xb3N7VfrhKyq517kC-MA@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: gen-art@ietf.org,  draft-ietf-appsawg-media-type-suffix-regs.all@tools.ietf.org
Content-Type: text/plain; charset=UTF-8
Subject: [Gen-art] Gen-ART review of draft-ietf-appsawg-media-type-suffix-regs-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, 16 Oct 2012 21:48:03 -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-appsawg-media-type-suffix-regs-06
Reviewer: Martin Thomson
Review Date: 2012-10-16
IETF LC End Date: 2012-10-19
IESG Telechat date: 2012-10-25

Summary: This document is ready for publication as a (?) RFC.

Minor issues: Is BCP status really appropriate?  Informational seems
more appropriate for this sort of document.  The choice of providing a
modicum of guidance in Section 2, as opposed to in the RFC that
establishes the registry, could suggest this status, but that seems a
bit weak as motivation.

Nits:

+der doesn't even make a passing reference to +ber.  That's odd, since
one describes a subset of the other.

Mention of schema for +der and +ber doesn't seem relevant to the key
security consideration: that structures can be nested indefinitely.
This is possible regardless of what the schema says - a generic
processor is more likely to fall victim in that regard.

From mary.ietf.barnes@gmail.com  Tue Oct 16 14:57:16 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 2844721F86BB for <gen-art@ietfa.amsl.com>; Tue, 16 Oct 2012 14:57:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.382
X-Spam-Level: 
X-Spam-Status: No, score=-103.382 tagged_above=-999 required=5 tests=[AWL=0.216, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K4cmCRyY4u3H for <gen-art@ietfa.amsl.com>; Tue, 16 Oct 2012 14:57:15 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3B6C421F867A for <gen-art@ietf.org>; Tue, 16 Oct 2012 14:57:15 -0700 (PDT)
Received: by mail-lb0-f172.google.com with SMTP id k13so5206012lbo.31 for <gen-art@ietf.org>; Tue, 16 Oct 2012 14:57:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=cN14AMWj9ZETuS7z5jhZqFBNo7eSC1ppTB6Z1//2DbQ=; b=OvTaQsYtP//62lFuzefxw0OOm7GBSULt6ZB8ZUHrg18cUTIqJi+PYXQbTqJSwOqx8K YHVq8Ny4lllCh/8pFc8MfFmNsObLRY4l2WsljPYZgOjyM8BBT1wKmbUo13f+wH9an6Fi jzAgA26cuKXtcFcDawPqywWokg/d9Zx3332q+A9ipoiJh2dGxg/srzRSqxyfmnxaN2eT kCq/Lw3SfGWW1lqCRR0gEHYrqOG1OMct/zAeGS9kMs/hPKvzlckv1b9kCy01SN2zjQZA spw4IwloZVoYdOIyt+vuk6xkvkwrq1ObjydNGGbEbB01CXPMd7EPwEmZ837XjeEPlbRs m65g==
MIME-Version: 1.0
Received: by 10.112.39.138 with SMTP id p10mr6012079lbk.54.1350424634202; Tue, 16 Oct 2012 14:57:14 -0700 (PDT)
Received: by 10.114.69.139 with HTTP; Tue, 16 Oct 2012 14:57:14 -0700 (PDT)
Date: Tue, 16 Oct 2012 16:57:14 -0500
Message-ID: <CAHBDyN5VK2MyxSZ-Da1yxeFQnZDrZbGnv8CHARNGCLO3SiP1hA@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: draft-ietf-ccamp-gmpls-ted-mib.all@tools.ietf.org
Content-Type: multipart/alternative; boundary=485b390f7ac49e1bfd04cc343cc1
Cc: gen-art@ietf.org
Subject: [Gen-art] Gen-ART LC Review: draft-ietf-ccamp-gmpls-ted-mib-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: Tue, 16 Oct 2012 21:57:16 -0000

--485b390f7ac49e1bfd04cc343cc1
Content-Type: text/plain; charset=ISO-8859-1

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-ccamp-gmpls-ted-mib-14
Reviewer:  Mary Barnes
Review Date:  17 Oct 2012
IETF LC End Date: 19 Oct 2012
IESG Telechat Date: 25 Oct 2012

Summary:  Ready.

Caveat: I am not a MIB expert and assume that the mib doctor review has
ensured that aspect of the document is correct.

Nits:
-----
- there are a number of unused references that can likely be removed.

--485b390f7ac49e1bfd04cc343cc1
Content-Type: text/html; charset=ISO-8859-1
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-ccamp-gmpls-ted-mib-14</div><div>R=
eviewer: =A0Mary Barnes=A0</div><div>Review Date: =A017 Oct 2012</div><div>=
IETF LC End Date: 19 Oct 2012</div><div>IESG Telechat Date: 25 Oct 2012</di=
v>
<div><br></div><div>Summary: =A0Ready.</div><div><br></div><div>Caveat: I a=
m not a MIB expert and assume that the mib doctor review has ensured that a=
spect of the document is correct.</div><div><br></div><div>Nits:</div><div>
-----</div><div>- there are a number of unused references that can likely b=
e removed.=A0</div>

--485b390f7ac49e1bfd04cc343cc1--

From ron.even.tlv@gmail.com  Wed Oct 17 02:59:38 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 C43CC21F87E8; Wed, 17 Oct 2012 02:59:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GU8HNmB6G-HD; Wed, 17 Oct 2012 02:59:37 -0700 (PDT)
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by ietfa.amsl.com (Postfix) with ESMTP id 35B8A21F87B8; Wed, 17 Oct 2012 02:59:37 -0700 (PDT)
Received: by mail-wi0-f178.google.com with SMTP id hr7so345936wib.13 for <multiple recipients>; Wed, 17 Oct 2012 02:59:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; bh=lv3+m4lyJZ+XxnK3cbQ+l0HL+WVvDL7cbZq4IJ+ZdNA=; b=j0OEdNZbYF5ZMR/65mS0FuHlBaG2WB9eS6xNtIpgzCJu4hxuANSaKST8P9G38nmhum sSUkM/SzI3vjzAgR6Szocd/3rOXqlrnMJFQ2qOxzOB9iyGInV1Tj+BKJ9CneMeEvlm5g djVF/eiYuuXhX+VrDip/doqojITF4S6N5xV2z0Sx1MjaV7toSet4mu7PlGhL4CJt+6O5 +3cse2nPaWEd6fu3xCFCblJzPw2wEOaxCWnd+ZDUqK1dwDojolz1QpdkXeN6rZqNSLZ2 jUgwv+x6tIj+WjMhqRgfLQcAQB8Y2avZmi4PWTfqq8qM0AiakT6VtXgdnROXxydA2yRB asTA==
Received: by 10.180.84.41 with SMTP id v9mr2987398wiy.8.1350467976392; Wed, 17 Oct 2012 02:59:36 -0700 (PDT)
Received: from RoniE (bzq-79-176-243-9.red.bezeqint.net. [79.176.243.9]) by mx.google.com with ESMTPS id cl8sm23567588wib.10.2012.10.17.02.59.33 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 17 Oct 2012 02:59:35 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-leiba-5322upd-from-group.all@tools.ietf.org>
Date: Wed, 17 Oct 2012 11:57:22 +0200
Message-ID: <010301cdac4d$cfa70060$6ef50120$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0104_01CDAC5E.93306CA0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac2sTc0q0twAdGB/TEqBQ74s7zgemw==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART LC review of draft-leiba-5322upd-from-group-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, 17 Oct 2012 09:59:38 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0104_01CDAC5E.93306CA0
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-leiba-5322upd-from-group-06

Reviewer: Roni Even

Review Date:2012-10-17

IETF LC End Date: 2012-11-6

IESG Telechat date:

 

Summary: This draft is almost ready for publication as a standard track RFC.

 

 

Major issues:

 

Minor issues:

1.	It is not clear from the draft what the use case for using the group
construct is.  Section 3 talks about the issues with using the group
construct and recommend limited use, but this is the only information.
2.	Section 2.1 says "If the sender field uses group syntax, the group
MUST NOT contains more than one mailbox."  Why use a group name for a single
mailbox?

 

Nits/editorial comments:

 


------=_NextPart_000_0104_01CDAC5E.93306CA0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:37364675;
	mso-list-type:hybrid;
	mso-list-template-ids:-1149338328 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK1"></a><a name=3D"OLE_LINK2">I am the assigned Gen-ART =
reviewer for this draft. For background on Gen-ART, please see the FAQ =
at &lt;</a><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Please resolve these comments along with any other =
Last Call comments you may receive.<o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span style=3D'font-family:"Courier =
New"'>draft-leiba-5322upd-from-group-06</span><o:p></o:p></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;10&#8211;17<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2012&#8211;11&#8211;6<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 almost ready for publication as</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'> a =
standard track </span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>RFC</span><=
span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>.<o:p></o:p=
></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><ol style=3D'margin-top:0in' start=3D1 =
type=3D1><li class=3DMsoNormal style=3D'mso-list:l0 level1 lfo1'>It is =
not clear from the draft what the use case for using the group construct =
is.&nbsp; Section 3 talks about the issues with using the group =
construct and recommend limited use, but this is the only =
information.<o:p></o:p></li><li class=3DMsoNormal style=3D'mso-list:l0 =
level1 lfo1'>Section 2.1 says &#8220;If the sender field uses group =
syntax, the group MUST NOT contains more than one mailbox.&#8221;&nbsp; =
Why use a group name for a single mailbox?<o:p></o:p></li></ol><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0104_01CDAC5E.93306CA0--


From ron.even.tlv@gmail.com  Wed Oct 17 03:03:21 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 4706D21F881E; Wed, 17 Oct 2012 03:03:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qzawPmXt0Cof; Wed, 17 Oct 2012 03:03:19 -0700 (PDT)
Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by ietfa.amsl.com (Postfix) with ESMTP id A730921F87F1; Wed, 17 Oct 2012 03:03:18 -0700 (PDT)
Received: by mail-wi0-f172.google.com with SMTP id hq12so365189wib.13 for <multiple recipients>; Wed, 17 Oct 2012 03:03:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:x-mailer:thread-index:content-language; bh=GcglzIWPqoOBssYYsj9+9qoqKYSCCSxp1o4dBNg5cZU=; b=oWyVIW9cfsnlTEtZTSSNQdIooWBmwJ2N7H+f2iB3/Ud1Asmo+eDXAF9f2h6cqRbFZH YpWksz41EZ+474gYhlOhJeFcZafRVDiLKioU1XKU1euJziBwzanswwjL7harDBgWcu/1 ph0qvVAKQC80MWyO1dWQSbtB04mMOXEGYX6/mTHZq/ZABsMLPHGKBNzJU7gTp20egIu5 knsu9AKMAJEZhavcgC83aFZ+QZzZu5XNmLo13yFmEcwnxh8o4xUjQAK8Bs4SXHcgKtcr 5FtVz0G9OCc73SBZtGPHsnQdwsNpItGJQKCFHOg+tAEGyF01iBD42JbZT19PFoqlNADM RdHg==
Received: by 10.180.19.71 with SMTP id c7mr3036359wie.2.1350468197685; Wed, 17 Oct 2012 03:03:17 -0700 (PDT)
Received: from RoniE (bzq-79-176-243-9.red.bezeqint.net. [79.176.243.9]) by mx.google.com with ESMTPS id dm3sm26767231wib.3.2012.10.17.03.03.14 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 17 Oct 2012 03:03:16 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Malis, Andrew G \(Andy\)'" <andrew.g.malis@verizon.com>, <draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org>
References: <002101cd7997$a5204330$ef60c990$@gmail.com> <CC98C05A.2FC85%andrew.g.malis@one.verizon.com>
In-Reply-To: <CC98C05A.2FC85%andrew.g.malis@one.verizon.com>
Date: Wed, 17 Oct 2012 12:01:03 +0200
Message-ID: <010801cdac4e$5328ecf0$f97ac6d0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0109_01CDAC5F.16B34390"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKvrrCCYTySHJIE6oYZ/BaFSZDU3pX5PyvA
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-ccamp-rfc5787bis-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Oct 2012 10:03:21 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0109_01CDAC5F.16B34390
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Andy,

Thanks

Roni

 

From: Malis, Andrew G (Andy) [mailto:andrew.g.malis@verizon.com] 
Sent: 09 October, 2012 2:55 AM
To: Roni Even; draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org
Cc: ietf@ietf.org; gen-art@ietf.org; Malis, Andrew G (Andy)
Subject: Re: Gen-ART LC review of draft-ietf-ccamp-rfc5787bis-05

 

Roni,

 

Thanks for your review, and sorry for the delay on the response, but we've
also been working on incorporating other changes to the draft as well. 

 

To answer your question on section 6.1, that was a good catch. That should
have said "other than the first", rather than "preceding the first". This
will be corrected.

 

To answer your question on section 10, the text is repeated in the
subsections to make life easier for IANA, since they would probably have
replicated it themselves anyway in the three registry listings.

 

On your last comment, we agree with you that the more familiar reader will
not have a problem.

 

Thanks again,

Andy

 

From: Roni Even <ron.even.tlv@gmail.com>
Date: Monday, August 13, 2012 14:07 
To: "draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org"
<draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org>
Cc: "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Gen-ART LC review of draft-ietf-ccamp-rfc5787bis-05
Resent-To: <acee.lindem@ericsson.com>, Adrian Farrell <adrian@olddog.co.uk>,
Andrew Malis <andrew.g.malis@verizon.com>, <dbrungard@att.com>,
<dimitri.papadimitriou@alcatel-lucent.com>, <lberger@labn.net>

 

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-ccamp-rfc5787bis-05.

Reviewer: Roni Even

Review Date:2012-8-12

IETF LC End Date: 2012-8-17

IESG Telechat date:

 

Summary: This draft is almost ready for publication as a standard track RFC.

 

 

Major issues:

 

Minor issues:

In section 6.1 " If specified more than once, instances preceding the first
will be ignored and condition SHOULD be logged for possible action by the
network operator."  I am not sure what is meant by preceding the first.

 

 

Nits/editorial comments:

 

1.	The following note appears in section 10.1, 10.2 and 10.3. "Note
that the same values for the Inter-RA Export Upward sub-TLV and the Inter-RA
Export Downward Sub-TLV MUST be used when they appear in the Link TLV, Node
Attribute TLV, and Router Address TLV." - why not have it in section 10
before section 10.1.
2.	I saw in appendix  B that one of the changes from RFC 5787 was to
clarify the terminology before defining extensions, I would have found it
easier to read if the ASON hierarchy and the relation to OSPF in section 2
were presented in figures. This was more an issue to me as a reader not
familiar with the terminology and I would like to think that the more
familiar reader will not have problem.

 


------=_NextPart_000_0109_01CDAC5F.16B34390
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:229272229;
	mso-list-template-ids:-65088188;}
@list l1
	{mso-list-id:715087181;
	mso-list-type:hybrid;
	mso-list-template-ids:-1205706658 -1668626108 67698713 67698715 =
67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-bidi-font-family:Calibri;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Andy,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Thanks<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Roni<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Malis, Andrew G (Andy) [mailto:andrew.g.malis@verizon.com] =
<br><b>Sent:</b> 09 October, 2012 2:55 AM<br><b>To:</b> Roni Even; =
draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org<br><b>Cc:</b> =
ietf@ietf.org; gen-art@ietf.org; Malis, Andrew G =
(Andy)<br><b>Subject:</b> Re: Gen-ART LC review of =
draft-ietf-ccamp-rfc5787bis-05<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'>Roni,<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'><o:p>&nbsp;</o:p></span></p></div><div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'>Thanks for your review, and sorry for the delay on =
the response, but we've&nbsp;also been working on incorporating other =
changes to the draft as =
well.&nbsp;<o:p></o:p></span></p></div></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'>To answer your question on section 6.1, that was a =
good catch. That should have said &quot;other than the first&quot;, =
rather than &quot;preceding the first&quot;. This will be =
corrected.<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'>To answer your question on section 10, the text is =
repeated in the subsections to make life easier for IANA, since they =
would probably have replicated it themselves anyway in the three =
registry listings.<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'>On your last comment, we agree with you that the =
more familiar reader will not have a =
problem.<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'>Thanks again,<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'>Andy<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'><o:p>&nbsp;</o:p></span></p></div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Tahoma","sans-ser=
if";color:black'>From: </span></b><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Tahoma","sans-ser=
if";color:black'>Roni Even &lt;<a =
href=3D"mailto:ron.even.tlv@gmail.com">ron.even.tlv@gmail.com</a>&gt;<br>=
<b>Date: </b>Monday, August 13, 2012 14:07 <br><b>To: </b>&quot;<a =
href=3D"mailto:draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org">draft-ietf=
-ccamp-rfc5787bis.all@tools.ietf.org</a>&quot; &lt;<a =
href=3D"mailto:draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org">draft-ietf=
-ccamp-rfc5787bis.all@tools.ietf.org</a>&gt;<br><b>Cc: </b>&quot;<a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&quot; &lt;<a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;, &quot;<a =
href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a>&quot; &lt;<a =
href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a>&gt;<br><b>Subject: =
</b>Gen-ART LC review of draft-ietf-ccamp-rfc5787bis-05<br><b>Resent-To: =
</b>&lt;<a =
href=3D"mailto:acee.lindem@ericsson.com">acee.lindem@ericsson.com</a>&gt;=
, Adrian Farrell &lt;<a =
href=3D"mailto:adrian@olddog.co.uk">adrian@olddog.co.uk</a>&gt;, Andrew =
Malis &lt;<a =
href=3D"mailto:andrew.g.malis@verizon.com">andrew.g.malis@verizon.com</a>=
&gt;, &lt;<a =
href=3D"mailto:dbrungard@att.com">dbrungard@att.com</a>&gt;, &lt;<a =
href=3D"mailto:dimitri.papadimitriou@alcatel-lucent.com">dimitri.papadimi=
triou@alcatel-lucent.com</a>&gt;, &lt;<a =
href=3D"mailto:lberger@labn.net">lberger@labn.net</a>&gt;<o:p></o:p></spa=
n></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'><o:p>&nbsp;</o:p></span></p></div><div><div><p =
class=3DMsoNormal><span style=3D'color:#08003F'>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></span></p><p class=3DMsoNormal><span =
style=3D'color:#08003F'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#08003F'>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>&nbsp;</span><span style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>Document: </span><span =
style=3D'color:#08003F'>draft-ietf-ccamp-rfc5787bis-05.<o:p></o:p></span>=
</p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>Reviewer: Roni Even</span><span =
style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>Review Date:2012&#8211;8&#8211;12</span><span =
style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>IETF LC End Date: 2012&#8211;8&#8211;17</span><span =
style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>IESG Telechat date:</span><span =
style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>&nbsp;</span><span style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>Summary: This draft is almost ready for publication as a standard =
track RFC.</span><span style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>&nbsp;</span><span style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>&nbsp;</span><span style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>Major issues:</span><span =
style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>&nbsp;</span><span style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>Minor issues:</span><span =
style=3D'color:#08003F'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#08003F'>In section 6.1 &#8220; If specified more than =
once, instances preceding the first will be ignored and condition SHOULD =
be logged for possible action by the network operator.&#8221;&nbsp; I am =
not sure what is meant by preceding the first.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#08003F'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>&nbsp;</span><span style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>Nits/editorial comments:</span><span =
style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>&nbsp;</span><span style=3D'color:#08003F'><o:p></o:p></span></p><ol =
style=3D'margin-top:0in' start=3D1 type=3D1><li class=3DMsoNormal =
style=3D'color:#08003F;mso-list:l1 level1 lfo3'>The following note =
appears in section 10.1, 10.2 and 10.3. &#8220;Note that the same values =
for the Inter-RA Export Upward sub-TLV and the Inter-RA Export Downward =
Sub-TLV MUST be used when they appear in the Link TLV, Node Attribute =
TLV, and Router Address TLV.&#8221; &#8211; why not have it in section =
10 before section 10.1.<o:p></o:p></li><li class=3DMsoNormal =
style=3D'color:#08003F;mso-list:l1 level1 lfo3'>I saw in appendix&nbsp; =
B that one of the changes from RFC 5787 was to clarify the terminology =
before defining extensions, I would have found it easier to read if the =
ASON hierarchy and the relation to OSPF in section 2 were presented in =
figures. This was more an issue to me as a reader not familiar with the =
terminology and I would like to think that the more familiar reader will =
not have problem.<o:p></o:p></li></ol><p class=3DMsoNormal><span =
style=3D'color:#08003F'>&nbsp;<o:p></o:p></span></p></div></div></div></b=
ody></html>
------=_NextPart_000_0109_01CDAC5F.16B34390--


From miguel.a.garcia@ericsson.com  Wed Oct 17 07:21:35 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 67C1A21F8607 for <gen-art@ietfa.amsl.com>; Wed, 17 Oct 2012 07:21:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.243
X-Spam-Level: 
X-Spam-Status: No, score=-6.243 tagged_above=-999 required=5 tests=[AWL=0.006,  BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2-hlvZvMCR4C for <gen-art@ietfa.amsl.com>; Wed, 17 Oct 2012 07:21:34 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 2579021F84B6 for <gen-art@ietf.org>; Wed, 17 Oct 2012 07:21:33 -0700 (PDT)
X-AuditID: c1b4fb25-b7f956d0000011c3-bf-507ebeecdad6
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 1A.4B.04547.CEEBE705; Wed, 17 Oct 2012 16:21:32 +0200 (CEST)
Received: from [159.107.51.88] (153.88.115.8) by esessmw0184.eemea.ericsson.se (153.88.115.82) with Microsoft SMTP Server id 8.3.279.1; Wed, 17 Oct 2012 16:21:31 +0200
Message-ID: <507EBEE9.2030909@ericsson.com>
Date: Wed, 17 Oct 2012 16:21:29 +0200
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: draft-ietf-fecframe-simple-rs.all@tools.ietf.org,  Greg Shepherd <gjshep@gmail.com>, fecframe-chairs@tools.ietf.org,  Martin Stiemerling <martin.stiemerling@neclab.eu>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprILMWRmVeSWpSXmKPExsUyM+Jvre6bfXUBBu1t2habjx9ntrh5qYXV 4uqrzywWW+bkWXT0XWVzYPXYOesuu8eSJT+ZPGYce8nu8eXyZ7YAligum5TUnMyy1CJ9uwSu jL8r9zAXPBSpOP79KmMD40GBLkZODgkBE4nnD6czQdhiEhfurWfrYuTiEBI4xSjxYfIGKGc1 o8Sk5d/YQKp4BbQlbv36wgpiswioSjxqOskCYrMJmEu0btzI3sXIwSEqECzRdVgMolxQ4uTM Jywgc0QENjJKbD1+hh0kwSygL3Hkz26wzcIC1hLrZ/ezQcRtJS7Muc4CYctLbH87hxnEFhLQ lJh8cynzBEb+WUjmzkLSMgtJywJG5lWMwrmJmTnp5UZ6qUWZycXF+Xl6xambGIHBenDLb9Ud jHfOiRxilOZgURLntd66x19IID2xJDU7NbUgtSi+qDQntfgQIxMHp1QD4+LdK5Kmr7qj//Lp 2eu+M5Re3Fc/u0sk+O7MqCCnrd9eZfbOWvLc8IxsU4/vu4aWVF0xG+ZqcevPL5/KcLeKlFWL bfUoP/ZUkm2X9tx/8wt0z7+pY7txRt/ynKBZasPEOTGXVIMvrjh5+q95yiWNDZfLLj875Ccm 5bvuov3uwPnJYhvO1p0MqFNiKc5INNRiLipOBACULzdDJAIAAA==
Cc: General Area Review Team <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-fecframe-simple-rs-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, 17 Oct 2012 14:21:35 -0000

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

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

Document: draft-ietf-fecframe-simple-rs-04
Reviewer: Miguel Garcia <Miguel.A.Garcia@ericsson.com>
Review Date: 2012-10-17
IETF LC End Date: 2012-10-22

Summary: The document is ready for publication as a standards track RFC, 
but has some Nits that should be addressed.

Major issues: none

Minor issues: none

Nits/editorial comments:

- Section 5.1.1 starts with this sentence:

    The FEC Framework Configuration Information (or FFCI) includes
    information that MUST be communicated between the sender and
    receiver(s).

This is not a normative "MUST" that you are specifying. You are merely 
describing how another specification has a normative MUST, but it is not 
of this document. Therefore, this "MUST" should be replaced by a "need" 
or perhaps a "must".

- Section 5.1.1.1 reads:

    When SDP is used to communicate the FFCI, this FEC Encoding ID is
    carried in the 'encoding-id' parameter.

Two points here:
a) I am missing a normative MUST, such as "this FEC Encoding ID MUST be 
carried..."
b) I guess it would not be such a bad idea to complete the sentence with 
the attribute name in SDP and normative reference that defines the 
attribute and the parameter.

Proposal:

    When SDP is used to communicate the FFCI, this FEC Encoding ID MUST be
    carried in the 'encoding-id' parameter of the  'fec-repair-flow'
    attribute specified in RFC 6364 [RFC6364].

- Similarly in Section 5.1.1.2:

If you agree with this changes, you should do similar changes to Section 
5.1.1.2, the text beginning with "When SDP is used..." Notice also that 
the example following this text in Section 5.1.1.2 is misleading because 
it does not contain a single SDP line, which is generally considered the 
atomic representation element in examples, but just a fraction of it. I 
suggest to extend the example to the full a=fec-repair-flow line.

- Section 8, IANA. Isn't the name of the registry "Reliable Multicast 
Transport (RMT) FEC Encoding IDs and FEC Instance IDs"? Or am I looking 
at the wrong registry? I think that the "FEC Framework (FECFRAME) FEC 
Encoding IDs is one of the registries included under that umbrella of RMT 
FEC Encoding IDs. As a reader, I would like to be able to find the right 
registry without doubt.



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


From ned.freed@mrochek.com  Wed Oct 17 11:19:17 2012
Return-Path: <ned.freed@mrochek.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 DD01521F8605 for <gen-art@ietfa.amsl.com>; Wed, 17 Oct 2012 11:19:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.523
X-Spam-Level: 
X-Spam-Status: No, score=-2.523 tagged_above=-999 required=5 tests=[AWL=0.076,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i5ht0dLiPRxZ for <gen-art@ietfa.amsl.com>; Wed, 17 Oct 2012 11:19:17 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 60E6621F85F4 for <gen-art@ietf.org>; Wed, 17 Oct 2012 11:19:17 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OLIW8X82EO0008V7@mauve.mrochek.com> for gen-art@ietf.org; Wed, 17 Oct 2012 11:14:15 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OLDMMCPN8G00008S@mauve.mrochek.com>; Wed, 17 Oct 2012 11:14:12 -0700 (PDT)
Message-id: <01OLIW8VNVCU00008S@mauve.mrochek.com>
Date: Wed, 17 Oct 2012 10:49:55 -0700 (PDT)
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Wed, 17 Oct 2012 11:57:22 +0200" <010301cdac4d$cfa70060$6ef50120$@gmail.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <010301cdac4d$cfa70060$6ef50120$@gmail.com>
To: Roni Even <ron.even.tlv@gmail.com>
Cc: gen-art@ietf.org, draft-leiba-5322upd-from-group.all@tools.ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-leiba-5322upd-from-group-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, 17 Oct 2012 18:19:18 -0000

> Minor issues:

> 1.	It is not clear from the draft what the use case for using the group
> construct is.  Section 3 talks about the issues with using the group
> construct and recommend limited use, but this is the only information.

The main driver for this work is to add support for EAI downgrade mechanisms,
although a good case can also be made that the present restrictions on group
usage are silly, limiting and unnecessary. (The silliness arises from the
observation that these restrictions enforced by most agents in the field.)

It is far from clear that it makes sense to clutter up this very clean and
crisp specification with a bunch of EAI use case scenarios, especially since
this is an update to RFC 5322 that could in theory be merged into the main
document in the future. A decision taken long ago for both RFC 5321 and 5322
was to keep them as free of entanglements with technology that's layered on top
of them (e.g., MIME, various SMTP extensions) as possible.

In any case, the decision of the group was not to do this.

> 2.	Section 2.1 says "If the sender field uses group syntax, the group
> MUST NOT contains more than one mailbox."  Why use a group name for a single
> mailbox?

Why not? I'm sorry, but this question makes no sense. A group is a
characteristic attached to a collection of zero or more addresses. A group
containing a single member is every bit as valid as a construct as a group
containing 20 members. Or zero, for that matter.

				Ned

From dhc@dcrocker.net  Wed Oct 17 11:30:59 2012
Return-Path: <dhc@dcrocker.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 17DE421F8668; Wed, 17 Oct 2012 11:30:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.524
X-Spam-Level: 
X-Spam-Status: No, score=-6.524 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9he2Gf80wuv6; Wed, 17 Oct 2012 11:30:58 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7570D21F865D; Wed, 17 Oct 2012 11:30:58 -0700 (PDT)
Received: from [192.168.1.6] (adsl-67-127-59-48.dsl.pltn13.pacbell.net [67.127.59.48]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q9HIUrpt021073 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 17 Oct 2012 11:30:54 -0700
Message-ID: <507EF95D.5090007@dcrocker.net>
Date: Wed, 17 Oct 2012 11:30:53 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121005 Thunderbird/16.0
MIME-Version: 1.0
To: ned+ietf@mauve.mrochek.com
References: <010301cdac4d$cfa70060$6ef50120$@gmail.com> <01OLIW8VNVCU00008S@mauve.mrochek.com>
In-Reply-To: <01OLIW8VNVCU00008S@mauve.mrochek.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 17 Oct 2012 11:30:56 -0700 (PDT)
Cc: gen-art@ietf.org, draft-leiba-5322upd-from-group.all@tools.ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-leiba-5322upd-from-group-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
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, 17 Oct 2012 18:30:59 -0000

On 10/17/2012 10:49 AM, ned+ietf@mauve.mrochek.com wrote:
>> Minor issues:
>
>> 1.	It is not clear from the draft what the use case for using the group
>> construct is.  Section 3 talks about the issues with using the group
>> construct and recommend limited use, but this is the only information.
>
> The main driver for this work is to add support for EAI downgrade mechanisms,


Although the Intro text cites this, it doesn't explain how the change 
will help.  Nor is this explained elsewhere in the document.

A single sentence summarizing what benefit is achieved with the change, 
along with a couple of usage examples, would go a long way towards 
showing how this update helps in practical ways.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From ned.freed@mrochek.com  Wed Oct 17 12:06:14 2012
Return-Path: <ned.freed@mrochek.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 A869721F8658 for <gen-art@ietfa.amsl.com>; Wed, 17 Oct 2012 12:06:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.525
X-Spam-Level: 
X-Spam-Status: No, score=-2.525 tagged_above=-999 required=5 tests=[AWL=0.074,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 46AY8GSP5C75 for <gen-art@ietfa.amsl.com>; Wed, 17 Oct 2012 12:06:14 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 0182D21F8650 for <gen-art@ietf.org>; Wed, 17 Oct 2012 12:06:13 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OLIXV4JS6O000637@mauve.mrochek.com> for gen-art@ietf.org; Wed, 17 Oct 2012 12:01:10 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OLDMMCPN8G00008S@mauve.mrochek.com>; Wed, 17 Oct 2012 12:01:08 -0700 (PDT)
Message-id: <01OLIXV2SU4O00008S@mauve.mrochek.com>
Date: Wed, 17 Oct 2012 12:00:05 -0700 (PDT)
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Wed, 17 Oct 2012 11:30:53 -0700" <507EF95D.5090007@dcrocker.net>
MIME-version: 1.0
Content-type: TEXT/PLAIN; format=flowed
References: <010301cdac4d$cfa70060$6ef50120$@gmail.com> <01OLIW8VNVCU00008S@mauve.mrochek.com> <507EF95D.5090007@dcrocker.net>
To: Dave Crocker <dhc@dcrocker.net>
Cc: ned+ietf@mauve.mrochek.com, gen-art@ietf.org, draft-leiba-5322upd-from-group.all@tools.ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-leiba-5322upd-from-group-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, 17 Oct 2012 19:06:14 -0000

> On 10/17/2012 10:49 AM, ned+ietf@mauve.mrochek.com wrote:
> >> Minor issues:
> >
> >> 1.	It is not clear from the draft what the use case for using the group
> >> construct is.  Section 3 talks about the issues with using the group
> >> construct and recommend limited use, but this is the only information.
> >
> > The main driver for this work is to add support for EAI downgrade mechanisms,


> Although the Intro text cites this, it doesn't explain how the change
> will help.  Nor is this explained elsewhere in the document.

> A single sentence summarizing what benefit is achieved with the change,
> along with a couple of usage examples, would go a long way towards
> showing how this update helps in practical ways.

I could live with a single sentence, but I strongly object to the inclusion
of examples, for the reasons I gave in my original response.

				Ned

From john-ietf@jck.com  Wed Oct 17 12:27:44 2012
Return-Path: <john-ietf@jck.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 7254F21F86A4; Wed, 17 Oct 2012 12:27:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.525
X-Spam-Level: 
X-Spam-Status: No, score=-102.525 tagged_above=-999 required=5 tests=[AWL=0.074, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WHR1gGIlXrqU; Wed, 17 Oct 2012 12:27:44 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id ECD8F21F86B0; Wed, 17 Oct 2012 12:27:43 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TOZHE-000PK0-5O; Wed, 17 Oct 2012 15:27:36 -0400
Date: Wed, 17 Oct 2012 15:27:31 -0400
From: John C Klensin <john-ietf@jck.com>
To: ned+ietf@mauve.mrochek.com, Dave Crocker <dhc@dcrocker.net>
Message-ID: <5B0F81787945877A5CC3794B@JcK-HP8200.jck.com>
In-Reply-To: <01OLIXV2SU4O00008S@mauve.mrochek.com>
References: <010301cdac4d$cfa70060$6ef50120$@gmail.com> <01OLIW8VNVCU00008S@mauve.mrochek.com> <507EF95D.5090007@dcrocker.net> <01OLIXV2SU4O00008S@mauve.mrochek.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: gen-art@ietf.org, draft-leiba-5322upd-from-group.all@tools.ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-leiba-5322upd-from-group-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, 17 Oct 2012 19:27:44 -0000

--On Wednesday, October 17, 2012 12:00 -0700
ned+ietf@mauve.mrochek.com wrote:

>> A single sentence summarizing what benefit is achieved with
>> the change, along with a couple of usage examples, would go a
>> long way towards showing how this update helps in practical
>> ways.
> 
> I could live with a single sentence, but I strongly object to
> the inclusion
> of examples, for the reasons I gave in my original response.

Would a possible middle ground be to include a single
well-crafted sentence with an informative citation of
draft-ietf-eai-popimap-downgrade?  That document does contain
examples and an explanation of that particular use case.

I'd prefer to avoid that entirely for the same reasons Ned
cites, but it would, IMO, be good to get on with this rather
than quibbling for days or weeks.

    john



From dhc@dcrocker.net  Wed Oct 17 13:26:33 2012
Return-Path: <dhc@dcrocker.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 0636521F86DD; Wed, 17 Oct 2012 13:26:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.549
X-Spam-Level: 
X-Spam-Status: No, score=-6.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bFPrgbbxK2VE; Wed, 17 Oct 2012 13:26:32 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 8681021F86C7; Wed, 17 Oct 2012 13:26:32 -0700 (PDT)
Received: from [192.168.1.6] (adsl-67-127-59-48.dsl.pltn13.pacbell.net [67.127.59.48]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q9HKQVsx023358 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 17 Oct 2012 13:26:31 -0700
Message-ID: <507F1477.1050905@dcrocker.net>
Date: Wed, 17 Oct 2012 13:26:31 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121005 Thunderbird/16.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
References: <010301cdac4d$cfa70060$6ef50120$@gmail.com> <01OLIW8VNVCU00008S@mauve.mrochek.com> <507EF95D.5090007@dcrocker.net> <01OLIXV2SU4O00008S@mauve.mrochek.com> <5B0F81787945877A5CC3794B@JcK-HP8200.jck.com>
In-Reply-To: <5B0F81787945877A5CC3794B@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 17 Oct 2012 13:26:32 -0700 (PDT)
Cc: ned+ietf@mauve.mrochek.com, gen-art@ietf.org, draft-leiba-5322upd-from-group.all@tools.ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-leiba-5322upd-from-group-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
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, 17 Oct 2012 20:26:33 -0000

On 10/17/2012 12:27 PM, John C Klensin wrote:
>
>
> --On Wednesday, October 17, 2012 12:00 -0700
> ned+ietf@mauve.mrochek.com wrote:
>
>>> A single sentence summarizing what benefit is achieved with
>>> the change, along with a couple of usage examples, would go a
>>> long way towards showing how this update helps in practical
>>> ways.
>>
>> I could live with a single sentence, but I strongly object to
>> the inclusion
>> of examples, for the reasons I gave in my original response.
>
> Would a possible middle ground be to include a single
> well-crafted sentence with an informative citation of
> draft-ietf-eai-popimap-downgrade?  That document does contain
> examples and an explanation of that particular use case.


I thought Ned's goal was -- quite reasonably, IMO -- to not be dependent 
upon EAI for this general-purpose enhancement.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From john-ietf@jck.com  Wed Oct 17 14:16:43 2012
Return-Path: <john-ietf@jck.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 543D621F86B0; Wed, 17 Oct 2012 14:16:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.527
X-Spam-Level: 
X-Spam-Status: No, score=-102.527 tagged_above=-999 required=5 tests=[AWL=0.072, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ReqJ4TiyGILP; Wed, 17 Oct 2012 14:16:42 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id C159E21F86A4; Wed, 17 Oct 2012 14:16:42 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TOayh-000PRO-KN; Wed, 17 Oct 2012 17:16:35 -0400
Date: Wed, 17 Oct 2012 17:16:31 -0400
From: John C Klensin <john-ietf@jck.com>
To: dcrocker@bbiw.net
Message-ID: <4C905CA81E1237976A78C364@JcK-HP8200.jck.com>
In-Reply-To: <507F1477.1050905@dcrocker.net>
References: <010301cdac4d$cfa70060$6ef50120$@gmail.com> <01OLIW8VNVCU00008S@mauve.mrochek.com> <507EF95D.5090007@dcrocker.net> <01OLIXV2SU4O00008S@mauve.mrochek.com> <5B0F81787945877A5CC3794B@JcK-HP8200.jck.com> <507F1477.1050905@dcrocker.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ned+ietf@mauve.mrochek.com, gen-art@ietf.org, draft-leiba-5322upd-from-group.all@tools.ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-leiba-5322upd-from-group-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, 17 Oct 2012 21:16:43 -0000

--On Wednesday, October 17, 2012 13:26 -0700 Dave Crocker
<dhc@dcrocker.net> wrote:

>...
>>>> A single sentence summarizing what benefit is achieved with
>>>> the change, along with a couple of usage examples, would go
>>>> a long way towards showing how this update helps in
>>>> practical ways.
>>> 
>>> I could live with a single sentence, but I strongly object to
>>> the inclusion
>>> of examples, for the reasons I gave in my original response.
>> 
>> Would a possible middle ground be to include a single
>> well-crafted sentence with an informative citation of
>> draft-ietf-eai-popimap-downgrade?  That document does contain
>> examples and an explanation of that particular use case.
> 
> I thought Ned's goal was -- quite reasonably, IMO -- to not be
> dependent upon EAI for this general-purpose enhancement.

The problem is that all of the practical (i.e., not constructed
just for the document) examples we have, especially with the
advice to not use these group addresses except under special
circumstances, are associated with EAI.  So, as soon as one says
something equivalent to "summarize the benefit and provide use
cases" one either becomes dependent on EAI for examples (which
is not what we usually mean by "dependent") or is constructing
works of fancy or speculation.

The other approach --and the one I think Ned is advocating
although he can speak for himself-- is to make this change
primarily because embedding the prohibition on using groups in
backward-pointing addresses in the syntax has outlived its
usefulness if, indeed, it was ever wise.  Instead, we end up
with the syntax restriction eliminated and rather general
use/applicability advice.  It seems to me that ought to be
sufficient.

    best,
    john



From ned.freed@mrochek.com  Wed Oct 17 14:40:12 2012
Return-Path: <ned.freed@mrochek.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 E508A21F8716 for <gen-art@ietfa.amsl.com>; Wed, 17 Oct 2012 14:40:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.526
X-Spam-Level: 
X-Spam-Status: No, score=-2.526 tagged_above=-999 required=5 tests=[AWL=0.073,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SYqpn5S+Xkeo for <gen-art@ietfa.amsl.com>; Wed, 17 Oct 2012 14:40:12 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 6B33B21F8711 for <gen-art@ietf.org>; Wed, 17 Oct 2012 14:40:12 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OLJ390L4ZK00097O@mauve.mrochek.com> for gen-art@ietf.org; Wed, 17 Oct 2012 14:35:09 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OLDMMCPN8G00008S@mauve.mrochek.com>; Wed, 17 Oct 2012 14:35:05 -0700 (PDT)
Message-id: <01OLJ38YAL9600008S@mauve.mrochek.com>
Date: Wed, 17 Oct 2012 14:32:29 -0700 (PDT)
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Wed, 17 Oct 2012 15:27:31 -0400" <5B0F81787945877A5CC3794B@JcK-HP8200.jck.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <010301cdac4d$cfa70060$6ef50120$@gmail.com> <01OLIW8VNVCU00008S@mauve.mrochek.com> <507EF95D.5090007@dcrocker.net> <01OLIXV2SU4O00008S@mauve.mrochek.com> <5B0F81787945877A5CC3794B@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
Cc: ned+ietf@mauve.mrochek.com, gen-art@ietf.org, Dave Crocker <dhc@dcrocker.net>, draft-leiba-5322upd-from-group.all@tools.ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-leiba-5322upd-from-group-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, 17 Oct 2012 21:40:13 -0000

> --On Wednesday, October 17, 2012 12:00 -0700
> ned+ietf@mauve.mrochek.com wrote:

> >> A single sentence summarizing what benefit is achieved with
> >> the change, along with a couple of usage examples, would go a
> >> long way towards showing how this update helps in practical
> >> ways.
> >
> > I could live with a single sentence, but I strongly object to
> > the inclusion
> > of examples, for the reasons I gave in my original response.

> Would a possible middle ground be to include a single
> well-crafted sentence with an informative citation of
> draft-ietf-eai-popimap-downgrade?  That document does contain
> examples and an explanation of that particular use case.

> I'd prefer to avoid that entirely for the same reasons Ned
> cites, but it would, IMO, be good to get on with this rather
> than quibbling for days or weeks.

Channeling my inner Maslow, I see the present text as best, an additional
sentence or two as next best, a sentence and a cite to the downgrade doc next
in line, and including actual EAI examples in this doc as the worst choice.

FWIW.

				Ned


From dhc@dcrocker.net  Wed Oct 17 16:19:09 2012
Return-Path: <dhc@dcrocker.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 2D42321F867E; Wed, 17 Oct 2012 16:19:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.556
X-Spam-Level: 
X-Spam-Status: No, score=-6.556 tagged_above=-999 required=5 tests=[AWL=0.043,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e9bzxvVsy7UO; Wed, 17 Oct 2012 16:19:08 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 819C521F8540; Wed, 17 Oct 2012 16:19:08 -0700 (PDT)
Received: from [192.168.1.6] (adsl-67-127-59-48.dsl.pltn13.pacbell.net [67.127.59.48]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q9HNJ7Wk026837 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 17 Oct 2012 16:19:07 -0700
Message-ID: <507F3CEA.2010306@dcrocker.net>
Date: Wed, 17 Oct 2012 16:19:06 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121005 Thunderbird/16.0
MIME-Version: 1.0
To: Ned Freed <ned.freed@mrochek.com>
References: <010301cdac4d$cfa70060$6ef50120$@gmail.com> <01OLIW8VNVCU00008S@mauve.mrochek.com> <507EF95D.5090007@dcrocker.net> <01OLIXV2SU4O00008S@mauve.mrochek.com> <5B0F81787945877A5CC3794B@JcK-HP8200.jck.com> <01OLJ38YAL9600008S@mauve.mrochek.com>
In-Reply-To: <01OLJ38YAL9600008S@mauve.mrochek.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 17 Oct 2012 16:19:08 -0700 (PDT)
Cc: John C Klensin <john-ietf@jck.com>, ned+ietf@mauve.mrochek.com, gen-art@ietf.org, draft-leiba-5322upd-from-group.all@tools.ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-leiba-5322upd-from-group-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
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, 17 Oct 2012 23:19:09 -0000

On 10/17/2012 2:32 PM, Ned Freed wrote:
> Channeling my inner Maslow, I see the present text as best, an additional
> sentence or two as next best, a sentence and a cite to the downgrade doc next
> in line, and including actual EAI examples in this doc as the worst choice.


The problem I have with the current text is that it says 'what' 
motivated the change, but not how it is useful for the intended class of 
uses.  The reader is left entirely to guess.

Self-actualization among the inadequately-informed invites fantasy more 
than it invites utility.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From barryleiba@gmail.com  Wed Oct 17 16:46:03 2012
Return-Path: <barryleiba@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 2DCF421F8621; Wed, 17 Oct 2012 16:46:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.065
X-Spam-Level: 
X-Spam-Status: No, score=-103.065 tagged_above=-999 required=5 tests=[AWL=-0.088, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6efpUFfizLOc; Wed, 17 Oct 2012 16:46:02 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 825B121F861F; Wed, 17 Oct 2012 16:45:59 -0700 (PDT)
Received: by mail-vc0-f172.google.com with SMTP id fl11so9597491vcb.31 for <multiple recipients>; Wed, 17 Oct 2012 16:45:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=2TCoh3SaoQ/BJJeiPbkoKJY7hUHpilkLFBAjUbfhDck=; b=DNBr2dxaMV+2SPc5ZzURqKXPJIqXJmBuQo1a0pd8E120o5jH0PSA3WKDaPcGuASooC IwGnfqTR7ajGiWFqukgvHKHDwDJyWlM7yaGiIM7pAZE8GE762+T8MHDBlefk2+6A8vrD fIRVotjvZCFdip76IsfVe6mwmksICuDWFn88o7sOzZA0hem4oRvlDy2qFNZvkVC5qHfh hJ6lgSY7z5N8NkqWUfJmeZA5hONfxR6de+AZBmpWBlWjggOfPPEQX8ol7BxLlWePwSg7 Fym51z8XZzAh5FFgHi5r634HDWIWs+qr+Fc8yPFPBhOuP+c9WINe4LEUAdKB2aEMIp7y IvsQ==
MIME-Version: 1.0
Received: by 10.58.86.36 with SMTP id m4mr12550829vez.14.1350517558744; Wed, 17 Oct 2012 16:45:58 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.58.28.231 with HTTP; Wed, 17 Oct 2012 16:45:58 -0700 (PDT)
In-Reply-To: <507F3CEA.2010306@dcrocker.net>
References: <010301cdac4d$cfa70060$6ef50120$@gmail.com> <01OLIW8VNVCU00008S@mauve.mrochek.com> <507EF95D.5090007@dcrocker.net> <01OLIXV2SU4O00008S@mauve.mrochek.com> <5B0F81787945877A5CC3794B@JcK-HP8200.jck.com> <01OLJ38YAL9600008S@mauve.mrochek.com> <507F3CEA.2010306@dcrocker.net>
Date: Wed, 17 Oct 2012 19:45:58 -0400
X-Google-Sender-Auth: zOjJ2SzgtHpYEv4w-ivH0d5WAYE
Message-ID: <CALaySJLex2ozmTMByO8=mRmu-fETX-TDRk7CdMedz5nDxjT6vA@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: dcrocker@bbiw.net
Content-Type: text/plain; charset=ISO-8859-1
Cc: Ned Freed <ned.freed@mrochek.com>, draft-leiba-5322upd-from-group.all@tools.ietf.org, ned+ietf@mauve.mrochek.com, gen-art@ietf.org, John C Klensin <john-ietf@jck.com>, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-leiba-5322upd-from-group-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, 17 Oct 2012 23:46:03 -0000

>> Channeling my inner Maslow, I see the present text as best, an additional
>> sentence or two as next best, a sentence and a cite to the downgrade doc
>> next in line, and including actual EAI examples in this doc as the worst
>> choice.
>
> The problem I have with the current text is that it says 'what' motivated
> the change, but not how it is useful for the intended class of uses.  The
> reader is left entirely to guess.

So, is it better to put in a sentence about representing non-ASCII
text in the group name without including a replyable address?

Or is it better to remove the notation about the EAI use case, and
just say that it's stupid to have the restriction, so we're removing
it?

I'm ambivalent.

Barry

From ned.freed@mrochek.com  Wed Oct 17 17:40:39 2012
Return-Path: <ned.freed@mrochek.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 F0EA821F8623 for <gen-art@ietfa.amsl.com>; Wed, 17 Oct 2012 17:40:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.528
X-Spam-Level: 
X-Spam-Status: No, score=-2.528 tagged_above=-999 required=5 tests=[AWL=0.071,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EcoRuY+PxmLk for <gen-art@ietfa.amsl.com>; Wed, 17 Oct 2012 17:40:38 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 3DE3421F8625 for <gen-art@ietf.org>; Wed, 17 Oct 2012 17:40:24 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OLJ9JD42OW0005HX@mauve.mrochek.com> for gen-art@ietf.org; Wed, 17 Oct 2012 17:35:18 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OLDMMCPN8G00008S@mauve.mrochek.com>; Wed, 17 Oct 2012 17:35:13 -0700 (PDT)
Message-id: <01OLJ9JAK8SQ00008S@mauve.mrochek.com>
Date: Wed, 17 Oct 2012 17:18:37 -0700 (PDT)
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Wed, 17 Oct 2012 16:19:06 -0700" <507F3CEA.2010306@dcrocker.net>
MIME-version: 1.0
Content-type: TEXT/PLAIN; format=flowed
References: <010301cdac4d$cfa70060$6ef50120$@gmail.com> <01OLIW8VNVCU00008S@mauve.mrochek.com> <507EF95D.5090007@dcrocker.net> <01OLIXV2SU4O00008S@mauve.mrochek.com> <5B0F81787945877A5CC3794B@JcK-HP8200.jck.com> <01OLJ38YAL9600008S@mauve.mrochek.com> <507F3CEA.2010306@dcrocker.net>
To: Dave Crocker <dhc@dcrocker.net>
Cc: Ned Freed <ned.freed@mrochek.com>, draft-leiba-5322upd-from-group.all@tools.ietf.org, ned+ietf@mauve.mrochek.com, gen-art@ietf.org, John C Klensin <john-ietf@jck.com>, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-leiba-5322upd-from-group-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, 18 Oct 2012 00:40:39 -0000

> On 10/17/2012 2:32 PM, Ned Freed wrote:
> > Channeling my inner Maslow, I see the present text as best, an additional
> > sentence or two as next best, a sentence and a cite to the downgrade doc next
> > in line, and including actual EAI examples in this doc as the worst choice.


> The problem I have with the current text is that it says 'what'
> motivated the change, but not how it is useful for the intended class of
> uses.  The reader is left entirely to guess.

> Self-actualization among the inadequately-informed invites fantasy more
> than it invites utility.

That depends on both the utility and the desirability of repeating the existing
use case, doesn't it? The EAI use case of downgraded messages is one that only
exists because of a nasty confluence of restrictions and which we absolutely do
not want to see repeated in any other context.

If you really think this is important to explain why we're making this change
against the overall context of RFC 5322 - and I most certainly do not agree
that it is important to do so - then the best "use case" to add is the negative
one: The elimination of an unnecessary restriction that isn't followed in
practice.

I see no way to explain the narrow EAI use case in this context without either
dragging in a whole bunch of EAI that has no business being here or leaving
various things dangling. Either way the average reader looking at general
message usage isn't going to get it, and the more you try and waltz around this
the more likely you are to get exactly the outcome you fear: Someone is going
to see some sort of parallel with some problem they are trying to solve (some
sort of deliberate form of address obfuscation scheme immediately comes to
mind) and proceeds to make a mess of things.

				Ned

P.S. It really would be best if this could wait until there was an update
to RFC 5322. But that's not how the timing has worked out, so this is the
best alternative available.

From yiu_lee@cable.comcast.com  Wed Oct 17 17:46:32 2012
Return-Path: <yiu_lee@cable.comcast.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 AB97921F862B; Wed, 17 Oct 2012 17:46:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.798
X-Spam-Level: 
X-Spam-Status: No, score=-103.798 tagged_above=-999 required=5 tests=[AWL=1.433, BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QXk9iY44ZBJz; Wed, 17 Oct 2012 17:46:31 -0700 (PDT)
Received: from cable.comcast.com (copdcavout01.cable.comcast.com [76.96.32.253]) by ietfa.amsl.com (Postfix) with ESMTP id 9E46421F8623; Wed, 17 Oct 2012 17:46:31 -0700 (PDT)
Received: from ([24.40.56.115]) by copdcavout01.cable.comcast.com with ESMTP  id C7WM3M1.38137703; Wed, 17 Oct 2012 18:23:03 -0600
Received: from PACDCEXMB05.cable.comcast.com ([169.254.7.147]) by PACDCEXHUB02.cable.comcast.com ([fe80::492e:3fa1:c2ad:e04e%13]) with mapi id 14.02.0318.001; Wed, 17 Oct 2012 20:46:26 -0400
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: "Black, David" <david.black@emc.com>, "roberta.maglione@telecomitalia.it" <roberta.maglione@telecomitalia.it>, "carlw@mcsr-labs.org" <carlw@mcsr-labs.org>, "christian.jacquenet@orange.com" <christian.jacquenet@orange.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART review of draft-ietf-softwire-dslite-deployment-06
Thread-Index: AQHNrMoAT7CfnR/9yUSA1hDdxxOKmg==
Date: Thu, 18 Oct 2012 00:46:24 +0000
Message-ID: <E3FAB1F4F41F3A45B287E8D9C53522FD37A7EC79@PACDCEXMB05.cable.comcast.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7120DFAEF29@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.4.120824
x-originating-ip: [24.40.55.70]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3433351583_493034"
MIME-Version: 1.0
Cc: "softwires@ietf.org" <softwires@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-softwire-dslite-deployment-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, 18 Oct 2012 00:46:32 -0000

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

Hi David,

Thanks very much for review the draft. Comments inline.

Thanks,
Yiu

On 10/15/12 7:10 PM, "Black, David" <david.black@emc.com> wrote:

>I am the assigned Gen-ART reviewer for this draft. For background on
>Gen-ART, please see the FAQ at
><http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
>Please resolve these comments along with any other Last Call comments
>you may receive.
>
>Document: draft-ietf-softwire-dslite-deployment-06
>Reviewer: David L. Black
>Review Date: October 15, 2012
>IETF LC End Date: October 16, 2012
>IESG Telechat Date: October 25, 2012
>
>Summary:
>
>This draft is on the right track but has open issues, described in the
>review.
>
>This is a generally well-written draft that expands considerably on the
>brief
>deployment considerations for DS-Lite in Appendix A of RFC 6333.  The
>draft
>is clear and reasonably well-written, and a significant improvement on
>that
>RFC 6333 Appendix, although an understanding of RFC 6333 is necessary to
>understand this draft, which seems completely reasonable.
>
>The B4 and AFTR acronyms are clever - kudos to whomever came up with
>those.
>
>I found five open issues, all of which are minor.
>
>Minor Issues:
>
>[1] Ironically, the first issue is that something should be said about
>the relationship of this draft to Appendix A of RFC 6333.  It probably
>suffices to say that this draft expands on the material in that Appendix,
>as I see no need to specify that this draft updates RFC 6333 solely to
>change non-normative material in an Appendix.

[YL] In "Overview", we will add:

"This document expands Appendix A of RFC6333 and discusses various
DS-Lite deployment considerations for operators."

>
>[2] The MTU increase technique in Section 2.2 is a "may", which is
>consistent with Section 5.3 of RFC 6333.  OTOH, Section 2.2 of this
>draft should also discuss the AFTR resource exhaustion concern that
>described in Section 6.3 of RFC 6333, as that is a potential
>operational reason for an ISP to increase MTU size (e.g., if customer
>sourcing of large IPv4 packets is not sufficiently rare).

[YL] In 2.2, we will add:

"Note that reassembly at Tunnel Exit-Point is resource
	intensive. A large number of B4 may terminate on the same AFTR. If many B4
	fragment the packets, it would increase sufficient load to the AFTR for
	reassembly. We recommend the operator should increase the MTU size of the
IPv6
	network between B4 and AFTR to avoid fragmentation."

>
>[3] Section 2.7 refers to "the AFTR's internal interface".  There may be
>two internal interfaces, the physical IPv6 interface (outer header) and
>the tunnel's IPv4 interface (inner header).  The text should be clarified
>to indicate which interface is involved - it appears that the AFTR's
>physical IPv6 interface is intended in this section.

[YL] We replace "internal" to "IPv6"

>
>[4] Section 2.7 cites RFC 6333 for use of DHCPv6 with DS-Lite.  RFC 6334
>should be cited - either in addition to or instead of RFC 6333.

[YL] Fixed

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

[YL] Good catch. Actually I believe AFTR "does" have both IPv4 and IPv6 to
identify the customer. I suggest we remove

"but it will potentially introduce some additional complexity because
   the AFTR does not have detailed customer identity information."

>
>Nits:
>
>Section 2.3 on MTU Considerations could usefully mention MTU discovery
>techniques, as possibilities for customer IPv4 traffic to adapt to a
>smaller IPv4 MTU.  If this is done, it would be useful to mention
>RFC 4821 in addition to the mention of RFC 1191 in RFC 6333.

[YL] We would consider RFC 4821. However, the challenge is I don't have
information how many current OS support RFC 4821. Since DS-lite is a
transition technology, it would be unreasonable to ask the OS company to
implement RFC 4821 for DS-lite.

>
>Section 2.4 should define "lawful intercept".  It would be helpful to
>cite a reference for this concept if something appropriate can be found.

[YL] We will find whether there is any reference to this concept. If we
can't find any, we would add an explanation in the draft.

>
>Section 2.5:
>- Are one or both types of logging recommended?

[YL] We tempted to recommend source-specific log. However, some regulators
require to use both and the regulations vary country from country, this is
why we left it open and let the operators to decide.

>- Last paragraph on p.4, "timestamped log" is not a good verb phrase.
>	"maintain a timestamped log of" would be a better replacement.

[YL] Fixed

>- Last paragraph in section, where is the batch file sent?

[YL] We will add:

"The files may be compressed before transferring to a repository server
	to better utilize bandwidth and storage."


>
>In Section 2.7, I'm having a hard time understanding which traffic is
>intended to be subject to the Outgoing Policies and the Incoming Policies.
>Expanding each of those two bullets to explain what traffic is subject
>to each class of policies would help.

[YL] Does this help?

Outgoing Policies apply to packets originating from B4 to IPv4 network.
Incoming Policies apply to packets originating from IPv4 network to B4.



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

[YL] Added the cite.

>
>idnits 2.12.13 found a tiny nit - draft-ietf-pcp-base is now at
>version 28.

[YL] Fixed.

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

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

MIIVmQYJKoZIhvcNAQcCoIIVijCCFYYCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
EzEwggU0MIIEHKADAgECAhEAzuhISIgzOwSitfbc2LN4WDANBgkqhkiG9w0BAQUFADCBkzEL
MAkGA1UEBhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2Fs
Zm9yZDEaMBgGA1UEChMRQ09NT0RPIENBIExpbWl0ZWQxOTA3BgNVBAMTMENPTU9ETyBDbGll
bnQgQXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTAeFw0xMjA4MjgwMDAwMDBa
Fw0xMzA4MjgyMzU5NTlaMCoxKDAmBgkqhkiG9w0BCQEWGXlpdV9sZWVAY2FibGUuY29tY2Fz
dC5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCscOeu5/EoYRdja1jb6L4x
o0TIevelc17NsPuRHfr2z3BGUMbfsJY1p0uXO9+inBQoBXwb07ac3SbOjA/6Ef3NlMPItWdT
RGeFL6e/sMju9RgVyJURFnFgp7tc2tffnPOupnKZeeRehXeEFjun6+GC6teb1kSMu+WMMaCa
D7/XSK+Q+F0Udc2Av0/gUCkGfTDpNnYwutfctEMRnle6EYUqmJMN4C0crEfovmYdMFFgJLKs
Wa5Cdc+naFoIqzW8AcZB6+1XUDTzFbgjqgUbFFZFPzVZqNxLDFNy4tn8VlRSp2jBhgwQHtk1
ZA+spFENaeUuebp4tczj0IHG683FhhWjAgMBAAGjggHpMIIB5TAfBgNVHSMEGDAWgBR6E04A
dFvGeGNkJ8Ev4qBbvHnFezAdBgNVHQ4EFgQUz03csl7CmjwQY+spX9VWeGb5sVQwDgYDVR0P
AQH/BAQDAgWgMAwGA1UdEwEB/wQCMAAwIAYDVR0lBBkwFwYIKwYBBQUHAwQGCysGAQQBsjEB
AwUCMBEGCWCGSAGG+EIBAQQEAwIFIDBGBgNVHSAEPzA9MDsGDCsGAQQBsjEBAgEBATArMCkG
CCsGAQUFBwIBFh1odHRwczovL3NlY3VyZS5jb21vZG8ubmV0L0NQUzBXBgNVHR8EUDBOMEyg
SqBIhkZodHRwOi8vY3JsLmNvbW9kb2NhLmNvbS9DT01PRE9DbGllbnRBdXRoZW50aWNhdGlv
bmFuZFNlY3VyZUVtYWlsQ0EuY3JsMIGIBggrBgEFBQcBAQR8MHowUgYIKwYBBQUHMAKGRmh0
dHA6Ly9jcnQuY29tb2RvY2EuY29tL0NPTU9ET0NsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2Vj
dXJlRW1haWxDQS5jcnQwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLmNvbW9kb2NhLmNvbTAk
BgNVHREEHTAbgRl5aXVfbGVlQGNhYmxlLmNvbWNhc3QuY29tMA0GCSqGSIb3DQEBBQUAA4IB
AQBG7LORtWcmzDlw0N/D5AwfsSLe93essAqKFhJ+nt7SmMVBsxGzFnSsZGQHMYQ4UXtiVq9A
NjtPk00F3DC3QGxe4mxdwF9LzeYHpHMpCHTzNyilSimKZolLNBO+MO/U0u79rdF2W+dOAwkB
dzroWBxK+yMhijJn2DCE/1pgxqBz+c9zbAtJYPVpgbeGNvvfIp6CA/JYsupQNqPX49a4MdJ3
L9yXLTiegSE8uPUlCB3sHZclQOXAttuMewpcKDoIC4wZgERKQqRH61PQO100GLKUO+VrTq+f
xNkjOAqA+dih6QO5Djbv3qcMTCcAChJQYK8BS7jved8XgEVa0Ihz7oWKMIIFGjCCBAKgAwIB
AgIQbRnqpxlPajMi5iIyeqpx3jANBgkqhkiG9w0BAQUFADCBrjELMAkGA1UEBhMCVVMxCzAJ
BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJU
UlVTVCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNV
BAMTLVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbDAeFw0x
MTA0MjgwMDAwMDBaFw0yMDA1MzAxMDQ4MzhaMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMS
R3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8g
Q0EgTGltaXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQg
U2VjdXJlIEVtYWlsIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAkoSEW0tX
mNReL4uk4UDIo1NYX2Zl8TJO958yfVXQeExVt0KU4PkncQfFxmmkuTLE8UAakMwnVmJ/F7Vx
aa7lIBvky2NeYMqiQfZq4aP/uN8fSG1lQ4wqLitjOHffsReswtqCAtbUMmrUZ28gE49cNfrl
VICv2HEKHTcKAlBTbJUdqRAUtJmVWRIx/wmi0kzcUtve4kABW0ho3cVKtODtJB86r3FfB+Os
vxQ7sCVxaD30D9YXWEYVgTxoi4uDD216IVfmNLDbMn7jSuGlUnJkJpFOpZIP/+CxYP0ab2hR
mWONGoulzEKbm30iY9OpoPzOnpDfRBn0XFs1uhbzp5v/wQIDAQABo4IBSzCCAUcwHwYDVR0j
BBgwFoAUiYJnfcSdJnAAS7RQSHzePa4Ebn0wHQYDVR0OBBYEFHoTTgB0W8Z4Y2QnwS/ioFu8
ecV7MA4GA1UdDwEB/wQEAwIBBjASBgNVHRMBAf8ECDAGAQH/AgEAMBEGA1UdIAQKMAgwBgYE
VR0gADBYBgNVHR8EUTBPME2gS6BJhkdodHRwOi8vY3JsLnVzZXJ0cnVzdC5jb20vVVROLVVT
RVJGaXJzdC1DbGllbnRBdXRoZW50aWNhdGlvbmFuZEVtYWlsLmNybDB0BggrBgEFBQcBAQRo
MGYwPQYIKwYBBQUHMAKGMWh0dHA6Ly9jcnQudXNlcnRydXN0LmNvbS9VVE5BZGRUcnVzdENs
aWVudF9DQS5jcnQwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVzZXJ0cnVzdC5jb20wDQYJ
KoZIhvcNAQEFBQADggEBAIXWvnhXVW0zf0RS/kLVBqgBA4CK+w2y/Uq/9q9BSfUbWsXSrRtz
bj7pJnzmTJjBMCjfy/tCPKElPgp11tA9OYZm0aGbtU2bb68obB2v5ep0WqjascDxdXovnrqT
ecr+4pEeVnSy+I3T4ENyG+2P/WA5IEf7i686ZUg8mD2lJb+972DgSeUWyOs/Q4Pw4O4NwdPN
M1+b0L1garM7/vrUyTo8H+2b/5tJM75CKTmD7jNpLoKdRU2oadqAGx490hpdfEeZpZsIbRKZ
htZdVwcbpzC+S0lEuJB+ytF5OOu0M/qgOl0mWJ5hVRi0IdWZ1eBDQEIwvuql55TSsP7zdfl/
bucwggSdMIIDhaADAgECAhA0PekrrCc0/4/LNJT7zHBUMA0GCSqGSIb3DQEBBQUAMG8xCzAJ
BgNVBAYTAlNFMRQwEgYDVQQKEwtBZGRUcnVzdCBBQjEmMCQGA1UECxMdQWRkVHJ1c3QgRXh0
ZXJuYWwgVFRQIE5ldHdvcmsxIjAgBgNVBAMTGUFkZFRydXN0IEV4dGVybmFsIENBIFJvb3Qw
HhcNMDUwNjA3MDgwOTEwWhcNMjAwNTMwMTA0ODM4WjCBrjELMAkGA1UEBhMCVVMxCzAJBgNV
BAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT
VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMT
LVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbDCCASIwDQYJ
KoZIhvcNAQEBBQADggEPADCCAQoCggEBALI5haTyfatBO2JGN67NwWB1vDll+UoaR6K5zEjM
apjVTTUZuaRC5c5J4oovHnzSMQfHTrSDZJ0uKdWiZMSFvYVRNXmkTmiQexx6pJKoF/KYFfKT
zMmkMpW7DE8wvZigC4vlbhuiRvp4vKJvq1lepS/Pytptqi/rrKGzaqq3Lmc1i3nhHmmI4uZG
zaCl6r4LznY6eg6b6vzaJ1s9cx8i5khhxkzzabGoLhu21DEgLLyCio6kDqXXiUP8FlqvHXHX
EVnauocNr/rz4cLwpMVnjNbWVDreCqS6A3ezZcj9HtN0YqoYymiTHqGFfvVHZcv4TVcodNI0
/zC27vZiMBSMLOsCAwEAAaOB9DCB8TAfBgNVHSMEGDAWgBStvZh6NLQm9/rEJlTvA73gJMtU
GjAdBgNVHQ4EFgQUiYJnfcSdJnAAS7RQSHzePa4Ebn0wDgYDVR0PAQH/BAQDAgEGMA8GA1Ud
EwEB/wQFMAMBAf8wEQYDVR0gBAowCDAGBgRVHSAAMEQGA1UdHwQ9MDswOaA3oDWGM2h0dHA6
Ly9jcmwudXNlcnRydXN0LmNvbS9BZGRUcnVzdEV4dGVybmFsQ0FSb290LmNybDA1BggrBgEF
BQcBAQQpMCcwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVzZXJ0cnVzdC5jb20wDQYJKoZI
hvcNAQEFBQADggEBAAG8nONjKLDzMQHC33vdYqABnSMxD5ySc1NR6h9M+tafxMovZ354Mw90
FrmRh5H1iib6ZHAA2B75CwRiUIeTgdTa9SPbNLuFVrRwNG54gzcehRzFERWSX4cXvaxq/fHC
0cyJX7F88D5R8jXzfOxgmGs6K+Dv37N9huu1G/Vb7KJ8mBPXAFC50S1z3gN4dOEFhTFey5q5
nZTGuZQ3dXLcRPtn6PD6JR5Sp9ol6UfgoMc8oE6xCjb7d0if75eK+7T+45QUqIO8XC0/0mBx
YO7CcYIM6Yg249ogtKOgbKqWS7iAjnXKSQf2OxS639wF2Z/b4LLmTaB4JufnLW5/X8YeiBUw
ggQ2MIIDHqADAgECAgEBMA0GCSqGSIb3DQEBBQUAMG8xCzAJBgNVBAYTAlNFMRQwEgYDVQQK
EwtBZGRUcnVzdCBBQjEmMCQGA1UECxMdQWRkVHJ1c3QgRXh0ZXJuYWwgVFRQIE5ldHdvcmsx
IjAgBgNVBAMTGUFkZFRydXN0IEV4dGVybmFsIENBIFJvb3QwHhcNMDAwNTMwMTA0ODM4WhcN
MjAwNTMwMTA0ODM4WjBvMQswCQYDVQQGEwJTRTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAk
BgNVBAsTHUFkZFRydXN0IEV4dGVybmFsIFRUUCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVz
dCBFeHRlcm5hbCBDQSBSb290MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAt/ca
M+byAAQtOeBOW+0fvGwPzbX6I7bO3psRM5ekKUx9k5+9SryT7QMa44/P5W1QWtaXKZRagLBJ
etsulf24yr83OC0ePpFBrXBWx/BPP+gynnTKyJBU6cZfD3idmkA8Dqxhql4Uj56HoWpQ3Nea
Tq8Fs6ZxlJxxs1BgCscTnTgHhgKo6ahpJhiQq0ywTyOrOk+E2N/On+Fpb7vXQtdrROTHre5t
QV9yWnEIN7N5ZaRZoJQ39wAvDcKSctrQOHLbFKhFxF0qfbe01sTurM0TRLfJK91DACX6Yblp
algjEbenM49WdVn1zSnXRrcKK2W200JvFbK4e/vv6V1T1TRaJwIDAQABo4HcMIHZMB0GA1Ud
DgQWBBStvZh6NLQm9/rEJlTvA73gJMtUGjALBgNVHQ8EBAMCAQYwDwYDVR0TAQH/BAUwAwEB
/zCBmQYDVR0jBIGRMIGOgBStvZh6NLQm9/rEJlTvA73gJMtUGqFzpHEwbzELMAkGA1UEBhMC
U0UxFDASBgNVBAoTC0FkZFRydXN0IEFCMSYwJAYDVQQLEx1BZGRUcnVzdCBFeHRlcm5hbCBU
VFAgTmV0d29yazEiMCAGA1UEAxMZQWRkVHJ1c3QgRXh0ZXJuYWwgQ0EgUm9vdIIBATANBgkq
hkiG9w0BAQUFAAOCAQEAsJvghSXC1iPiD5YGkp1BmJzZhHmB2R5bFAcjNmWPsNh3u6xBbEdg
g1Gw+TI95/z2JhPHgBalv1r8h894eYkhmuJMBwqGNbzy3lHE0pa33H5O7nD9HDnrDAJRFC2O
vRbgwd9Gdeckrez0QrSFk3AQZ7qdBjVKGNMresxRQqF6Y9Hmu6HFK8I2vhMN5r1jfnl7pwkN
QKtq3Y+Kw/b2jBpCBVHURfWfp2IhaBUgQzyZ53y9JNipkRdziD9WGzE4GLRxD5rNyA6eji4b
4YyYg8sfMfFETMYEc0l2YA/H+L0XgGsu6cxMDlqaeQ8gCi7VnmMmHlWSlNiCF1p70LzHj06G
BDGCAjAwggIsAgEBMIGpMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5j
aGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDE5
MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWls
IENBAhEAzuhISIgzOwSitfbc2LN4WDAJBgUrDgMCGgUAoF0wIwYJKoZIhvcNAQkEMRYEFMMH
sMOZ10JTh9owhxBX+FD1xKU7MBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcN
AQkFMQ8XDTEyMTAxODAwNDYyMlowDQYJKoZIhvcNAQEBBQAEggEAVXCxAZKhMeCjLddBOMAc
euaqgybURvaW20hpdAFWozQtHwiE4PuiVqDfyXb2yUkarjFljj7hCe5skRPcCVpfRzmjzXwy
+W5TQf1Slf431sNvR2xy5AW2NP57EnbGu1s7Mtvy5PC1eNBa68NS3Sxofveh1PJho7ca/E6m
dY+IsVuHgjgx3HpAhbehKLEhJ48pWXc9eygaYc94SUhjfWFKVPeY7h43LN4/hDsvOQVpFbcO
4Tv3UiBrr7XDuRHPEKnwMuh0RGP9JePzKB+/QSMfjzUf3J3UT0nZe2ZDQvCX0S51Jq9vies8
wLPlTa+1QYlkVcgQkJb7A5vTvhRgmBsF+A==

--B_3433351583_493034--

From dhc@dcrocker.net  Wed Oct 17 17:50:20 2012
Return-Path: <dhc@dcrocker.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 06FFE21F8686; Wed, 17 Oct 2012 17:50:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.562
X-Spam-Level: 
X-Spam-Status: No, score=-6.562 tagged_above=-999 required=5 tests=[AWL=0.038,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1QI4PhiV2L-q; Wed, 17 Oct 2012 17:50:19 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 52BA821F866E; Wed, 17 Oct 2012 17:50:19 -0700 (PDT)
Received: from [192.168.1.6] (adsl-67-127-59-48.dsl.pltn13.pacbell.net [67.127.59.48]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q9I0oIPi029055 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 17 Oct 2012 17:50:18 -0700
Message-ID: <507F5249.2090507@dcrocker.net>
Date: Wed, 17 Oct 2012 17:50:17 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121005 Thunderbird/16.0
MIME-Version: 1.0
To: Ned Freed <ned.freed@mrochek.com>
References: <010301cdac4d$cfa70060$6ef50120$@gmail.com> <01OLIW8VNVCU00008S@mauve.mrochek.com> <507EF95D.5090007@dcrocker.net> <01OLIXV2SU4O00008S@mauve.mrochek.com> <5B0F81787945877A5CC3794B@JcK-HP8200.jck.com> <01OLJ38YAL9600008S@mauve.mrochek.com> <507F3CEA.2010306@dcrocker.net> <01OLJ9JAK8SQ00008S@mauve.mrochek.com>
In-Reply-To: <01OLJ9JAK8SQ00008S@mauve.mrochek.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 17 Oct 2012 17:50:19 -0700 (PDT)
Cc: John C Klensin <john-ietf@jck.com>, ned+ietf@mauve.mrochek.com, gen-art@ietf.org, draft-leiba-5322upd-from-group.all@tools.ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-leiba-5322upd-from-group-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
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, 18 Oct 2012 00:50:20 -0000

On 10/17/2012 5:18 PM, Ned Freed wrote:
> If you really think this is important to explain why we're making
> this change against the overall context of RFC 5322 - and I most
> certainly do not agree that it is important to do so - then the best
> "use case" to add is the negative one: The elimination of an
> unnecessary restriction that isn't followed in practice.
>
> I see no way to explain the narrow EAI use case in this context
> without either dragging in a whole bunch of EAI that has no business
> being here or leaving various things dangling.


ack. mumble.

So I'll suggest a bit of an amalgam, including a cross reference of the 
type I prefer to avoid:

    1. State that this removes a restriction that was never essential.

    2. State that the timing of this removal is to accomodate EAI and 
for its use of the now-available features, see [RFCxxxx].

d/


-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From ned.freed@mrochek.com  Wed Oct 17 17:55:58 2012
Return-Path: <ned.freed@mrochek.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 9484321F8628 for <gen-art@ietfa.amsl.com>; Wed, 17 Oct 2012 17:55:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.529
X-Spam-Level: 
X-Spam-Status: No, score=-2.529 tagged_above=-999 required=5 tests=[AWL=0.070,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ed07GE3s+ZKK for <gen-art@ietfa.amsl.com>; Wed, 17 Oct 2012 17:55:58 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 27F3321F8623 for <gen-art@ietf.org>; Wed, 17 Oct 2012 17:55:58 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OLJA3P9BRK0009K0@mauve.mrochek.com> for gen-art@ietf.org; Wed, 17 Oct 2012 17:50:54 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OLDMMCPN8G00008S@mauve.mrochek.com>; Wed, 17 Oct 2012 17:50:51 -0700 (PDT)
Message-id: <01OLJA3N74PA00008S@mauve.mrochek.com>
Date: Wed, 17 Oct 2012 17:50:08 -0700 (PDT)
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Wed, 17 Oct 2012 19:45:58 -0400" <CALaySJLex2ozmTMByO8=mRmu-fETX-TDRk7CdMedz5nDxjT6vA@mail.gmail.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <010301cdac4d$cfa70060$6ef50120$@gmail.com> <01OLIW8VNVCU00008S@mauve.mrochek.com> <507EF95D.5090007@dcrocker.net> <01OLIXV2SU4O00008S@mauve.mrochek.com> <5B0F81787945877A5CC3794B@JcK-HP8200.jck.com> <01OLJ38YAL9600008S@mauve.mrochek.com> <507F3CEA.2010306@dcrocker.net> <CALaySJLex2ozmTMByO8=mRmu-fETX-TDRk7CdMedz5nDxjT6vA@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Cc: Ned Freed <ned.freed@mrochek.com>, draft-leiba-5322upd-from-group.all@tools.ietf.org, ned+ietf@mauve.mrochek.com, gen-art@ietf.org, dcrocker@bbiw.net, John C Klensin <john-ietf@jck.com>, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-leiba-5322upd-from-group-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, 18 Oct 2012 00:55:58 -0000

> >> Channeling my inner Maslow, I see the present text as best, an additional
> >> sentence or two as next best, a sentence and a cite to the downgrade doc
> >> next in line, and including actual EAI examples in this doc as the worst
> >> choice.
> >
> > The problem I have with the current text is that it says 'what' motivated
> > the change, but not how it is useful for the intended class of uses.  The
> > reader is left entirely to guess.

> So, is it better to put in a sentence about representing non-ASCII
> text in the group name without including a replyable address?

> Or is it better to remove the notation about the EAI use case, and
> just say that it's stupid to have the restriction, so we're removing
> it?

If the alternative is to dig into EAI in any depth at all, the latter is far
preferable.

				Ned

From david.black@emc.com  Wed Oct 17 18:12:19 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 A294421F86AB; Wed, 17 Oct 2012 18:12:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.535
X-Spam-Level: 
X-Spam-Status: No, score=-102.535 tagged_above=-999 required=5 tests=[AWL=0.064, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xd2PuNFkJr2t; Wed, 17 Oct 2012 18:12:17 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id D936421F8622; Wed, 17 Oct 2012 18:12:16 -0700 (PDT)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q9I1CCt5010771 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Oct 2012 21:12:12 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.129]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Wed, 17 Oct 2012 21:11:54 -0400
Received: from mxhub20.corp.emc.com (mxhub20.corp.emc.com [10.254.93.49]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q9I1BrQc017300; Wed, 17 Oct 2012 21:11:53 -0400
Received: from mx15a.corp.emc.com ([169.254.1.83]) by mxhub20.corp.emc.com ([10.254.93.49]) with mapi; Wed, 17 Oct 2012 21:11:53 -0400
From: "Black, David" <david.black@emc.com>
To: "Lee, Yiu" <Yiu_Lee@cable.comcast.com>, "roberta.maglione@telecomitalia.it" <roberta.maglione@telecomitalia.it>, "carlw@mcsr-labs.org" <carlw@mcsr-labs.org>, "christian.jacquenet@orange.com" <christian.jacquenet@orange.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Date: Wed, 17 Oct 2012 21:11:51 -0400
Thread-Topic: Gen-ART review of draft-ietf-softwire-dslite-deployment-06
Thread-Index: AQHNrMoAT7CfnR/9yUSA1hDdxxOKmpe+Pf7g
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7120DFAF3B9@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE7120DFAEF29@MX15A.corp.emc.com> <E3FAB1F4F41F3A45B287E8D9C53522FD37A7EC79@PACDCEXMB05.cable.comcast.com>
In-Reply-To: <E3FAB1F4F41F3A45B287E8D9C53522FD37A7EC79@PACDCEXMB05.cable.comcast.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: "softwires@ietf.org" <softwires@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-softwire-dslite-deployment-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, 18 Oct 2012 01:12:19 -0000

Yiu,

Thank you for your responses - most of them look fine, and in=20
particular anything that I don't comment on here is acceptable to me.

> [YL] In 2.2, we will add:
>=20
> "Note that reassembly at Tunnel Exit-Point is resource
> 	intensive. A large number of B4 may terminate on the same AFTR. If many =
B4
> 	fragment the packets, it would increase sufficient load to the AFTR for
> 	reassembly. We recommend the operator should increase the MTU size of th=
e IPv6
> 	network between B4 and AFTR to avoid fragmentation."

I would change "is" to "may be" in the first line.

> >[5] Section 2.8 discusses IPv4 accounting at the AFTR, but notes that
> >"the AFTR does not have detailed customer identity information."  Does
> >that create a theft of service possibility?  If so, that possibility
> >should be mentioned as a security consideration.  Also, Section 2.8
> >ought to be expanded with a sentence or two explaining why the AFTR
> >does not have that identity information, and in particular to explain
> >whether and why it is unreasonable in some or all cases to expect
> >that customer identity information be provided to the AFTR as part
> >of provisioning each customer's softwire.
>=20
> [YL] Good catch. Actually I believe AFTR "does" have both IPv4 and IPv6 t=
o
> identify the customer. I suggest we remove
>=20
> "but it will potentially introduce some additional complexity because
>    the AFTR does not have detailed customer identity information."

That's definitely an easy way to address that issue, and it's fine with me.

> >Section 2.3 on MTU Considerations could usefully mention MTU discovery
> >techniques, as possibilities for customer IPv4 traffic to adapt to a
> >smaller IPv4 MTU.  If this is done, it would be useful to mention
> >RFC 4821 in addition to the mention of RFC 1191 in RFC 6333.
>=20
> [YL] We would consider RFC 4821. However, the challenge is I don't have
> information how many current OS support RFC 4821. Since DS-lite is a
> transition technology, it would be unreasonable to ask the OS company to
> implement RFC 4821 for DS-lite.

That's ok - this was a nit.

> >- Are one or both types of logging recommended?
>=20
> [YL] We tempted to recommend source-specific log. However, some regulator=
s
> require to use both and the regulations vary country from country, this i=
s
> why we left it open and let the operators to decide.

Please add a version of your explanation to the draft.

> >In Section 2.7, I'm having a hard time understanding which traffic is
> >intended to be subject to the Outgoing Policies and the Incoming Policie=
s.
> >Expanding each of those two bullets to explain what traffic is subject
> >to each class of policies would help.
>=20
> [YL] Does this help?
>=20
> Outgoing Policies apply to packets originating from B4 to IPv4 network.
> Incoming Policies apply to packets originating from IPv4 network to B4.

Yes, that's clearer, although the B4 is not the network endpoint for any
of that traffic.  I suggest:

Outgoing Policies apply to packets originating from behind the B4 with=20
a destination on the IPv4 network.

Incoming Policies apply to packets originating from the IPv4 network to
a destination behind the B4.

Thanks,
--David


> -----Original Message-----
> From: Lee, Yiu [mailto:Yiu_Lee@cable.comcast.com]
> Sent: Wednesday, October 17, 2012 8:46 PM
> To: Black, David; roberta.maglione@telecomitalia.it; carlw@mcsr-labs.org;
> christian.jacquenet@orange.com; mohamed.boucadair@orange.com; gen-art@iet=
f.org
> Cc: softwires@ietf.org; ietf@ietf.org; Ralph Droms
> Subject: Re: Gen-ART review of draft-ietf-softwire-dslite-deployment-06
>=20
> Hi David,
>=20
> Thanks very much for review the draft. Comments inline.
>=20
> Thanks,
> Yiu
>=20
> On 10/15/12 7:10 PM, "Black, David" <david.black@emc.com> wrote:
>=20
> >I am the assigned Gen-ART reviewer for this draft. For background on
> >Gen-ART, please see the FAQ at
> ><http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >
> >Please resolve these comments along with any other Last Call comments
> >you may receive.
> >
> >Document: draft-ietf-softwire-dslite-deployment-06
> >Reviewer: David L. Black
> >Review Date: October 15, 2012
> >IETF LC End Date: October 16, 2012
> >IESG Telechat Date: October 25, 2012
> >
> >Summary:
> >
> >This draft is on the right track but has open issues, described in the
> >review.
> >
> >This is a generally well-written draft that expands considerably on the =
brief
> >deployment considerations for DS-Lite in Appendix A of RFC 6333.  The dr=
aft
> >is clear and reasonably well-written, and a significant improvement on t=
hat
> >RFC 6333 Appendix, although an understanding of RFC 6333 is necessary to
> >understand this draft, which seems completely reasonable.
> >
> >The B4 and AFTR acronyms are clever - kudos to whomever came up with
> >those.
> >
> >I found five open issues, all of which are minor.
> >
> >Minor Issues:
> >
> >[1] Ironically, the first issue is that something should be said about
> >the relationship of this draft to Appendix A of RFC 6333.  It probably
> >suffices to say that this draft expands on the material in that Appendix=
,
> >as I see no need to specify that this draft updates RFC 6333 solely to
> >change non-normative material in an Appendix.
>=20
> [YL] In "Overview", we will add:
>=20
> "This document expands Appendix A of RFC6333 and discusses various
> DS-Lite deployment considerations for operators."
>=20
> >
> >[2] The MTU increase technique in Section 2.2 is a "may", which is
> >consistent with Section 5.3 of RFC 6333.  OTOH, Section 2.2 of this
> >draft should also discuss the AFTR resource exhaustion concern that
> >described in Section 6.3 of RFC 6333, as that is a potential
> >operational reason for an ISP to increase MTU size (e.g., if customer
> >sourcing of large IPv4 packets is not sufficiently rare).
>=20
> [YL] In 2.2, we will add:
>=20
> "Note that reassembly at Tunnel Exit-Point is resource
> 	intensive. A large number of B4 may terminate on the same AFTR. If many =
B4
> 	fragment the packets, it would increase sufficient load to the AFTR for
> 	reassembly. We recommend the operator should increase the MTU size of th=
e IPv6
> 	network between B4 and AFTR to avoid fragmentation."
>=20
> >
> >[3] Section 2.7 refers to "the AFTR's internal interface".  There may be
> >two internal interfaces, the physical IPv6 interface (outer header) and
> >the tunnel's IPv4 interface (inner header).  The text should be clarifie=
d
> >to indicate which interface is involved - it appears that the AFTR's
> >physical IPv6 interface is intended in this section.
>=20
> [YL] We replace "internal" to "IPv6"
>=20
> >
> >[4] Section 2.7 cites RFC 6333 for use of DHCPv6 with DS-Lite.  RFC 6334
> >should be cited - either in addition to or instead of RFC 6333.
>=20
> [YL] Fixed
>=20
> >
> >[5] Section 2.8 discusses IPv4 accounting at the AFTR, but notes that
> >"the AFTR does not have detailed customer identity information."  Does
> >that create a theft of service possibility?  If so, that possibility
> >should be mentioned as a security consideration.  Also, Section 2.8
> >ought to be expanded with a sentence or two explaining why the AFTR
> >does not have that identity information, and in particular to explain
> >whether and why it is unreasonable in some or all cases to expect
> >that customer identity information be provided to the AFTR as part
> >of provisioning each customer's softwire.
>=20
> [YL] Good catch. Actually I believe AFTR "does" have both IPv4 and IPv6 t=
o
> identify the customer. I suggest we remove
>=20
> "but it will potentially introduce some additional complexity because
>    the AFTR does not have detailed customer identity information."
>=20
> >
> >Nits:
> >
> >Section 2.3 on MTU Considerations could usefully mention MTU discovery
> >techniques, as possibilities for customer IPv4 traffic to adapt to a
> >smaller IPv4 MTU.  If this is done, it would be useful to mention
> >RFC 4821 in addition to the mention of RFC 1191 in RFC 6333.
>=20
> [YL] We would consider RFC 4821. However, the challenge is I don't have
> information how many current OS support RFC 4821. Since DS-lite is a
> transition technology, it would be unreasonable to ask the OS company to
> implement RFC 4821 for DS-lite.
>=20
> >
> >Section 2.4 should define "lawful intercept".  It would be helpful to
> >cite a reference for this concept if something appropriate can be found.
>=20
> [YL] We will find whether there is any reference to this concept. If we
> can't find any, we would add an explanation in the draft.
>=20
> >
> >Section 2.5:
> >- Are one or both types of logging recommended?
>=20
> [YL] We tempted to recommend source-specific log. However, some regulator=
s
> require to use both and the regulations vary country from country, this i=
s
> why we left it open and let the operators to decide.
>=20
> >- Last paragraph on p.4, "timestamped log" is not a good verb phrase.
> >	"maintain a timestamped log of" would be a better replacement.
>=20
> [YL] Fixed
>=20
> >- Last paragraph in section, where is the batch file sent?
>=20
> [YL] We will add:
>=20
> "The files may be compressed before transferring to a repository server
> 	to better utilize bandwidth and storage."
>=20
>=20
> >
> >In Section 2.7, I'm having a hard time understanding which traffic is
> >intended to be subject to the Outgoing Policies and the Incoming Policie=
s.
> >Expanding each of those two bullets to explain what traffic is subject
> >to each class of policies would help.
>=20
> [YL] Does this help?
>=20
> Outgoing Policies apply to packets originating from B4 to IPv4 network.
> Incoming Policies apply to packets originating from IPv4 network to B4.
>=20
>=20
>=20
> >
> >Section 3.2.2.2 uses 192.0.0.2/32 as an example IP address for the
> >B4.  That section should also cross-reference Section 5.7 on RFC 6333
> >on IP address assignment to B4s, as other IP addresses may be used.
>=20
> [YL] Added the cite.
>=20
> >
> >idnits 2.12.13 found a tiny nit - draft-ietf-pcp-base is now at
> >version 28.
>=20
> [YL] Fixed.
>=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
> >----------------------------------------------------
> >
> >

From roberta.maglione@telecomitalia.it  Thu Oct 18 00:12:50 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 24F4C21F85F7; Thu, 18 Oct 2012 00:12:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.487
X-Spam-Level: 
X-Spam-Status: No, score=-1.487 tagged_above=-999 required=5 tests=[AWL=0.232,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fvLH0GT6KgLz; Thu, 18 Oct 2012 00:12:49 -0700 (PDT)
Received: from GRFEDG701BA020.telecomitalia.it (grfedg701ba020.telecomitalia.it [156.54.233.200]) by ietfa.amsl.com (Postfix) with ESMTP id 6879E21F85A7; Thu, 18 Oct 2012 00:12:40 -0700 (PDT)
Received: from grfhub704ba020.griffon.local (10.188.101.117) by GRFEDG701BA020.telecomitalia.it (10.188.45.100) with Microsoft SMTP Server (TLS) id 8.3.279.5; Thu, 18 Oct 2012 09:12:31 +0200
Received: from GRFMBX704BA020.griffon.local ([10.188.101.15]) by grfhub704ba020.griffon.local ([10.188.101.117]) with mapi; Thu, 18 Oct 2012 09:12:29 +0200
From: Maglione Roberta <roberta.maglione@telecomitalia.it>
To: "'Black, David'" <david.black@emc.com>, "Lee, Yiu" <Yiu_Lee@cable.comcast.com>, "carlw@mcsr-labs.org" <carlw@mcsr-labs.org>, "christian.jacquenet@orange.com" <christian.jacquenet@orange.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Date: Thu, 18 Oct 2012 09:12:29 +0200
Thread-Topic: Gen-ART review of draft-ietf-softwire-dslite-deployment-06
Thread-Index: AQHNrMoAT7CfnR/9yUSA1hDdxxOKmpe+Pf7ggABl0SA=
Message-ID: <282BBE8A501E1F4DA9C775F964BB21FE519702F258@GRFMBX704BA020.griffon.local>
References: <8D3D17ACE214DC429325B2B98F3AE7120DFAEF29@MX15A.corp.emc.com> <E3FAB1F4F41F3A45B287E8D9C53522FD37A7EC79@PACDCEXMB05.cable.comcast.com> <8D3D17ACE214DC429325B2B98F3AE7120DFAF3B9@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7120DFAF3B9@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-ti-disclaimer: Disclaimer1
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "softwires@ietf.org" <softwires@ietf.org>, Ullio Mario <mario.ullio@telecomitalia.it>, "ietf@ietf.org" <ietf@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-softwire-dslite-deployment-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, 18 Oct 2012 07:12:50 -0000

Hello Yiu and David,
regarding point 5:

> [YL] Good catch. Actually I believe AFTR "does" have both IPv4 and IPv6 t=
o
> identify the customer. I suggest we remove
>
> "but it will potentially introduce some additional complexity because
>    the AFTR does not have detailed customer identity information."

The point related to the accounting is different: what I meant here with ac=
counting is RADIUS based accounting, commonly used in Broadband networks.

Today RADIUS accounting is done at the BNG level, the problem with the intr=
oduction of the AFTR is that the AFTR does not interact with AAA/RADIUS Ser=
ver for the initial authentication/authorization/accounting phase because t=
he authentication/authorization/accounting process happens between BNG and =
RADIUS Server when the session comes up.
The ATFR is not able to perform RADIUS accounting because as it does not in=
teract with the RADIUS Server it does not have " detailed customer identity=
 information" for example it does know the accounting session ID associated=
 to that session, that's why it cannot do detailed accounting for each sing=
le subscriber even if the ATFR can still correlated IPv6 and IPv4 traffic b=
elonging to the same user.

This is an important operational issue, I would suggest to keep this concep=
t. If you think is needed I can add some lines of text in order to clarify =
this point.

Thanks
Regards,
Roberta
-----Original Message-----
From: Black, David [mailto:david.black@emc.com]
Sent: Thursday, October 18, 2012 3:12 AM
To: Lee, Yiu; Maglione Roberta; carlw@mcsr-labs.org; christian.jacquenet@or=
ange.com; mohamed.boucadair@orange.com; gen-art@ietf.org
Cc: softwires@ietf.org; ietf@ietf.org; Ralph Droms; Black, David
Subject: RE: Gen-ART review of draft-ietf-softwire-dslite-deployment-06

Yiu,

Thank you for your responses - most of them look fine, and in
particular anything that I don't comment on here is acceptable to me.

> [YL] In 2.2, we will add:
>
> "Note that reassembly at Tunnel Exit-Point is resource
>       intensive. A large number of B4 may terminate on the same AFTR. If =
many B4
>       fragment the packets, it would increase sufficient load to the AFTR=
 for
>       reassembly. We recommend the operator should increase the MTU size =
of the IPv6
>       network between B4 and AFTR to avoid fragmentation."

I would change "is" to "may be" in the first line.

> >[5] Section 2.8 discusses IPv4 accounting at the AFTR, but notes that
> >"the AFTR does not have detailed customer identity information."  Does
> >that create a theft of service possibility?  If so, that possibility
> >should be mentioned as a security consideration.  Also, Section 2.8
> >ought to be expanded with a sentence or two explaining why the AFTR
> >does not have that identity information, and in particular to explain
> >whether and why it is unreasonable in some or all cases to expect
> >that customer identity information be provided to the AFTR as part
> >of provisioning each customer's softwire.
>
> [YL] Good catch. Actually I believe AFTR "does" have both IPv4 and IPv6 t=
o
> identify the customer. I suggest we remove
>
> "but it will potentially introduce some additional complexity because
>    the AFTR does not have detailed customer identity information."

That's definitely an easy way to address that issue, and it's fine with me.

> >Section 2.3 on MTU Considerations could usefully mention MTU discovery
> >techniques, as possibilities for customer IPv4 traffic to adapt to a
> >smaller IPv4 MTU.  If this is done, it would be useful to mention
> >RFC 4821 in addition to the mention of RFC 1191 in RFC 6333.
>
> [YL] We would consider RFC 4821. However, the challenge is I don't have
> information how many current OS support RFC 4821. Since DS-lite is a
> transition technology, it would be unreasonable to ask the OS company to
> implement RFC 4821 for DS-lite.

That's ok - this was a nit.

> >- Are one or both types of logging recommended?
>
> [YL] We tempted to recommend source-specific log. However, some regulator=
s
> require to use both and the regulations vary country from country, this i=
s
> why we left it open and let the operators to decide.

Please add a version of your explanation to the draft.

> >In Section 2.7, I'm having a hard time understanding which traffic is
> >intended to be subject to the Outgoing Policies and the Incoming Policie=
s.
> >Expanding each of those two bullets to explain what traffic is subject
> >to each class of policies would help.
>
> [YL] Does this help?
>
> Outgoing Policies apply to packets originating from B4 to IPv4 network.
> Incoming Policies apply to packets originating from IPv4 network to B4.

Yes, that's clearer, although the B4 is not the network endpoint for any
of that traffic.  I suggest:

Outgoing Policies apply to packets originating from behind the B4 with
a destination on the IPv4 network.

Incoming Policies apply to packets originating from the IPv4 network to
a destination behind the B4.

Thanks,
--David


> -----Original Message-----
> From: Lee, Yiu [mailto:Yiu_Lee@cable.comcast.com]
> Sent: Wednesday, October 17, 2012 8:46 PM
> To: Black, David; roberta.maglione@telecomitalia.it; carlw@mcsr-labs.org;
> christian.jacquenet@orange.com; mohamed.boucadair@orange.com; gen-art@iet=
f.org
> Cc: softwires@ietf.org; ietf@ietf.org; Ralph Droms
> Subject: Re: Gen-ART review of draft-ietf-softwire-dslite-deployment-06
>
> Hi David,
>
> Thanks very much for review the draft. Comments inline.
>
> Thanks,
> Yiu
>
> On 10/15/12 7:10 PM, "Black, David" <david.black@emc.com> wrote:
>
> >I am the assigned Gen-ART reviewer for this draft. For background on
> >Gen-ART, please see the FAQ at
> ><http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >
> >Please resolve these comments along with any other Last Call comments
> >you may receive.
> >
> >Document: draft-ietf-softwire-dslite-deployment-06
> >Reviewer: David L. Black
> >Review Date: October 15, 2012
> >IETF LC End Date: October 16, 2012
> >IESG Telechat Date: October 25, 2012
> >
> >Summary:
> >
> >This draft is on the right track but has open issues, described in the
> >review.
> >
> >This is a generally well-written draft that expands considerably on the =
brief
> >deployment considerations for DS-Lite in Appendix A of RFC 6333.  The dr=
aft
> >is clear and reasonably well-written, and a significant improvement on t=
hat
> >RFC 6333 Appendix, although an understanding of RFC 6333 is necessary to
> >understand this draft, which seems completely reasonable.
> >
> >The B4 and AFTR acronyms are clever - kudos to whomever came up with
> >those.
> >
> >I found five open issues, all of which are minor.
> >
> >Minor Issues:
> >
> >[1] Ironically, the first issue is that something should be said about
> >the relationship of this draft to Appendix A of RFC 6333.  It probably
> >suffices to say that this draft expands on the material in that Appendix=
,
> >as I see no need to specify that this draft updates RFC 6333 solely to
> >change non-normative material in an Appendix.
>
> [YL] In "Overview", we will add:
>
> "This document expands Appendix A of RFC6333 and discusses various
> DS-Lite deployment considerations for operators."
>
> >
> >[2] The MTU increase technique in Section 2.2 is a "may", which is
> >consistent with Section 5.3 of RFC 6333.  OTOH, Section 2.2 of this
> >draft should also discuss the AFTR resource exhaustion concern that
> >described in Section 6.3 of RFC 6333, as that is a potential
> >operational reason for an ISP to increase MTU size (e.g., if customer
> >sourcing of large IPv4 packets is not sufficiently rare).
>
> [YL] In 2.2, we will add:
>
> "Note that reassembly at Tunnel Exit-Point is resource
>       intensive. A large number of B4 may terminate on the same AFTR. If =
many B4
>       fragment the packets, it would increase sufficient load to the AFTR=
 for
>       reassembly. We recommend the operator should increase the MTU size =
of the IPv6
>       network between B4 and AFTR to avoid fragmentation."
>
> >
> >[3] Section 2.7 refers to "the AFTR's internal interface".  There may be
> >two internal interfaces, the physical IPv6 interface (outer header) and
> >the tunnel's IPv4 interface (inner header).  The text should be clarifie=
d
> >to indicate which interface is involved - it appears that the AFTR's
> >physical IPv6 interface is intended in this section.
>
> [YL] We replace "internal" to "IPv6"
>
> >
> >[4] Section 2.7 cites RFC 6333 for use of DHCPv6 with DS-Lite.  RFC 6334
> >should be cited - either in addition to or instead of RFC 6333.
>
> [YL] Fixed
>
> >
> >[5] Section 2.8 discusses IPv4 accounting at the AFTR, but notes that
> >"the AFTR does not have detailed customer identity information."  Does
> >that create a theft of service possibility?  If so, that possibility
> >should be mentioned as a security consideration.  Also, Section 2.8
> >ought to be expanded with a sentence or two explaining why the AFTR
> >does not have that identity information, and in particular to explain
> >whether and why it is unreasonable in some or all cases to expect
> >that customer identity information be provided to the AFTR as part
> >of provisioning each customer's softwire.
>
> [YL] Good catch. Actually I believe AFTR "does" have both IPv4 and IPv6 t=
o
> identify the customer. I suggest we remove
>
> "but it will potentially introduce some additional complexity because
>    the AFTR does not have detailed customer identity information."
>
> >
> >Nits:
> >
> >Section 2.3 on MTU Considerations could usefully mention MTU discovery
> >techniques, as possibilities for customer IPv4 traffic to adapt to a
> >smaller IPv4 MTU.  If this is done, it would be useful to mention
> >RFC 4821 in addition to the mention of RFC 1191 in RFC 6333.
>
> [YL] We would consider RFC 4821. However, the challenge is I don't have
> information how many current OS support RFC 4821. Since DS-lite is a
> transition technology, it would be unreasonable to ask the OS company to
> implement RFC 4821 for DS-lite.
>
> >
> >Section 2.4 should define "lawful intercept".  It would be helpful to
> >cite a reference for this concept if something appropriate can be found.
>
> [YL] We will find whether there is any reference to this concept. If we
> can't find any, we would add an explanation in the draft.
>
> >
> >Section 2.5:
> >- Are one or both types of logging recommended?
>
> [YL] We tempted to recommend source-specific log. However, some regulator=
s
> require to use both and the regulations vary country from country, this i=
s
> why we left it open and let the operators to decide.
>
> >- Last paragraph on p.4, "timestamped log" is not a good verb phrase.
> >     "maintain a timestamped log of" would be a better replacement.
>
> [YL] Fixed
>
> >- Last paragraph in section, where is the batch file sent?
>
> [YL] We will add:
>
> "The files may be compressed before transferring to a repository server
>       to better utilize bandwidth and storage."
>
>
> >
> >In Section 2.7, I'm having a hard time understanding which traffic is
> >intended to be subject to the Outgoing Policies and the Incoming Policie=
s.
> >Expanding each of those two bullets to explain what traffic is subject
> >to each class of policies would help.
>
> [YL] Does this help?
>
> Outgoing Policies apply to packets originating from B4 to IPv4 network.
> Incoming Policies apply to packets originating from IPv4 network to B4.
>
>
>
> >
> >Section 3.2.2.2 uses 192.0.0.2/32 as an example IP address for the
> >B4.  That section should also cross-reference Section 5.7 on RFC 6333
> >on IP address assignment to B4s, as other IP addresses may be used.
>
> [YL] Added the cite.
>
> >
> >idnits 2.12.13 found a tiny nit - draft-ietf-pcp-base is now at
> >version 28.
>
> [YL] Fixed.
>
> >
> >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
> >----------------------------------------------------
> >
> >

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 roberta.maglione@telecomitalia.it  Thu Oct 18 00:18:07 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 2C7E521F85B4 for <gen-art@ietfa.amsl.com>; Thu, 18 Oct 2012 00:18:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.533
X-Spam-Level: 
X-Spam-Status: No, score=-1.533 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WvlLep6bd5ZF for <gen-art@ietfa.amsl.com>; Thu, 18 Oct 2012 00:18:06 -0700 (PDT)
Received: from GRFEDG701BA020.telecomitalia.it (grfedg701ba020.telecomitalia.it [156.54.233.200]) by ietfa.amsl.com (Postfix) with ESMTP id 6F83621F857D for <gen-art@ietf.org>; Thu, 18 Oct 2012 00:18:05 -0700 (PDT)
Received: from GRFHUB702BA020.griffon.local (10.188.101.112) by GRFEDG701BA020.telecomitalia.it (10.188.45.100) with Microsoft SMTP Server (TLS) id 8.3.279.5; Thu, 18 Oct 2012 09:18:01 +0200
Received: from GRFMBX704BA020.griffon.local ([10.188.101.15]) by GRFHUB702BA020.griffon.local ([10.188.101.112]) with mapi; Thu, 18 Oct 2012 09:17:59 +0200
From: Maglione Roberta <roberta.maglione@telecomitalia.it>
To: "'Black, David'" <david.black@emc.com>, "Lee, Yiu" <Yiu_Lee@cable.comcast.com>, "'draft-ietf-softwire-dslite-deployment@tools.ietf.org'" <draft-ietf-softwire-dslite-deployment@tools.ietf.org>
Date: Thu, 18 Oct 2012 09:18:00 +0200
Thread-Topic: Gen-ART review of draft-ietf-softwire-dslite-deployment-06
Thread-Index: AQHNrMoAT7CfnR/9yUSA1hDdxxOKmpe+Pf7ggABprIA=
Message-ID: <282BBE8A501E1F4DA9C775F964BB21FE519702F25A@GRFMBX704BA020.griffon.local>
References: <8D3D17ACE214DC429325B2B98F3AE7120DFAEF29@MX15A.corp.emc.com> <E3FAB1F4F41F3A45B287E8D9C53522FD37A7EC79@PACDCEXMB05.cable.comcast.com> <8D3D17ACE214DC429325B2B98F3AE7120DFAF3B9@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7120DFAF3B9@MX15A.corp.emc.com>
Accept-Language: en-US, it-IT
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, it-IT
x-ti-disclaimer: Disclaimer1
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>, "softwire-chairs@tools.ietf.org" <softwire-chairs@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-softwire-dslite-deployment-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, 18 Oct 2012 07:18:07 -0000

Hello Yiu and David,
regarding point 5:

> [YL] Good catch. Actually I believe AFTR "does" have both IPv4 and
> IPv6 to identify the customer. I suggest we remove
>
> "but it will potentially introduce some additional complexity because
>    the AFTR does not have detailed customer identity information."

The point related to the accounting is different: what I meant here with ac=
counting is RADIUS based accounting, commonly used in Broadband networks.

Today RADIUS accounting is done at the BNG level, the problem with the intr=
oduction of the AFTR is that the AFTR does not interact with AAA/RADIUS Ser=
ver for the initial authentication/authorization/accounting phase because t=
he authentication/authorization/accounting process happens between BNG and =
RADIUS Server when the session comes up.
The ATFR is not able to perform RADIUS accounting because as it does not in=
teract with the RADIUS Server it does not have " detailed customer identity=
 information" for example it does know the accounting session ID associated=
 to that session, that's why it cannot do detailed accounting for each sing=
le subscriber even if the ATFR can still correlated IPv6 and IPv4 traffic b=
elonging to the same user.

This is an important operational issue, I would suggest to keep this concep=
t. If you think is needed I can add some lines of text in order to clarify =
this point.

Thanks
Regards,
Roberta

-----Original Message-----
From: Black, David [mailto:david.black@emc.com]
Sent: Thursday, October 18, 2012 3:12 AM
To: Lee, Yiu; Maglione Roberta; carlw@mcsr-labs.org; christian.jacquenet@or=
ange.com; mohamed.boucadair@orange.com; gen-art@ietf.org
Cc: softwires@ietf.org; ietf@ietf.org; Ralph Droms; Black, David
Subject: RE: Gen-ART review of draft-ietf-softwire-dslite-deployment-06

Yiu,

Thank you for your responses - most of them look fine, and in
particular anything that I don't comment on here is acceptable to me.

> [YL] In 2.2, we will add:
>
> "Note that reassembly at Tunnel Exit-Point is resource
>       intensive. A large number of B4 may terminate on the same AFTR. If =
many B4
>       fragment the packets, it would increase sufficient load to the AFTR=
 for
>       reassembly. We recommend the operator should increase the MTU size =
of the IPv6
>       network between B4 and AFTR to avoid fragmentation."

I would change "is" to "may be" in the first line.

> >[5] Section 2.8 discusses IPv4 accounting at the AFTR, but notes that
> >"the AFTR does not have detailed customer identity information."  Does
> >that create a theft of service possibility?  If so, that possibility
> >should be mentioned as a security consideration.  Also, Section 2.8
> >ought to be expanded with a sentence or two explaining why the AFTR
> >does not have that identity information, and in particular to explain
> >whether and why it is unreasonable in some or all cases to expect
> >that customer identity information be provided to the AFTR as part
> >of provisioning each customer's softwire.
>
> [YL] Good catch. Actually I believe AFTR "does" have both IPv4 and IPv6 t=
o
> identify the customer. I suggest we remove
>
> "but it will potentially introduce some additional complexity because
>    the AFTR does not have detailed customer identity information."

That's definitely an easy way to address that issue, and it's fine with me.

> >Section 2.3 on MTU Considerations could usefully mention MTU discovery
> >techniques, as possibilities for customer IPv4 traffic to adapt to a
> >smaller IPv4 MTU.  If this is done, it would be useful to mention
> >RFC 4821 in addition to the mention of RFC 1191 in RFC 6333.
>
> [YL] We would consider RFC 4821. However, the challenge is I don't have
> information how many current OS support RFC 4821. Since DS-lite is a
> transition technology, it would be unreasonable to ask the OS company to
> implement RFC 4821 for DS-lite.

That's ok - this was a nit.

> >- Are one or both types of logging recommended?
>
> [YL] We tempted to recommend source-specific log. However, some regulator=
s
> require to use both and the regulations vary country from country, this i=
s
> why we left it open and let the operators to decide.

Please add a version of your explanation to the draft.

> >In Section 2.7, I'm having a hard time understanding which traffic is
> >intended to be subject to the Outgoing Policies and the Incoming Policie=
s.
> >Expanding each of those two bullets to explain what traffic is subject
> >to each class of policies would help.
>
> [YL] Does this help?
>
> Outgoing Policies apply to packets originating from B4 to IPv4 network.
> Incoming Policies apply to packets originating from IPv4 network to B4.

Yes, that's clearer, although the B4 is not the network endpoint for any
of that traffic.  I suggest:

Outgoing Policies apply to packets originating from behind the B4 with
a destination on the IPv4 network.

Incoming Policies apply to packets originating from the IPv4 network to
a destination behind the B4.

Thanks,
--David


> -----Original Message-----
> From: Lee, Yiu [mailto:Yiu_Lee@cable.comcast.com]
> Sent: Wednesday, October 17, 2012 8:46 PM
> To: Black, David; roberta.maglione@telecomitalia.it; carlw@mcsr-labs.org;
> christian.jacquenet@orange.com; mohamed.boucadair@orange.com; gen-art@iet=
f.org
> Cc: softwires@ietf.org; ietf@ietf.org; Ralph Droms
> Subject: Re: Gen-ART review of draft-ietf-softwire-dslite-deployment-06
>
> Hi David,
>
> Thanks very much for review the draft. Comments inline.
>
> Thanks,
> Yiu
>
> On 10/15/12 7:10 PM, "Black, David" <david.black@emc.com> wrote:
>
> >I am the assigned Gen-ART reviewer for this draft. For background on
> >Gen-ART, please see the FAQ at
> ><http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >
> >Please resolve these comments along with any other Last Call comments
> >you may receive.
> >
> >Document: draft-ietf-softwire-dslite-deployment-06
> >Reviewer: David L. Black
> >Review Date: October 15, 2012
> >IETF LC End Date: October 16, 2012
> >IESG Telechat Date: October 25, 2012
> >
> >Summary:
> >
> >This draft is on the right track but has open issues, described in the
> >review.
> >
> >This is a generally well-written draft that expands considerably on the =
brief
> >deployment considerations for DS-Lite in Appendix A of RFC 6333.  The dr=
aft
> >is clear and reasonably well-written, and a significant improvement on t=
hat
> >RFC 6333 Appendix, although an understanding of RFC 6333 is necessary to
> >understand this draft, which seems completely reasonable.
> >
> >The B4 and AFTR acronyms are clever - kudos to whomever came up with
> >those.
> >
> >I found five open issues, all of which are minor.
> >
> >Minor Issues:
> >
> >[1] Ironically, the first issue is that something should be said about
> >the relationship of this draft to Appendix A of RFC 6333.  It probably
> >suffices to say that this draft expands on the material in that Appendix=
,
> >as I see no need to specify that this draft updates RFC 6333 solely to
> >change non-normative material in an Appendix.
>
> [YL] In "Overview", we will add:
>
> "This document expands Appendix A of RFC6333 and discusses various
> DS-Lite deployment considerations for operators."
>
> >
> >[2] The MTU increase technique in Section 2.2 is a "may", which is
> >consistent with Section 5.3 of RFC 6333.  OTOH, Section 2.2 of this
> >draft should also discuss the AFTR resource exhaustion concern that
> >described in Section 6.3 of RFC 6333, as that is a potential
> >operational reason for an ISP to increase MTU size (e.g., if customer
> >sourcing of large IPv4 packets is not sufficiently rare).
>
> [YL] In 2.2, we will add:
>
> "Note that reassembly at Tunnel Exit-Point is resource
>       intensive. A large number of B4 may terminate on the same AFTR. If =
many B4
>       fragment the packets, it would increase sufficient load to the AFTR=
 for
>       reassembly. We recommend the operator should increase the MTU size =
of the IPv6
>       network between B4 and AFTR to avoid fragmentation."
>
> >
> >[3] Section 2.7 refers to "the AFTR's internal interface".  There may be
> >two internal interfaces, the physical IPv6 interface (outer header) and
> >the tunnel's IPv4 interface (inner header).  The text should be clarifie=
d
> >to indicate which interface is involved - it appears that the AFTR's
> >physical IPv6 interface is intended in this section.
>
> [YL] We replace "internal" to "IPv6"
>
> >
> >[4] Section 2.7 cites RFC 6333 for use of DHCPv6 with DS-Lite.  RFC 6334
> >should be cited - either in addition to or instead of RFC 6333.
>
> [YL] Fixed
>
> >
> >[5] Section 2.8 discusses IPv4 accounting at the AFTR, but notes that
> >"the AFTR does not have detailed customer identity information."  Does
> >that create a theft of service possibility?  If so, that possibility
> >should be mentioned as a security consideration.  Also, Section 2.8
> >ought to be expanded with a sentence or two explaining why the AFTR
> >does not have that identity information, and in particular to explain
> >whether and why it is unreasonable in some or all cases to expect
> >that customer identity information be provided to the AFTR as part
> >of provisioning each customer's softwire.
>
> [YL] Good catch. Actually I believe AFTR "does" have both IPv4 and IPv6 t=
o
> identify the customer. I suggest we remove
>
> "but it will potentially introduce some additional complexity because
>    the AFTR does not have detailed customer identity information."
>
> >
> >Nits:
> >
> >Section 2.3 on MTU Considerations could usefully mention MTU discovery
> >techniques, as possibilities for customer IPv4 traffic to adapt to a
> >smaller IPv4 MTU.  If this is done, it would be useful to mention
> >RFC 4821 in addition to the mention of RFC 1191 in RFC 6333.
>
> [YL] We would consider RFC 4821. However, the challenge is I don't have
> information how many current OS support RFC 4821. Since DS-lite is a
> transition technology, it would be unreasonable to ask the OS company to
> implement RFC 4821 for DS-lite.
>
> >
> >Section 2.4 should define "lawful intercept".  It would be helpful to
> >cite a reference for this concept if something appropriate can be found.
>
> [YL] We will find whether there is any reference to this concept. If we
> can't find any, we would add an explanation in the draft.
>
> >
> >Section 2.5:
> >- Are one or both types of logging recommended?
>
> [YL] We tempted to recommend source-specific log. However, some regulator=
s
> require to use both and the regulations vary country from country, this i=
s
> why we left it open and let the operators to decide.
>
> >- Last paragraph on p.4, "timestamped log" is not a good verb phrase.
> >     "maintain a timestamped log of" would be a better replacement.
>
> [YL] Fixed
>
> >- Last paragraph in section, where is the batch file sent?
>
> [YL] We will add:
>
> "The files may be compressed before transferring to a repository server
>       to better utilize bandwidth and storage."
>
>
> >
> >In Section 2.7, I'm having a hard time understanding which traffic is
> >intended to be subject to the Outgoing Policies and the Incoming Policie=
s.
> >Expanding each of those two bullets to explain what traffic is subject
> >to each class of policies would help.
>
> [YL] Does this help?
>
> Outgoing Policies apply to packets originating from B4 to IPv4 network.
> Incoming Policies apply to packets originating from IPv4 network to B4.
>
>
>
> >
> >Section 3.2.2.2 uses 192.0.0.2/32 as an example IP address for the
> >B4.  That section should also cross-reference Section 5.7 on RFC 6333
> >on IP address assignment to B4s, as other IP addresses may be used.
>
> [YL] Added the cite.
>
> >
> >idnits 2.12.13 found a tiny nit - draft-ietf-pcp-base is now at
> >version 28.
>
> [YL] Fixed.
>
> >
> >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
> >----------------------------------------------------
> >
> >

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 barryleiba@gmail.com  Thu Oct 18 04:13:19 2012
Return-Path: <barryleiba@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 EC19D21F8688; Thu, 18 Oct 2012 04:13:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.094
X-Spam-Level: 
X-Spam-Status: No, score=-103.094 tagged_above=-999 required=5 tests=[AWL=-0.117, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fsoRT7XUQYD9; Thu, 18 Oct 2012 04:13:18 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 12A1A21F8685; Thu, 18 Oct 2012 04:13:15 -0700 (PDT)
Received: by mail-vb0-f44.google.com with SMTP id fc26so9552156vbb.31 for <multiple recipients>; Thu, 18 Oct 2012 04:13:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=W/U2vijy17iOKl5oFvrgrbw60CdbhHBXVW+6pjwNehY=; b=ijRH4MbTkO93i+Ofz6sIQpxKcHeK2uyWww90Uckeqfqlj0TY4YwPk0Y6rw/ABC1iH7 o/MbT1xpHhPCFnaX7ATsurmhI4KgG1ILV5tSrwpNPkqEC7rzMRJB7Oz/Mro2VLiPMptl bVUMOlKEPt1AFgWb35UQCB5NBefN5Ufeeb/ZYxDb0NnNzCF2ljh777cPYBkp7ukS+aDo WPVG1e0vK/5JW9MZjTYS53ZvpfCm6gv7HRiwWRYDIvuk+n1Z1rmyGVsIeefBAbwPA0uz gYAV24WBXEhQ22Q/M1b625CSz26pgkvAeL4N4uxLK3beo8+Jdk8/AzHOpDCacWB/RuXZ y8Og==
MIME-Version: 1.0
Received: by 10.58.86.36 with SMTP id m4mr14950266vez.14.1350558795399; Thu, 18 Oct 2012 04:13:15 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.58.28.231 with HTTP; Thu, 18 Oct 2012 04:13:15 -0700 (PDT)
In-Reply-To: <507F5249.2090507@dcrocker.net>
References: <010301cdac4d$cfa70060$6ef50120$@gmail.com> <01OLIW8VNVCU00008S@mauve.mrochek.com> <507EF95D.5090007@dcrocker.net> <01OLIXV2SU4O00008S@mauve.mrochek.com> <5B0F81787945877A5CC3794B@JcK-HP8200.jck.com> <01OLJ38YAL9600008S@mauve.mrochek.com> <507F3CEA.2010306@dcrocker.net> <01OLJ9JAK8SQ00008S@mauve.mrochek.com> <507F5249.2090507@dcrocker.net>
Date: Thu, 18 Oct 2012 07:13:15 -0400
X-Google-Sender-Auth: JuQ-vsnNQA2rdg_REp7--4tWNRU
Message-ID: <CALaySJKD+JbkOuZsC7wQtNNLHBP-4a_=DNfQ0XkQWoCq78-JGg@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: dcrocker@bbiw.net
Content-Type: text/plain; charset=ISO-8859-1
Cc: Ned Freed <ned.freed@mrochek.com>, draft-leiba-5322upd-from-group.all@tools.ietf.org, ned+ietf@mauve.mrochek.com, gen-art@ietf.org, johnl@taugh.com, John C Klensin <john-ietf@jck.com>, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-leiba-5322upd-from-group-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, 18 Oct 2012 11:13:19 -0000

On Wed, Oct 17, 2012 at 8:50 PM, Dave Crocker <dhc@dcrocker.net> wrote:
>> I see no way to explain the narrow EAI use case in this context
>> without either dragging in a whole bunch of EAI that has no business
>> being here or leaving various things dangling.
>
> ack. mumble.
>
> So I'll suggest a bit of an amalgam, including a cross reference of the type
> I prefer to avoid:
>
>    1. State that this removes a restriction that was never essential.
>
>    2. State that the timing of this removal is to accomodate EAI and for its
> use of the now-available features, see [RFCxxxx].


On Thu, Oct 18, 2012 at 6:28 AM, John Levine <johnl@taugh.com> wrote
(with a large part of this distribution list removed):
>>So, is it better to put in a sentence about representing non-ASCII
>>text in the group name without including a replyable address?
>
> The main motivation is to provide a syntax for a non-replyable address
> in From: and Sender: headers for cases where that is appropriate.  See
> the EAI downgrade documents for a concrete example.
>
> A secondary motivation is to remove an arcane restriction that has not
> turned out to be useful in practice.

Dave and John (Levine) are both suggesting an informative reference
from this document to some piece of the EAI documents (which I guess
should be one or both of draft-ietf-eai-5738bis, Section 7, and
draft-ietf-eai-popimap-downgrade, Section 3.2.1).

Ned and John (Klensin), can you live with that (I know it's not your
preference).  All: which (or both) should the reference be to?

Barry

From yiu_lee@cable.comcast.com  Thu Oct 18 05:29:16 2012
Return-Path: <yiu_lee@cable.comcast.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 A0E1021F8618; Thu, 18 Oct 2012 05:29:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.109
X-Spam-Level: 
X-Spam-Status: No, score=-102.109 tagged_above=-999 required=5 tests=[AWL=-1.212, BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZTTy9bLOhn0U; Thu, 18 Oct 2012 05:29:15 -0700 (PDT)
Received: from cable.comcast.com (pacdcavout01.cable.comcast.com [69.241.43.119]) by ietfa.amsl.com (Postfix) with ESMTP id 2862221F85F4; Thu, 18 Oct 2012 05:29:15 -0700 (PDT)
Received: from ([24.40.56.115]) by pacdcavout01.cable.comcast.com with ESMTP  id 97wm3m1.30860935; Thu, 18 Oct 2012 08:22:04 -0400
Received: from PACDCEXMB05.cable.comcast.com ([169.254.7.147]) by PACDCEXHUB02.cable.comcast.com ([fe80::492e:3fa1:c2ad:e04e%13]) with mapi id 14.02.0318.001; Thu, 18 Oct 2012 08:29:10 -0400
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: "Black, David" <david.black@emc.com>, "roberta.maglione@telecomitalia.it" <roberta.maglione@telecomitalia.it>, "carlw@mcsr-labs.org" <carlw@mcsr-labs.org>, "christian.jacquenet@orange.com" <christian.jacquenet@orange.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART review of draft-ietf-softwire-dslite-deployment-06
Thread-Index: AQHNrSwstZEiPeUY0EatIphU3ATEWA==
Date: Thu, 18 Oct 2012 12:29:09 +0000
Message-ID: <E3FAB1F4F41F3A45B287E8D9C53522FD37A7F8BD@PACDCEXMB05.cable.comcast.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7120DFAF3B9@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.4.120824
x-originating-ip: [24.40.55.70]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3433393748_19694"
MIME-Version: 1.0
Cc: "softwires@ietf.org" <softwires@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-softwire-dslite-deployment-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, 18 Oct 2012 12:29:16 -0000

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

Thanks David! I will apply your changes to the next version.

On 10/17/12 9:11 PM, "Black, David" <david.black@emc.com> wrote:

>Yiu,
>
>Thank you for your responses - most of them look fine, and in
>particular anything that I don't comment on here is acceptable to me.
>
>> [YL] In 2.2, we will add:
>> 
>> "Note that reassembly at Tunnel Exit-Point is resource
>> 	intensive. A large number of B4 may terminate on the same AFTR. If
>>many B4
>> 	fragment the packets, it would increase sufficient load to the AFTR for
>> 	reassembly. We recommend the operator should increase the MTU size of
>>the IPv6
>> 	network between B4 and AFTR to avoid fragmentation."
>
>I would change "is" to "may be" in the first line.
>
>> >[5] Section 2.8 discusses IPv4 accounting at the AFTR, but notes that
>> >"the AFTR does not have detailed customer identity information."  Does
>> >that create a theft of service possibility?  If so, that possibility
>> >should be mentioned as a security consideration.  Also, Section 2.8
>> >ought to be expanded with a sentence or two explaining why the AFTR
>> >does not have that identity information, and in particular to explain
>> >whether and why it is unreasonable in some or all cases to expect
>> >that customer identity information be provided to the AFTR as part
>> >of provisioning each customer's softwire.
>> 
>> [YL] Good catch. Actually I believe AFTR "does" have both IPv4 and IPv6
>>to
>> identify the customer. I suggest we remove
>> 
>> "but it will potentially introduce some additional complexity because
>>    the AFTR does not have detailed customer identity information."
>
>That's definitely an easy way to address that issue, and it's fine with
>me.
>
>> >Section 2.3 on MTU Considerations could usefully mention MTU discovery
>> >techniques, as possibilities for customer IPv4 traffic to adapt to a
>> >smaller IPv4 MTU.  If this is done, it would be useful to mention
>> >RFC 4821 in addition to the mention of RFC 1191 in RFC 6333.
>> 
>> [YL] We would consider RFC 4821. However, the challenge is I don't have
>> information how many current OS support RFC 4821. Since DS-lite is a
>> transition technology, it would be unreasonable to ask the OS company to
>> implement RFC 4821 for DS-lite.
>
>That's ok - this was a nit.
>
>> >- Are one or both types of logging recommended?
>> 
>> [YL] We tempted to recommend source-specific log. However, some
>>regulators
>> require to use both and the regulations vary country from country, this
>>is
>> why we left it open and let the operators to decide.
>
>Please add a version of your explanation to the draft.
>
>> >In Section 2.7, I'm having a hard time understanding which traffic is
>> >intended to be subject to the Outgoing Policies and the Incoming
>>Policies.
>> >Expanding each of those two bullets to explain what traffic is subject
>> >to each class of policies would help.
>> 
>> [YL] Does this help?
>> 
>> Outgoing Policies apply to packets originating from B4 to IPv4 network.
>> Incoming Policies apply to packets originating from IPv4 network to B4.
>
>Yes, that's clearer, although the B4 is not the network endpoint for any
>of that traffic.  I suggest:
>
>Outgoing Policies apply to packets originating from behind the B4 with
>a destination on the IPv4 network.
>
>Incoming Policies apply to packets originating from the IPv4 network to
>a destination behind the B4.
>
>Thanks,
>--David
>
>
>> -----Original Message-----
>> From: Lee, Yiu [mailto:Yiu_Lee@cable.comcast.com]
>> Sent: Wednesday, October 17, 2012 8:46 PM
>> To: Black, David; roberta.maglione@telecomitalia.it;
>>carlw@mcsr-labs.org;
>> christian.jacquenet@orange.com; mohamed.boucadair@orange.com;
>>gen-art@ietf.org
>> Cc: softwires@ietf.org; ietf@ietf.org; Ralph Droms
>> Subject: Re: Gen-ART review of draft-ietf-softwire-dslite-deployment-06
>> 
>> Hi David,
>> 
>> Thanks very much for review the draft. Comments inline.
>> 
>> Thanks,
>> Yiu
>> 
>> On 10/15/12 7:10 PM, "Black, David" <david.black@emc.com> wrote:
>> 
>> >I am the assigned Gen-ART reviewer for this draft. For background on
>> >Gen-ART, please see the FAQ at
>> ><http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>> >
>> >Please resolve these comments along with any other Last Call comments
>> >you may receive.
>> >
>> >Document: draft-ietf-softwire-dslite-deployment-06
>> >Reviewer: David L. Black
>> >Review Date: October 15, 2012
>> >IETF LC End Date: October 16, 2012
>> >IESG Telechat Date: October 25, 2012
>> >
>> >Summary:
>> >
>> >This draft is on the right track but has open issues, described in the
>> >review.
>> >
>> >This is a generally well-written draft that expands considerably on
>>the brief
>> >deployment considerations for DS-Lite in Appendix A of RFC 6333.  The
>>draft
>> >is clear and reasonably well-written, and a significant improvement on
>>that
>> >RFC 6333 Appendix, although an understanding of RFC 6333 is necessary
>>to
>> >understand this draft, which seems completely reasonable.
>> >
>> >The B4 and AFTR acronyms are clever - kudos to whomever came up with
>> >those.
>> >
>> >I found five open issues, all of which are minor.
>> >
>> >Minor Issues:
>> >
>> >[1] Ironically, the first issue is that something should be said about
>> >the relationship of this draft to Appendix A of RFC 6333.  It probably
>> >suffices to say that this draft expands on the material in that
>>Appendix,
>> >as I see no need to specify that this draft updates RFC 6333 solely to
>> >change non-normative material in an Appendix.
>> 
>> [YL] In "Overview", we will add:
>> 
>> "This document expands Appendix A of RFC6333 and discusses various
>> DS-Lite deployment considerations for operators."
>> 
>> >
>> >[2] The MTU increase technique in Section 2.2 is a "may", which is
>> >consistent with Section 5.3 of RFC 6333.  OTOH, Section 2.2 of this
>> >draft should also discuss the AFTR resource exhaustion concern that
>> >described in Section 6.3 of RFC 6333, as that is a potential
>> >operational reason for an ISP to increase MTU size (e.g., if customer
>> >sourcing of large IPv4 packets is not sufficiently rare).
>> 
>> [YL] In 2.2, we will add:
>> 
>> "Note that reassembly at Tunnel Exit-Point is resource
>> 	intensive. A large number of B4 may terminate on the same AFTR. If
>>many B4
>> 	fragment the packets, it would increase sufficient load to the AFTR for
>> 	reassembly. We recommend the operator should increase the MTU size of
>>the IPv6
>> 	network between B4 and AFTR to avoid fragmentation."
>> 
>> >
>> >[3] Section 2.7 refers to "the AFTR's internal interface".  There may
>>be
>> >two internal interfaces, the physical IPv6 interface (outer header) and
>> >the tunnel's IPv4 interface (inner header).  The text should be
>>clarified
>> >to indicate which interface is involved - it appears that the AFTR's
>> >physical IPv6 interface is intended in this section.
>> 
>> [YL] We replace "internal" to "IPv6"
>> 
>> >
>> >[4] Section 2.7 cites RFC 6333 for use of DHCPv6 with DS-Lite.  RFC
>>6334
>> >should be cited - either in addition to or instead of RFC 6333.
>> 
>> [YL] Fixed
>> 
>> >
>> >[5] Section 2.8 discusses IPv4 accounting at the AFTR, but notes that
>> >"the AFTR does not have detailed customer identity information."  Does
>> >that create a theft of service possibility?  If so, that possibility
>> >should be mentioned as a security consideration.  Also, Section 2.8
>> >ought to be expanded with a sentence or two explaining why the AFTR
>> >does not have that identity information, and in particular to explain
>> >whether and why it is unreasonable in some or all cases to expect
>> >that customer identity information be provided to the AFTR as part
>> >of provisioning each customer's softwire.
>> 
>> [YL] Good catch. Actually I believe AFTR "does" have both IPv4 and IPv6
>>to
>> identify the customer. I suggest we remove
>> 
>> "but it will potentially introduce some additional complexity because
>>    the AFTR does not have detailed customer identity information."
>> 
>> >
>> >Nits:
>> >
>> >Section 2.3 on MTU Considerations could usefully mention MTU discovery
>> >techniques, as possibilities for customer IPv4 traffic to adapt to a
>> >smaller IPv4 MTU.  If this is done, it would be useful to mention
>> >RFC 4821 in addition to the mention of RFC 1191 in RFC 6333.
>> 
>> [YL] We would consider RFC 4821. However, the challenge is I don't have
>> information how many current OS support RFC 4821. Since DS-lite is a
>> transition technology, it would be unreasonable to ask the OS company to
>> implement RFC 4821 for DS-lite.
>> 
>> >
>> >Section 2.4 should define "lawful intercept".  It would be helpful to
>> >cite a reference for this concept if something appropriate can be
>>found.
>> 
>> [YL] We will find whether there is any reference to this concept. If we
>> can't find any, we would add an explanation in the draft.
>> 
>> >
>> >Section 2.5:
>> >- Are one or both types of logging recommended?
>> 
>> [YL] We tempted to recommend source-specific log. However, some
>>regulators
>> require to use both and the regulations vary country from country, this
>>is
>> why we left it open and let the operators to decide.
>> 
>> >- Last paragraph on p.4, "timestamped log" is not a good verb phrase.
>> >	"maintain a timestamped log of" would be a better replacement.
>> 
>> [YL] Fixed
>> 
>> >- Last paragraph in section, where is the batch file sent?
>> 
>> [YL] We will add:
>> 
>> "The files may be compressed before transferring to a repository server
>> 	to better utilize bandwidth and storage."
>> 
>> 
>> >
>> >In Section 2.7, I'm having a hard time understanding which traffic is
>> >intended to be subject to the Outgoing Policies and the Incoming
>>Policies.
>> >Expanding each of those two bullets to explain what traffic is subject
>> >to each class of policies would help.
>> 
>> [YL] Does this help?
>> 
>> Outgoing Policies apply to packets originating from B4 to IPv4 network.
>> Incoming Policies apply to packets originating from IPv4 network to B4.
>> 
>> 
>> 
>> >
>> >Section 3.2.2.2 uses 192.0.0.2/32 as an example IP address for the
>> >B4.  That section should also cross-reference Section 5.7 on RFC 6333
>> >on IP address assignment to B4s, as other IP addresses may be used.
>> 
>> [YL] Added the cite.
>> 
>> >
>> >idnits 2.12.13 found a tiny nit - draft-ietf-pcp-base is now at
>> >version 28.
>> 
>> [YL] Fixed.
>> 
>> >
>> >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
>> >----------------------------------------------------
>> >
>> >

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

MIIVmQYJKoZIhvcNAQcCoIIVijCCFYYCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
EzEwggU0MIIEHKADAgECAhEAzuhISIgzOwSitfbc2LN4WDANBgkqhkiG9w0BAQUFADCBkzEL
MAkGA1UEBhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2Fs
Zm9yZDEaMBgGA1UEChMRQ09NT0RPIENBIExpbWl0ZWQxOTA3BgNVBAMTMENPTU9ETyBDbGll
bnQgQXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTAeFw0xMjA4MjgwMDAwMDBa
Fw0xMzA4MjgyMzU5NTlaMCoxKDAmBgkqhkiG9w0BCQEWGXlpdV9sZWVAY2FibGUuY29tY2Fz
dC5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCscOeu5/EoYRdja1jb6L4x
o0TIevelc17NsPuRHfr2z3BGUMbfsJY1p0uXO9+inBQoBXwb07ac3SbOjA/6Ef3NlMPItWdT
RGeFL6e/sMju9RgVyJURFnFgp7tc2tffnPOupnKZeeRehXeEFjun6+GC6teb1kSMu+WMMaCa
D7/XSK+Q+F0Udc2Av0/gUCkGfTDpNnYwutfctEMRnle6EYUqmJMN4C0crEfovmYdMFFgJLKs
Wa5Cdc+naFoIqzW8AcZB6+1XUDTzFbgjqgUbFFZFPzVZqNxLDFNy4tn8VlRSp2jBhgwQHtk1
ZA+spFENaeUuebp4tczj0IHG683FhhWjAgMBAAGjggHpMIIB5TAfBgNVHSMEGDAWgBR6E04A
dFvGeGNkJ8Ev4qBbvHnFezAdBgNVHQ4EFgQUz03csl7CmjwQY+spX9VWeGb5sVQwDgYDVR0P
AQH/BAQDAgWgMAwGA1UdEwEB/wQCMAAwIAYDVR0lBBkwFwYIKwYBBQUHAwQGCysGAQQBsjEB
AwUCMBEGCWCGSAGG+EIBAQQEAwIFIDBGBgNVHSAEPzA9MDsGDCsGAQQBsjEBAgEBATArMCkG
CCsGAQUFBwIBFh1odHRwczovL3NlY3VyZS5jb21vZG8ubmV0L0NQUzBXBgNVHR8EUDBOMEyg
SqBIhkZodHRwOi8vY3JsLmNvbW9kb2NhLmNvbS9DT01PRE9DbGllbnRBdXRoZW50aWNhdGlv
bmFuZFNlY3VyZUVtYWlsQ0EuY3JsMIGIBggrBgEFBQcBAQR8MHowUgYIKwYBBQUHMAKGRmh0
dHA6Ly9jcnQuY29tb2RvY2EuY29tL0NPTU9ET0NsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2Vj
dXJlRW1haWxDQS5jcnQwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLmNvbW9kb2NhLmNvbTAk
BgNVHREEHTAbgRl5aXVfbGVlQGNhYmxlLmNvbWNhc3QuY29tMA0GCSqGSIb3DQEBBQUAA4IB
AQBG7LORtWcmzDlw0N/D5AwfsSLe93essAqKFhJ+nt7SmMVBsxGzFnSsZGQHMYQ4UXtiVq9A
NjtPk00F3DC3QGxe4mxdwF9LzeYHpHMpCHTzNyilSimKZolLNBO+MO/U0u79rdF2W+dOAwkB
dzroWBxK+yMhijJn2DCE/1pgxqBz+c9zbAtJYPVpgbeGNvvfIp6CA/JYsupQNqPX49a4MdJ3
L9yXLTiegSE8uPUlCB3sHZclQOXAttuMewpcKDoIC4wZgERKQqRH61PQO100GLKUO+VrTq+f
xNkjOAqA+dih6QO5Djbv3qcMTCcAChJQYK8BS7jved8XgEVa0Ihz7oWKMIIFGjCCBAKgAwIB
AgIQbRnqpxlPajMi5iIyeqpx3jANBgkqhkiG9w0BAQUFADCBrjELMAkGA1UEBhMCVVMxCzAJ
BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJU
UlVTVCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNV
BAMTLVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbDAeFw0x
MTA0MjgwMDAwMDBaFw0yMDA1MzAxMDQ4MzhaMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMS
R3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8g
Q0EgTGltaXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQg
U2VjdXJlIEVtYWlsIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAkoSEW0tX
mNReL4uk4UDIo1NYX2Zl8TJO958yfVXQeExVt0KU4PkncQfFxmmkuTLE8UAakMwnVmJ/F7Vx
aa7lIBvky2NeYMqiQfZq4aP/uN8fSG1lQ4wqLitjOHffsReswtqCAtbUMmrUZ28gE49cNfrl
VICv2HEKHTcKAlBTbJUdqRAUtJmVWRIx/wmi0kzcUtve4kABW0ho3cVKtODtJB86r3FfB+Os
vxQ7sCVxaD30D9YXWEYVgTxoi4uDD216IVfmNLDbMn7jSuGlUnJkJpFOpZIP/+CxYP0ab2hR
mWONGoulzEKbm30iY9OpoPzOnpDfRBn0XFs1uhbzp5v/wQIDAQABo4IBSzCCAUcwHwYDVR0j
BBgwFoAUiYJnfcSdJnAAS7RQSHzePa4Ebn0wHQYDVR0OBBYEFHoTTgB0W8Z4Y2QnwS/ioFu8
ecV7MA4GA1UdDwEB/wQEAwIBBjASBgNVHRMBAf8ECDAGAQH/AgEAMBEGA1UdIAQKMAgwBgYE
VR0gADBYBgNVHR8EUTBPME2gS6BJhkdodHRwOi8vY3JsLnVzZXJ0cnVzdC5jb20vVVROLVVT
RVJGaXJzdC1DbGllbnRBdXRoZW50aWNhdGlvbmFuZEVtYWlsLmNybDB0BggrBgEFBQcBAQRo
MGYwPQYIKwYBBQUHMAKGMWh0dHA6Ly9jcnQudXNlcnRydXN0LmNvbS9VVE5BZGRUcnVzdENs
aWVudF9DQS5jcnQwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVzZXJ0cnVzdC5jb20wDQYJ
KoZIhvcNAQEFBQADggEBAIXWvnhXVW0zf0RS/kLVBqgBA4CK+w2y/Uq/9q9BSfUbWsXSrRtz
bj7pJnzmTJjBMCjfy/tCPKElPgp11tA9OYZm0aGbtU2bb68obB2v5ep0WqjascDxdXovnrqT
ecr+4pEeVnSy+I3T4ENyG+2P/WA5IEf7i686ZUg8mD2lJb+972DgSeUWyOs/Q4Pw4O4NwdPN
M1+b0L1garM7/vrUyTo8H+2b/5tJM75CKTmD7jNpLoKdRU2oadqAGx490hpdfEeZpZsIbRKZ
htZdVwcbpzC+S0lEuJB+ytF5OOu0M/qgOl0mWJ5hVRi0IdWZ1eBDQEIwvuql55TSsP7zdfl/
bucwggSdMIIDhaADAgECAhA0PekrrCc0/4/LNJT7zHBUMA0GCSqGSIb3DQEBBQUAMG8xCzAJ
BgNVBAYTAlNFMRQwEgYDVQQKEwtBZGRUcnVzdCBBQjEmMCQGA1UECxMdQWRkVHJ1c3QgRXh0
ZXJuYWwgVFRQIE5ldHdvcmsxIjAgBgNVBAMTGUFkZFRydXN0IEV4dGVybmFsIENBIFJvb3Qw
HhcNMDUwNjA3MDgwOTEwWhcNMjAwNTMwMTA0ODM4WjCBrjELMAkGA1UEBhMCVVMxCzAJBgNV
BAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT
VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMT
LVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbDCCASIwDQYJ
KoZIhvcNAQEBBQADggEPADCCAQoCggEBALI5haTyfatBO2JGN67NwWB1vDll+UoaR6K5zEjM
apjVTTUZuaRC5c5J4oovHnzSMQfHTrSDZJ0uKdWiZMSFvYVRNXmkTmiQexx6pJKoF/KYFfKT
zMmkMpW7DE8wvZigC4vlbhuiRvp4vKJvq1lepS/Pytptqi/rrKGzaqq3Lmc1i3nhHmmI4uZG
zaCl6r4LznY6eg6b6vzaJ1s9cx8i5khhxkzzabGoLhu21DEgLLyCio6kDqXXiUP8FlqvHXHX
EVnauocNr/rz4cLwpMVnjNbWVDreCqS6A3ezZcj9HtN0YqoYymiTHqGFfvVHZcv4TVcodNI0
/zC27vZiMBSMLOsCAwEAAaOB9DCB8TAfBgNVHSMEGDAWgBStvZh6NLQm9/rEJlTvA73gJMtU
GjAdBgNVHQ4EFgQUiYJnfcSdJnAAS7RQSHzePa4Ebn0wDgYDVR0PAQH/BAQDAgEGMA8GA1Ud
EwEB/wQFMAMBAf8wEQYDVR0gBAowCDAGBgRVHSAAMEQGA1UdHwQ9MDswOaA3oDWGM2h0dHA6
Ly9jcmwudXNlcnRydXN0LmNvbS9BZGRUcnVzdEV4dGVybmFsQ0FSb290LmNybDA1BggrBgEF
BQcBAQQpMCcwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVzZXJ0cnVzdC5jb20wDQYJKoZI
hvcNAQEFBQADggEBAAG8nONjKLDzMQHC33vdYqABnSMxD5ySc1NR6h9M+tafxMovZ354Mw90
FrmRh5H1iib6ZHAA2B75CwRiUIeTgdTa9SPbNLuFVrRwNG54gzcehRzFERWSX4cXvaxq/fHC
0cyJX7F88D5R8jXzfOxgmGs6K+Dv37N9huu1G/Vb7KJ8mBPXAFC50S1z3gN4dOEFhTFey5q5
nZTGuZQ3dXLcRPtn6PD6JR5Sp9ol6UfgoMc8oE6xCjb7d0if75eK+7T+45QUqIO8XC0/0mBx
YO7CcYIM6Yg249ogtKOgbKqWS7iAjnXKSQf2OxS639wF2Z/b4LLmTaB4JufnLW5/X8YeiBUw
ggQ2MIIDHqADAgECAgEBMA0GCSqGSIb3DQEBBQUAMG8xCzAJBgNVBAYTAlNFMRQwEgYDVQQK
EwtBZGRUcnVzdCBBQjEmMCQGA1UECxMdQWRkVHJ1c3QgRXh0ZXJuYWwgVFRQIE5ldHdvcmsx
IjAgBgNVBAMTGUFkZFRydXN0IEV4dGVybmFsIENBIFJvb3QwHhcNMDAwNTMwMTA0ODM4WhcN
MjAwNTMwMTA0ODM4WjBvMQswCQYDVQQGEwJTRTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAk
BgNVBAsTHUFkZFRydXN0IEV4dGVybmFsIFRUUCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVz
dCBFeHRlcm5hbCBDQSBSb290MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAt/ca
M+byAAQtOeBOW+0fvGwPzbX6I7bO3psRM5ekKUx9k5+9SryT7QMa44/P5W1QWtaXKZRagLBJ
etsulf24yr83OC0ePpFBrXBWx/BPP+gynnTKyJBU6cZfD3idmkA8Dqxhql4Uj56HoWpQ3Nea
Tq8Fs6ZxlJxxs1BgCscTnTgHhgKo6ahpJhiQq0ywTyOrOk+E2N/On+Fpb7vXQtdrROTHre5t
QV9yWnEIN7N5ZaRZoJQ39wAvDcKSctrQOHLbFKhFxF0qfbe01sTurM0TRLfJK91DACX6Yblp
algjEbenM49WdVn1zSnXRrcKK2W200JvFbK4e/vv6V1T1TRaJwIDAQABo4HcMIHZMB0GA1Ud
DgQWBBStvZh6NLQm9/rEJlTvA73gJMtUGjALBgNVHQ8EBAMCAQYwDwYDVR0TAQH/BAUwAwEB
/zCBmQYDVR0jBIGRMIGOgBStvZh6NLQm9/rEJlTvA73gJMtUGqFzpHEwbzELMAkGA1UEBhMC
U0UxFDASBgNVBAoTC0FkZFRydXN0IEFCMSYwJAYDVQQLEx1BZGRUcnVzdCBFeHRlcm5hbCBU
VFAgTmV0d29yazEiMCAGA1UEAxMZQWRkVHJ1c3QgRXh0ZXJuYWwgQ0EgUm9vdIIBATANBgkq
hkiG9w0BAQUFAAOCAQEAsJvghSXC1iPiD5YGkp1BmJzZhHmB2R5bFAcjNmWPsNh3u6xBbEdg
g1Gw+TI95/z2JhPHgBalv1r8h894eYkhmuJMBwqGNbzy3lHE0pa33H5O7nD9HDnrDAJRFC2O
vRbgwd9Gdeckrez0QrSFk3AQZ7qdBjVKGNMresxRQqF6Y9Hmu6HFK8I2vhMN5r1jfnl7pwkN
QKtq3Y+Kw/b2jBpCBVHURfWfp2IhaBUgQzyZ53y9JNipkRdziD9WGzE4GLRxD5rNyA6eji4b
4YyYg8sfMfFETMYEc0l2YA/H+L0XgGsu6cxMDlqaeQ8gCi7VnmMmHlWSlNiCF1p70LzHj06G
BDGCAjAwggIsAgEBMIGpMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5j
aGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDE5
MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWls
IENBAhEAzuhISIgzOwSitfbc2LN4WDAJBgUrDgMCGgUAoF0wIwYJKoZIhvcNAQkEMRYEFGkn
nJBZtnpog7FZj5U6Qx+BLJFVMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcN
AQkFMQ8XDTEyMTAxODEyMjkwN1owDQYJKoZIhvcNAQEBBQAEggEAhqU5Lp5+wPE+aK5lPOnX
UW8gQG+BDt7ck9adN8TNr6ZBxLONPEDZDtYes5TuMyLnXaPqPH/fx0KuhsQZz/iNUiuRiAv2
ijEn9Q74BRAftfmFwX5L71HJf3l/g04+GoTB8u5UM1IUVwiXhqExsgGsF7CNPN9g6aA9BBF9
he0ud9aEWFEEdlhhImS715fUmi2Tod5rzTT9+Es3kW1lHCliEsfzsmGbYdq18GFje7lDLlGB
z67zY/j3DzXInR5dnXWr2fdjkgOrOsj/zhckt6k9spUlI1e4SSO4UoaP5NQTRXYMz/A7R0RZ
PdFLnT1aKHCcmFQ7uL6/gPfjUyFNZTFrbw==

--B_3433393748_19694--

From john-ietf@jck.com  Thu Oct 18 06:46:02 2012
Return-Path: <john-ietf@jck.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 6076221F8779; Thu, 18 Oct 2012 06:46:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.529
X-Spam-Level: 
X-Spam-Status: No, score=-102.529 tagged_above=-999 required=5 tests=[AWL=0.070, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BYU-HmWi9H6N; Thu, 18 Oct 2012 06:46:01 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 8275D21F8740; Thu, 18 Oct 2012 06:46:01 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TOqPt-0000iR-HU; Thu, 18 Oct 2012 09:45:41 -0400
Date: Thu, 18 Oct 2012 09:45:35 -0400
From: John C Klensin <john-ietf@jck.com>
To: Barry Leiba <barryleiba@computer.org>, dcrocker@bbiw.net
Message-ID: <E73A2748BBE3FA6E1EE3A2C3@JcK-HP8200.jck.com>
In-Reply-To: <CALaySJKD+JbkOuZsC7wQtNNLHBP-4a_=DNfQ0XkQWoCq78-JGg@mail.gmail.com>
References: <010301cdac4d$cfa70060$6ef50120$@gmail.com> <01OLIW8VNVCU00008S@mauve.mrochek.com> <507EF95D.5090007@dcrocker.net> <01OLIXV2SU4O00008S@mauve.mrochek.com> <5B0F81787945877A5CC3794B@JcK-HP8200.jck.com> <01OLJ38YAL9600008S@mauve.mrochek.com> <507F3CEA.2010306@dcrocker.net> <01OLJ9JAK8SQ00008S@mauve.mrochek.com> <507F5249.2090507@dcrocker.net> <CALaySJKD+JbkOuZsC7wQtNNLHBP-4a_=DNfQ0XkQWoCq78-JGg@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: Ned Freed <ned.freed@mrochek.com>, draft-leiba-5322upd-from-group.all@tools.ietf.org, ned+ietf@mauve.mrochek.com, gen-art@ietf.org, johnl@taugh.com, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-leiba-5322upd-from-group-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, 18 Oct 2012 13:46:03 -0000

--On Thursday, October 18, 2012 07:13 -0400 Barry Leiba
<barryleiba@computer.org> wrote:

> On Wed, Oct 17, 2012 at 8:50 PM, Dave Crocker
> <dhc@dcrocker.net> wrote:
>>> I see no way to explain the narrow EAI use case in this
>>> context without either dragging in a whole bunch of EAI that
>>> has no business being here or leaving various things
>>> dangling.
>> 
>> ack. mumble.
>> 
>> So I'll suggest a bit of an amalgam, including a cross
>> reference of the type I prefer to avoid:
>> 
>>    1. State that this removes a restriction that was never
>>    essential.
>> 
>>    2. State that the timing of this removal is to accomodate
>>    EAI and for its use of the now-available features, see
>> [RFCxxxx].
> 
> 
> On Thu, Oct 18, 2012 at 6:28 AM, John Levine <johnl@taugh.com>
> wrote (with a large part of this distribution list removed):
>>> So, is it better to put in a sentence about representing
>>> non-ASCII text in the group name without including a
>>> replyable address?
>> 
>> The main motivation is to provide a syntax for a
>> non-replyable address in From: and Sender: headers for cases
>> where that is appropriate.  See the EAI downgrade documents
>> for a concrete example.
>> 
>> A secondary motivation is to remove an arcane restriction
>> that has not turned out to be useful in practice.
> 
> Dave and John (Levine) are both suggesting an informative
> reference from this document to some piece of the EAI
> documents (which I guess should be one or both of
> draft-ietf-eai-5738bis, Section 7, and
> draft-ietf-eai-popimap-downgrade, Section 3.2.1).
> 
> Ned and John (Klensin), can you live with that (I know it's
> not your preference). 

As I said earlier, I can live with almost anything if it is
correct and allows us to move forward.  I am, however, getting
more concerned about the consequences to the virtual 5322bis and
its future instantiation if we go down these paths.  I would
really not like to be the relevant AD (or Pete-bis) trying to
defend leaving the explanation and reference out of 5322bis
given that they were important enough to include in this
document and, if the explanation and reference go into 5322bis,
why a large series of other references and explanations should
not be included.  I'd be a tad happier if this explanatory stuff
when into an appendix rather than the text.  

Using a different part of the EAI work as an example, the idea
that it would take little work to get from 5322 to 5322bis goes
completely out the window if the explanation of the syntax of
header fields has to say, effectively, "restricted to ASCII
except when they are not" followed by an explanation and
references.

If you do decide to do this, I slightly prefer Dave's
formulation to John(Levine)'s and prefer my earlier formulation
to either.  Borrowing a bit from Ned, 

* this restriction is inappropriate given contemporary
	practice, 
* its incorporation as a syntax rule rather than an
	applicability restriction was a matter of convenience
	that turned out to be a mistake, so
* we are converting it to an applicability
	restriction with the main motivation being to permit an
	identifiable (or named) but non-replyable
	backward-pointing address where that is necessary and
	the special considerations associated with "<>" don't
	apply.**
 and, if necessary,
* here is a pointer to the application that motivated us
	to move forward at this particular time.

As evidence of how silly the syntax restriction is, 5322 syntax
allows a group, non-replyable, address in the one field whose
sole purpose is to provide an address to which one is supposed
to reply ("Reply-to:" of course), creating what might be a high
in silly states.

** Yeah, I know that 5322 doesn't permit "<>" except in
	a Return-path, but I've seen that restriction
	un-enforced many times too.  We could have decided to
	make "From:" and "Sender:" use "mailbox[-list] / path"
	instead of allowing groups, but the group preserves
	somewhat more information -- information that 
   popimap-downgrade very much needs.  I don't think 
   that explanation belongs in 5322 either.

>  All: which (or both) should the reference be to?

To the extent to which an explanation or examples are needed, it
has to be popimap-downgrade.  But that document is not
particularly well-suited for the purpose, it doesn't contain an
explanation of why empty groups were  chosen in preference to
"<>" and more Downgraded-* headers (and shouldn't unless we are
going to start documenting every discarded design alternative),
and we still hope that it turns out to be a moderately
short-term transition mechanism that can gradually fade away
into a historical footnote.

Mumble.
    john


From dcrocker@bbiw.net  Thu Oct 18 06:51:00 2012
Return-Path: <dcrocker@bbiw.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 68F5721F875A; Thu, 18 Oct 2012 06:51:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.413
X-Spam-Level: 
X-Spam-Status: No, score=-6.413 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NDBn-7Tg62ub; Thu, 18 Oct 2012 06:50:59 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 79E7721F8758; Thu, 18 Oct 2012 06:50:59 -0700 (PDT)
Received: from [192.168.1.6] (adsl-67-127-59-48.dsl.pltn13.pacbell.net [67.127.59.48]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q9IDosbT008905 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 18 Oct 2012 06:50:55 -0700
Message-ID: <5080093D.2050406@bbiw.net>
Date: Thu, 18 Oct 2012 06:50:53 -0700
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121005 Thunderbird/16.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
References: <010301cdac4d$cfa70060$6ef50120$@gmail.com> <01OLIW8VNVCU00008S@mauve.mrochek.com> <507EF95D.5090007@dcrocker.net> <01OLIXV2SU4O00008S@mauve.mrochek.com> <5B0F81787945877A5CC3794B@JcK-HP8200.jck.com> <01OLJ38YAL9600008S@mauve.mrochek.com> <507F3CEA.2010306@dcrocker.net> <01OLJ9JAK8SQ00008S@mauve.mrochek.com> <507F5249.2090507@dcrocker.net> <CALaySJKD+JbkOuZsC7wQtNNLHBP-4a_=DNfQ0XkQWoCq78-JGg@mail.gmail.com> <E73A2748BBE3FA6E1EE3A2C3@JcK-HP8200.jck.com>
In-Reply-To: <E73A2748BBE3FA6E1EE3A2C3@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 18 Oct 2012 06:50:55 -0700 (PDT)
Cc: Ned Freed <ned.freed@mrochek.com>, draft-leiba-5322upd-from-group.all@tools.ietf.org, ned+ietf@mauve.mrochek.com, gen-art@ietf.org, johnl@taugh.com, Barry Leiba <barryleiba@computer.org>, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-leiba-5322upd-from-group-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, 18 Oct 2012 13:51:00 -0000

On 10/18/2012 6:45 AM, John C Klensin wrote:
> As I said earlier, I can live with almost anything if it is
> correct and allows us to move forward.  I am, however, getting
> more concerned about the consequences to the virtual 5322bis and
> its future instantiation if we go down these paths.  I would
> really not like to be the relevant AD (or Pete-bis) trying to
> defend leaving the explanation and reference out of 5322bis
> given that they were important enough to include in this
> document and, if the explanation and reference go into 5322bis,
> why a large series of other references and explanations should
> not be included.  I'd be a tad happier if this explanatory stuff
> when into an appendix rather than the text.


The job of the current draft is to be sufficient to its purpose.  Its 
purpose is to augment a base document with a specific revision.

An update segment document does not typically have the purpose of 
including extensive annotations for possible later use, attempting to 
anticipate or hypothesize later editing efforts, to revise the base 
document.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From david.black@emc.com  Thu Oct 18 08:11:23 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 5728A21F8830 for <gen-art@ietfa.amsl.com>; Thu, 18 Oct 2012 08:11:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.608
X-Spam-Level: 
X-Spam-Status: No, score=-102.608 tagged_above=-999 required=5 tests=[AWL=-0.009, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z+IGqnmQGj2F for <gen-art@ietfa.amsl.com>; Thu, 18 Oct 2012 08:11:20 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 7968521F87FD for <gen-art@ietf.org>; Thu, 18 Oct 2012 08:11:20 -0700 (PDT)
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 q9IFBCbQ001444 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 18 Oct 2012 11:11:14 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd04.lss.emc.com [10.254.222.226]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Thu, 18 Oct 2012 11:10:58 -0400
Received: from mxhub07.corp.emc.com (mxhub07.corp.emc.com [128.222.70.204]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q9IFAvpn019241; Thu, 18 Oct 2012 11:10:57 -0400
Received: from mx15a.corp.emc.com ([169.254.1.83]) by mxhub07.corp.emc.com ([128.222.70.204]) with mapi; Thu, 18 Oct 2012 11:10:57 -0400
From: "Black, David" <david.black@emc.com>
To: Maglione Roberta <roberta.maglione@telecomitalia.it>, "Lee, Yiu" <Yiu_Lee@cable.comcast.com>, "'draft-ietf-softwire-dslite-deployment@tools.ietf.org'" <draft-ietf-softwire-dslite-deployment@tools.ietf.org>
Date: Thu, 18 Oct 2012 11:10:56 -0400
Thread-Topic: Gen-ART review of draft-ietf-softwire-dslite-deployment-06
Thread-Index: AQHNrMoAT7CfnR/9yUSA1hDdxxOKmpe+Pf7ggABprICAAIOr4A==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7120DFAF49C@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE7120DFAEF29@MX15A.corp.emc.com> <E3FAB1F4F41F3A45B287E8D9C53522FD37A7EC79@PACDCEXMB05.cable.comcast.com> <8D3D17ACE214DC429325B2B98F3AE7120DFAF3B9@MX15A.corp.emc.com> <282BBE8A501E1F4DA9C775F964BB21FE519702F25A@GRFMBX704BA020.griffon.local>
In-Reply-To: <282BBE8A501E1F4DA9C775F964BB21FE519702F25A@GRFMBX704BA020.griffon.local>
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: "gen-art@ietf.org" <gen-art@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>, "softwire-chairs@tools.ietf.org" <softwire-chairs@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-softwire-dslite-deployment-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, 18 Oct 2012 15:11:23 -0000

Hello Roberta,

In that case, more text is needed to explain in Section 2.8, and
the related theft of service concern also needs to be discussed in
that section and/or the Security Considerations section.

Thanks,
--David

> -----Original Message-----
> From: Maglione Roberta [mailto:roberta.maglione@telecomitalia.it]
> Sent: Thursday, October 18, 2012 3:18 AM
> To: Black, David; Lee, Yiu; 'draft-ietf-softwire-dslite-
> deployment@tools.ietf.org'
> Cc: Ralph Droms; gen-art@ietf.org; softwire-chairs@tools.ietf.org
> Subject: RE: Gen-ART review of draft-ietf-softwire-dslite-deployment-06
>=20
> Hello Yiu and David,
> regarding point 5:
>=20
> > [YL] Good catch. Actually I believe AFTR "does" have both IPv4 and
> > IPv6 to identify the customer. I suggest we remove
> >
> > "but it will potentially introduce some additional complexity because
> >    the AFTR does not have detailed customer identity information."
>=20
> The point related to the accounting is different: what I meant here with
> accounting is RADIUS based accounting, commonly used in Broadband network=
s.
>=20
> Today RADIUS accounting is done at the BNG level, the problem with the
> introduction of the AFTR is that the AFTR does not interact with AAA/RADI=
US
> Server for the initial authentication/authorization/accounting phase beca=
use
> the authentication/authorization/accounting process happens between BNG a=
nd
> RADIUS Server when the session comes up.
> The ATFR is not able to perform RADIUS accounting because as it does not
> interact with the RADIUS Server it does not have " detailed customer iden=
tity
> information" for example it does know the accounting session ID associate=
d to
> that session, that's why it cannot do detailed accounting for each single
> subscriber even if the ATFR can still correlated IPv6 and IPv4 traffic
> belonging to the same user.
>=20
> This is an important operational issue, I would suggest to keep this conc=
ept.
> If you think is needed I can add some lines of text in order to clarify t=
his
> point.
>=20
> Thanks
> Regards,
> Roberta
>=20
> -----Original Message-----
> From: Black, David [mailto:david.black@emc.com]
> Sent: Thursday, October 18, 2012 3:12 AM
> To: Lee, Yiu; Maglione Roberta; carlw@mcsr-labs.org;
> christian.jacquenet@orange.com; mohamed.boucadair@orange.com; gen-art@iet=
f.org
> Cc: softwires@ietf.org; ietf@ietf.org; Ralph Droms; Black, David
> Subject: RE: Gen-ART review of draft-ietf-softwire-dslite-deployment-06
>=20
> Yiu,
>=20
> Thank you for your responses - most of them look fine, and in
> particular anything that I don't comment on here is acceptable to me.
>=20
> > [YL] In 2.2, we will add:
> >
> > "Note that reassembly at Tunnel Exit-Point is resource
> >       intensive. A large number of B4 may terminate on the same AFTR. I=
f
> many B4
> >       fragment the packets, it would increase sufficient load to the AF=
TR
> for
> >       reassembly. We recommend the operator should increase the MTU siz=
e of
> the IPv6
> >       network between B4 and AFTR to avoid fragmentation."
>=20
> I would change "is" to "may be" in the first line.
>=20
> > >[5] Section 2.8 discusses IPv4 accounting at the AFTR, but notes that
> > >"the AFTR does not have detailed customer identity information."  Does
> > >that create a theft of service possibility?  If so, that possibility
> > >should be mentioned as a security consideration.  Also, Section 2.8
> > >ought to be expanded with a sentence or two explaining why the AFTR
> > >does not have that identity information, and in particular to explain
> > >whether and why it is unreasonable in some or all cases to expect
> > >that customer identity information be provided to the AFTR as part
> > >of provisioning each customer's softwire.
> >
> > [YL] Good catch. Actually I believe AFTR "does" have both IPv4 and IPv6=
 to
> > identify the customer. I suggest we remove
> >
> > "but it will potentially introduce some additional complexity because
> >    the AFTR does not have detailed customer identity information."
>=20
> That's definitely an easy way to address that issue, and it's fine with m=
e.
>=20
> > >Section 2.3 on MTU Considerations could usefully mention MTU discovery
> > >techniques, as possibilities for customer IPv4 traffic to adapt to a
> > >smaller IPv4 MTU.  If this is done, it would be useful to mention
> > >RFC 4821 in addition to the mention of RFC 1191 in RFC 6333.
> >
> > [YL] We would consider RFC 4821. However, the challenge is I don't have
> > information how many current OS support RFC 4821. Since DS-lite is a
> > transition technology, it would be unreasonable to ask the OS company t=
o
> > implement RFC 4821 for DS-lite.
>=20
> That's ok - this was a nit.
>=20
> > >- Are one or both types of logging recommended?
> >
> > [YL] We tempted to recommend source-specific log. However, some regulat=
ors
> > require to use both and the regulations vary country from country, this=
 is
> > why we left it open and let the operators to decide.
>=20
> Please add a version of your explanation to the draft.
>=20
> > >In Section 2.7, I'm having a hard time understanding which traffic is
> > >intended to be subject to the Outgoing Policies and the Incoming Polic=
ies.
> > >Expanding each of those two bullets to explain what traffic is subject
> > >to each class of policies would help.
> >
> > [YL] Does this help?
> >
> > Outgoing Policies apply to packets originating from B4 to IPv4 network.
> > Incoming Policies apply to packets originating from IPv4 network to B4.
>=20
> Yes, that's clearer, although the B4 is not the network endpoint for any
> of that traffic.  I suggest:
>=20
> Outgoing Policies apply to packets originating from behind the B4 with
> a destination on the IPv4 network.
>=20
> Incoming Policies apply to packets originating from the IPv4 network to
> a destination behind the B4.
>=20
> Thanks,
> --David
>=20
>=20
> > -----Original Message-----
> > From: Lee, Yiu [mailto:Yiu_Lee@cable.comcast.com]
> > Sent: Wednesday, October 17, 2012 8:46 PM
> > To: Black, David; roberta.maglione@telecomitalia.it; carlw@mcsr-labs.or=
g;
> > christian.jacquenet@orange.com; mohamed.boucadair@orange.com; gen-
> art@ietf.org
> > Cc: softwires@ietf.org; ietf@ietf.org; Ralph Droms
> > Subject: Re: Gen-ART review of draft-ietf-softwire-dslite-deployment-06
> >
> > Hi David,
> >
> > Thanks very much for review the draft. Comments inline.
> >
> > Thanks,
> > Yiu
> >
> > On 10/15/12 7:10 PM, "Black, David" <david.black@emc.com> wrote:
> >
> > >I am the assigned Gen-ART reviewer for this draft. For background on
> > >Gen-ART, please see the FAQ at
> > ><http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> > >
> > >Please resolve these comments along with any other Last Call comments
> > >you may receive.
> > >
> > >Document: draft-ietf-softwire-dslite-deployment-06
> > >Reviewer: David L. Black
> > >Review Date: October 15, 2012
> > >IETF LC End Date: October 16, 2012
> > >IESG Telechat Date: October 25, 2012
> > >
> > >Summary:
> > >
> > >This draft is on the right track but has open issues, described in the
> > >review.
> > >
> > >This is a generally well-written draft that expands considerably on th=
e
> brief
> > >deployment considerations for DS-Lite in Appendix A of RFC 6333.  The =
draft
> > >is clear and reasonably well-written, and a significant improvement on=
 that
> > >RFC 6333 Appendix, although an understanding of RFC 6333 is necessary =
to
> > >understand this draft, which seems completely reasonable.
> > >
> > >The B4 and AFTR acronyms are clever - kudos to whomever came up with
> > >those.
> > >
> > >I found five open issues, all of which are minor.
> > >
> > >Minor Issues:
> > >
> > >[1] Ironically, the first issue is that something should be said about
> > >the relationship of this draft to Appendix A of RFC 6333.  It probably
> > >suffices to say that this draft expands on the material in that Append=
ix,
> > >as I see no need to specify that this draft updates RFC 6333 solely to
> > >change non-normative material in an Appendix.
> >
> > [YL] In "Overview", we will add:
> >
> > "This document expands Appendix A of RFC6333 and discusses various
> > DS-Lite deployment considerations for operators."
> >
> > >
> > >[2] The MTU increase technique in Section 2.2 is a "may", which is
> > >consistent with Section 5.3 of RFC 6333.  OTOH, Section 2.2 of this
> > >draft should also discuss the AFTR resource exhaustion concern that
> > >described in Section 6.3 of RFC 6333, as that is a potential
> > >operational reason for an ISP to increase MTU size (e.g., if customer
> > >sourcing of large IPv4 packets is not sufficiently rare).
> >
> > [YL] In 2.2, we will add:
> >
> > "Note that reassembly at Tunnel Exit-Point is resource
> >       intensive. A large number of B4 may terminate on the same AFTR. I=
f
> many B4
> >       fragment the packets, it would increase sufficient load to the AF=
TR
> for
> >       reassembly. We recommend the operator should increase the MTU siz=
e of
> the IPv6
> >       network between B4 and AFTR to avoid fragmentation."
> >
> > >
> > >[3] Section 2.7 refers to "the AFTR's internal interface".  There may =
be
> > >two internal interfaces, the physical IPv6 interface (outer header) an=
d
> > >the tunnel's IPv4 interface (inner header).  The text should be clarif=
ied
> > >to indicate which interface is involved - it appears that the AFTR's
> > >physical IPv6 interface is intended in this section.
> >
> > [YL] We replace "internal" to "IPv6"
> >
> > >
> > >[4] Section 2.7 cites RFC 6333 for use of DHCPv6 with DS-Lite.  RFC 63=
34
> > >should be cited - either in addition to or instead of RFC 6333.
> >
> > [YL] Fixed
> >
> > >
> > >[5] Section 2.8 discusses IPv4 accounting at the AFTR, but notes that
> > >"the AFTR does not have detailed customer identity information."  Does
> > >that create a theft of service possibility?  If so, that possibility
> > >should be mentioned as a security consideration.  Also, Section 2.8
> > >ought to be expanded with a sentence or two explaining why the AFTR
> > >does not have that identity information, and in particular to explain
> > >whether and why it is unreasonable in some or all cases to expect
> > >that customer identity information be provided to the AFTR as part
> > >of provisioning each customer's softwire.
> >
> > [YL] Good catch. Actually I believe AFTR "does" have both IPv4 and IPv6=
 to
> > identify the customer. I suggest we remove
> >
> > "but it will potentially introduce some additional complexity because
> >    the AFTR does not have detailed customer identity information."
> >
> > >
> > >Nits:
> > >
> > >Section 2.3 on MTU Considerations could usefully mention MTU discovery
> > >techniques, as possibilities for customer IPv4 traffic to adapt to a
> > >smaller IPv4 MTU.  If this is done, it would be useful to mention
> > >RFC 4821 in addition to the mention of RFC 1191 in RFC 6333.
> >
> > [YL] We would consider RFC 4821. However, the challenge is I don't have
> > information how many current OS support RFC 4821. Since DS-lite is a
> > transition technology, it would be unreasonable to ask the OS company t=
o
> > implement RFC 4821 for DS-lite.
> >
> > >
> > >Section 2.4 should define "lawful intercept".  It would be helpful to
> > >cite a reference for this concept if something appropriate can be foun=
d.
> >
> > [YL] We will find whether there is any reference to this concept. If we
> > can't find any, we would add an explanation in the draft.
> >
> > >
> > >Section 2.5:
> > >- Are one or both types of logging recommended?
> >
> > [YL] We tempted to recommend source-specific log. However, some regulat=
ors
> > require to use both and the regulations vary country from country, this=
 is
> > why we left it open and let the operators to decide.
> >
> > >- Last paragraph on p.4, "timestamped log" is not a good verb phrase.
> > >     "maintain a timestamped log of" would be a better replacement.
> >
> > [YL] Fixed
> >
> > >- Last paragraph in section, where is the batch file sent?
> >
> > [YL] We will add:
> >
> > "The files may be compressed before transferring to a repository server
> >       to better utilize bandwidth and storage."
> >
> >
> > >
> > >In Section 2.7, I'm having a hard time understanding which traffic is
> > >intended to be subject to the Outgoing Policies and the Incoming Polic=
ies.
> > >Expanding each of those two bullets to explain what traffic is subject
> > >to each class of policies would help.
> >
> > [YL] Does this help?
> >
> > Outgoing Policies apply to packets originating from B4 to IPv4 network.
> > Incoming Policies apply to packets originating from IPv4 network to B4.
> >
> >
> >
> > >
> > >Section 3.2.2.2 uses 192.0.0.2/32 as an example IP address for the
> > >B4.  That section should also cross-reference Section 5.7 on RFC 6333
> > >on IP address assignment to B4s, as other IP addresses may be used.
> >
> > [YL] Added the cite.
> >
> > >
> > >idnits 2.12.13 found a tiny nit - draft-ietf-pcp-base is now at
> > >version 28.
> >
> > [YL] Fixed.
> >
> > >
> > >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
> Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle
> persone indicate. La diffusione, copia o qualsiasi altra azione derivante
> dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualo=
ra
> abbiate ricevuto questo documento per errore siete cortesemente pregati d=
i
> darne immediata comunicazione al mittente e di provvedere alla sua
> distruzione, Grazie.
>=20
> This e-mail and any attachments is confidential and may contain privilege=
d
> information intended for the addressee(s) only. Dissemination, copying,
> printing or use by anybody else is unauthorised. If you are not the inten=
ded
> recipient, please delete this message and any attachments and advise the
> sender by return e-mail, Thanks.
>=20


From dcrocker@bbiw.net  Thu Oct 18 18:25:38 2012
Return-Path: <dcrocker@bbiw.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 AD79921F8528; Thu, 18 Oct 2012 18:25:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.475
X-Spam-Level: 
X-Spam-Status: No, score=-6.475 tagged_above=-999 required=5 tests=[AWL=0.124,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a78eHKqnYBvq; Thu, 18 Oct 2012 18:25:38 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0C99821F84FF; Thu, 18 Oct 2012 18:25:38 -0700 (PDT)
Received: from [192.168.1.6] (adsl-67-127-59-48.dsl.pltn13.pacbell.net [67.127.59.48]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q9J1Pap2031753 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 18 Oct 2012 18:25:37 -0700
Message-ID: <5080AC0E.8080001@bbiw.net>
Date: Thu, 18 Oct 2012 18:25:34 -0700
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Bill McQuillan <McQuilWP@pobox.com>
References: <010301cdac4d$cfa70060$6ef50120$@gmail.com> <01OLIW8VNVCU00008S@mauve.mrochek.com> <507EF95D.5090007@dcrocker.net> <01OLIXV2SU4O00008S@mauve.mrochek.com> <5B0F81787945877A5CC3794B@JcK-HP8200.jck.com> <01OLJ38YAL9600008S@mauve.mrochek.com> <507F3CEA.2010306@dcrocker.net> <01OLJ9JAK8SQ00008S@mauve.mrochek.com> <507F5249.2090507@dcrocker.net> <CALaySJKD+JbkOuZsC7wQtNNLHBP-4a_=DNfQ0XkQWoCq78-JGg@mail.gmail.com> <E73A2748BBE3FA6E1EE3A2C3@JcK-HP8200.jck.com> <1475027170.20121018175128@pobox.com>
In-Reply-To: <1475027170.20121018175128@pobox.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 18 Oct 2012 18:25:37 -0700 (PDT)
Cc: ned+ietf@mauve.mrochek.com, gen-art@ietf.org, johnl@taugh.com, IETF Discussion <ietf@ietf.org>, draft-leiba-5322upd-from-group.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-leiba-5322upd-from-group-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: Fri, 19 Oct 2012 01:25:38 -0000

> I have wondered about that limitation for at least 15 years. I
> have come up with possible explanations but without a shred of
> evidence from the RFCs.


FWIW,

The construct of "group" is pretty much an assertion of an aggregate 
identity.  That is, an identity beyond that of the listed addressees, 
deriving from their, ummmm... grouping.

The purpose of From: and Sender: is to assign bits of essential 
responsibility.

Unlike the current trend towards declaring personhood for corporations, 
the design motivation behind using the group construct was to restrict 
assignment of responsibilities to individuals, rather than aggregations 
of them.

All very abstract, I admit.  From the vantage point of some decades, 
even quaint.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From McQuilWP@pobox.com  Thu Oct 18 17:51:37 2012
Return-Path: <McQuilWP@pobox.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 2775221F8493; Thu, 18 Oct 2012 17:51:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2vBSNJSipSPN; Thu, 18 Oct 2012 17:51:33 -0700 (PDT)
Received: from smtp.pobox.com (b-pb-sasl-quonix.pobox.com [208.72.237.35]) by ietfa.amsl.com (Postfix) with ESMTP id 5063F21F849C; Thu, 18 Oct 2012 17:51:33 -0700 (PDT)
Received: from smtp.pobox.com (unknown [127.0.0.1]) by b-sasl-quonix.pobox.com (Postfix) with ESMTP id AD53881AB; Thu, 18 Oct 2012 20:51:31 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=date:from :message-id:to:cc:subject:in-reply-to:references:mime-version :content-type:content-transfer-encoding; s=sasl; bh=MgNqjWxq4ShP le4ZKFbqpRG15bA=; b=KbVMz4pVhqGhkUoowccZ+7wJ1l1D7URgT2KxO6Ur18OL 5nBTcVUPCo2NXZuTzqLWt7tgXgjG8yIezRQWKXyXTPjF8rmxpSt5hEzzWMrxIS7C eJ5iFq7NZHTE1E+umuWIwi6Bm/Ps14HKem0ny+fEkzkjnXu0LejNAEVISt2S1Oc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=date:from :message-id:to:cc:subject:in-reply-to:references:mime-version :content-type:content-transfer-encoding; q=dns; s=sasl; b=nSrnTq X9+4+U6PY6JzXnt0diRhsBuPuFVO2Nk5HJ+oJAmZCkDjJOiY2qV/A17A9ZqJ6c+L sRwogS0Ib0B1o5XAHJURz3mVNT+e10MWRgxN9w8eUXO7MsRIcvw3hXVinX2bMM4o RDLD7WGsOUMPN3xn6G7+9TVC/8JVPHQJeJN9U=
Received: from b-pb-sasl-quonix.pobox.com (unknown [127.0.0.1]) by b-sasl-quonix.pobox.com (Postfix) with ESMTP id 9A17D81AA; Thu, 18 Oct 2012 20:51:31 -0400 (EDT)
Received: from BQ07NB (unknown [68.107.15.47]) by b-sasl-quonix.pobox.com (Postfix) with ESMTPA id E691E81A9; Thu, 18 Oct 2012 20:51:29 -0400 (EDT)
Date: Thu, 18 Oct 2012 17:51:28 -0700
From: Bill McQuillan <McQuilWP@pobox.com>
X-Priority: 3 (Normal)
Message-ID: <1475027170.20121018175128@pobox.com>
To: IETF Discussion <ietf@ietf.org>
In-Reply-To: <E73A2748BBE3FA6E1EE3A2C3@JcK-HP8200.jck.com>
References: <010301cdac4d$cfa70060$6ef50120$@gmail.com> <01OLIW8VNVCU00008S@mauve.mrochek.com> <507EF95D.5090007@dcrocker.net> <01OLIXV2SU4O00008S@mauve.mrochek.com> <5B0F81787945877A5CC3794B@JcK-HP8200.jck.com> <01OLJ38YAL9600008S@mauve.mrochek.com> <507F3CEA.2010306@dcrocker.net> <01OLJ9JAK8SQ00008S@mauve.mrochek.com> <507F5249.2090507@dcrocker.net> <CALaySJKD+JbkOuZsC7wQtNNLHBP-4a_=DNfQ0XkQWoCq78-JGg@mail.gmail.com> <E73A2748BBE3FA6E1EE3A2C3@JcK-HP8200.jck.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Pobox-Relay-ID: 1F54F242-1987-11E2-90CF-9A8C2E706CDE-02871704!b-pb-sasl-quonix.pobox.com
X-Mailman-Approved-At: Fri, 19 Oct 2012 00:15:04 -0700
Cc: Ned Freed <ned.freed@mrochek.com>, draft-leiba-5322upd-from-group.all@tools.ietf.org, ned+ietf@mauve.mrochek.com, gen-art@ietf.org, johnl@taugh.com, dcrocker@bbiw.net, John C Klensin <john-ietf@jck.com>, Barry Leiba <barryleiba@computer.org>
Subject: Re: [Gen-art] Gen-ART LC review of draft-leiba-5322upd-from-group-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: Fri, 19 Oct 2012 00:51:37 -0000

On Thu, 2012-10-18, John C Klensin wrote:
<snip>

> As I said earlier, I can live with almost anything if it is
> correct and allows us to move forward.  I am, however, getting
> more concerned about the consequences to the virtual 5322bis and
> its future instantiation if we go down these paths.  I would
> really not like to be the relevant AD (or Pete-bis) trying to
> defend leaving the explanation and reference out of 5322bis
> given that they were important enough to include in this
> document and, if the explanation and reference go into 5322bis,
> why a large series of other references and explanations should
> not be included.  I'd be a tad happier if this explanatory stuff
> when into an appendix rather than the text.  

<serious value="false">
How about we put the explanation right next to the justification in 
5322 why <group> was not allowed in From: in the first place?
</serious>

I have wondered about that limitation for at least 15 years. I
have come up with possible explanations but without a shred of
evidence from the RFCs.

<snip>
-- 
Bill McQuillan <McQuilWP@pobox.com>


From alexey.melnikov@isode.com  Fri Oct 19 05:15:07 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 95C9E21F8643 for <gen-art@ietfa.amsl.com>; Fri, 19 Oct 2012 05:15:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.409
X-Spam-Level: 
X-Spam-Status: No, score=-102.409 tagged_above=-999 required=5 tests=[AWL=0.190, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00lJDSuXRpVB for <gen-art@ietfa.amsl.com>; Fri, 19 Oct 2012 05:15:06 -0700 (PDT)
Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id 6737821F863F for <gen-art@ietf.org>; Fri, 19 Oct 2012 05:15:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1350648905; d=isode.com; s=selector; i=@isode.com; bh=YSTixY7IeF3ewtEpZ7df9t4iaWS+TohZN2y5BnvnRfM=; 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=uBRrB/KoMSsZGenloBnMlieNIgM5ucI3bJpLeXxvUAMu5X3jKoGId/ru3AC4GAzOu6J0vS Rc6DwB7vIsNtU4uuGShfip8L5oPIMvkLDGIsbafJ++wMtPrIsQo2lwJ5GHEqyFMFhOVFKW E48Fu6XrUSGcrsn3tWc+ty8GB95LlYc=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by statler.isode.com (submission channel) via TCP with ESMTPA  id <UIFESAAbAkA-@statler.isode.com>; Fri, 19 Oct 2012 13:15:05 +0100
Message-ID: <5081444F.8090806@isode.com>
Date: Fri, 19 Oct 2012 13:15:11 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
To: Martin Thomson <martin.thomson@gmail.com>
References: <CABkgnnX11-NWygv3xzzcVRs=-nUJH7xb3N7VfrhKyq517kC-MA@mail.gmail.com>
In-Reply-To: <CABkgnnX11-NWygv3xzzcVRs=-nUJH7xb3N7VfrhKyq517kC-MA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-appsawg-media-type-suffix-regs.all@tools.ietf.org, gen-art@ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-appsawg-media-type-suffix-regs-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: Fri, 19 Oct 2012 12:15:07 -0000

Hi Martin,
Thank you for your review.

On 16/10/2012 22:48, Martin Thomson 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-appsawg-media-type-suffix-regs-06
> Reviewer: Martin Thomson
> Review Date: 2012-10-16
> IETF LC End Date: 2012-10-19
> IESG Telechat date: 2012-10-25
>
> Summary: This document is ready for publication as a (?) RFC.
>
> Minor issues: Is BCP status really appropriate?  Informational seems
> more appropriate for this sort of document.  The choice of providing a
> modicum of guidance in Section 2, as opposed to in the RFC that
> establishes the registry, could suggest this status, but that seems a
> bit weak as motivation.
This is a Normative reference for a BCP. It was split off from it.

I agree the registrations themselves can be Informational.
> Nits:
>
> +der doesn't even make a passing reference to +ber.  That's odd, since
> one describes a subset of the other.
It might be worth adding a sentence on this.
> Mention of schema for +der and +ber doesn't seem relevant to the key
> security consideration: that structures can be nested indefinitely.
> This is possible regardless of what the schema says - a generic
> processor is more likely to fall victim in that regard.
This is not really different from arbitrary nesting in, for example, 
XML. But I suppose this can be pointed out explicitly.


From tony@att.com  Fri Oct 19 05:30:47 2012
Return-Path: <tony@att.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 0943C21F8641 for <gen-art@ietfa.amsl.com>; Fri, 19 Oct 2012 05:30:47 -0700 (PDT)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Vhux3TWQ8qg for <gen-art@ietfa.amsl.com>; Fri, 19 Oct 2012 05:30:46 -0700 (PDT)
Received: from nbfkord-smmo07.seg.att.com (nbfkord-smmo07.seg.att.com [209.65.160.93]) by ietfa.amsl.com (Postfix) with ESMTP id 463CB21F8480 for <gen-art@ietf.org>; Fri, 19 Oct 2012 05:30:46 -0700 (PDT)
Received: from unknown [144.160.20.145] (EHLO mlpd192.enaf.sfdc.sbc.com) by nbfkord-smmo07.seg.att.com(mxl_mta-6.11.0-12) over TLS secured channel with ESMTP id 5f741805.0.365042.00-386.1026036.nbfkord-smmo07.seg.att.com (envelope-from <tony@att.com>);  Fri, 19 Oct 2012 12:30:46 +0000 (UTC)
X-MXL-Hash: 508147f65008acf6-7eda57e6f9dd8dbb4d0b198547ad85915b16aaea
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q9JCUjhD013347 for <gen-art@ietf.org>; Fri, 19 Oct 2012 08:30:45 -0400
Received: from sflint02.pst.cso.att.com (sflint02.pst.cso.att.com [144.154.234.229]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q9JCUc9l013302 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Fri, 19 Oct 2012 08:30:41 -0400
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by sflint02.pst.cso.att.com (RSA Interceptor) for <gen-art@ietf.org>; Fri, 19 Oct 2012 08:30:17 -0400
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q9JCUFwR029364 for <gen-art@ietf.org>; Fri, 19 Oct 2012 08:30:15 -0400
Received: from dns.maillennium.att.com (mailgw1.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q9JCU9Y1028459 for <gen-art@ietf.org>; Fri, 19 Oct 2012 08:30:10 -0400
Received: from [135.70.108.96] (vpn-135-70-108-96.vpn.swst.att.com[135.70.108.96]) by maillennium.att.com (mailgw1) with ESMTP id <20121019122903gw100r2c7pe> (Authid: tony); Fri, 19 Oct 2012 12:29:04 +0000
X-Originating-IP: [135.70.108.96]
Message-ID: <508147CE.8020504@att.com>
Date: Fri, 19 Oct 2012 08:30:06 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>
References: <CABkgnnX11-NWygv3xzzcVRs=-nUJH7xb3N7VfrhKyq517kC-MA@mail.gmail.com> <5081444F.8090806@isode.com>
In-Reply-To: <5081444F.8090806@isode.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <tony@att.com>
X-SOURCE-IP: [144.160.20.145]
X-AnalysisOut: [v=2.0 cv=XqxNzy59 c=1 sm=0 a=ZRNLZ4dFUbCvG8UMqPvVAA==:17 a]
X-AnalysisOut: [=RqPfq0KeRFEA:10 a=T3ddMRUbpJkA:10 a=ttUpEkhFMjkA:10 a=ofM]
X-AnalysisOut: [gfj31e3cA:10 a=BLceEmwcHowA:10 a=8nJEP1OIZ-IA:10 a=zQP7CpK]
X-AnalysisOut: [OAAAA:8 a=tpHpYmXAcOYA:10 a=GO9qPJzFhAt7ufXnnKsA:9 a=wPNLv]
X-AnalysisOut: [fGTeEIA:10]
Cc: draft-ietf-appsawg-media-type-suffix-regs.all@tools.ietf.org, gen-art@ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-appsawg-media-type-suffix-regs-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: Fri, 19 Oct 2012 12:30:47 -0000

On 10/19/2012 8:15 AM, Alexey Melnikov wrote:
> Hi Martin,
> Thank you for your review.

Yes, thank you.

> On 16/10/2012 22:48, Martin Thomson wrote:
>
>> Nits:
>>
>> +der doesn't even make a passing reference to +ber.  That's odd, since
>> one describes a subset of the other.
> It might be worth adding a sentence on this.

I originally had the two in the same section with a common description 
and subsections for the registration forms, making it very obvious that 
they were related. I got comments to separate them out an dpull them 
both up to top level.

You can still tell that they are related by the fact that they use the 
same reference, but do we really need any additional text? My 
inclination is to not add anything further.

     Tony

From peter@akayla.com  Sun Oct 21 14:39:33 2012
Return-Path: <peter@akayla.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F31A521F88FE; Sun, 21 Oct 2012 14:39:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.299
X-Spam-Level: 
X-Spam-Status: No, score=-0.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MANGLED_LIST=2.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aBZf2oN9T-vi; Sun, 21 Oct 2012 14:39:32 -0700 (PDT)
Received: from p3plsmtpa06-02.prod.phx3.secureserver.net (p3plsmtpa06-02.prod.phx3.secureserver.net [173.201.192.103]) by ietfa.amsl.com (Postfix) with ESMTP id 0CA9321F88F5; Sun, 21 Oct 2012 14:39:31 -0700 (PDT)
Received: from [192.168.6.4] ([64.134.68.84]) by p3plsmtpa06-02.prod.phx3.secureserver.net with  id DxfU1k0041p5FpL01xfV5A; Sun, 21 Oct 2012 14:39:30 -0700
User-Agent: Microsoft-MacOutlook/14.2.4.120824
Date: Sun, 21 Oct 2012 14:39:31 -0700
From: Peter Yee <peter@akayla.com>
To: <draft-ietf-nfsv4-federated-fs-protocol.all@tools.ietf.org>
Message-ID: <CCA9B9A3.11A0%peter@akayla.com>
Thread-Topic: Gen-ART review of draft-ietf-nfsv4-federated-fs-protocol-13
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: gen-art@ietf.org, "ietf@ietf.org" <ietf@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-nfsv4-federated-fs-protocol-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, 21 Oct 2012 21:39:33 -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-nfsv4-federated-fs-protocol-13
Reviewer: Peter Yee
Review Date: Oct-19-2012
IETF LC End Date: Oct-22-2012
IESG Telechat date: TBD


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


This Standards Track document describes a protocol for maintaining a
Namespace Database for use with federated filesystem protocols.  The
document is well-written with good examples and little need to jump back
and forth in the text to understand it.

General: Are ranges (in attribute values) inclusive or exclusive?  They
appear to be inclusive, but it might be worth saying that somewhere, if
only once.

Section 2.7, NsdbName definition: expand NSDB to Namespace Database as
this is the first use of the term.

Section 2.8.1, 2nd sentence: "extention" -> "extension"

Section 2.8.3, 2nd paragraph, last sentence: in addition to checking for
added FSL records, shouldn't the fileserver also be checking for deleted
or migrated FSLs?  And why would the fileserver do this at the expiration
of the FSN TTL instead of waiting for the next access to the that FSN?
Otherwise the fileserver could be generating unnecessary traffic, although
there is a tradeoff to be made vs. performance.

Section 2.8.3, 3rd paragraph after bullet items, 1st sentence: "which" ->
"that".  (Yeah, I know, grammar police.)

Section 2.9, 3rd paragraph, 2nd sentence: "admininistrative" ->
"administrative"

Section 2.12, 2nd paragraph, last sentence: expand NCE (NSDB Container
Entry) as this is the first use of the term.

Section 3.2, item #5: "fs_location" -> "fs_locations"

Section 4.1, 1st paragraph, 3rd sentence: probably worth expanding "DSE"
to "DSA-specific entry" here.

Section 4.2.1.8, 1st paragraph, 2nd sentence: bracket "Section 2.8.1" in
"(see" and ")" for readability.

Section 4.2.2: "LDAP Objects" -> "LDAP Object Classes" seems appropriate.

Section 4.2.2.1, 2nd and 3rd sentences: replace "fedfsFsn" with
"fedfsNsdbContainerInfo"

Section 4.2.2.2, 5th paragraph: how is the prohibition on referencing
other attributes in the fedfsFsn object class supposed to work if this
document is the defining document for that object class?

Section 5.1.3.1, 1st paragraph after LDIF definition: a port number of
2049 is given.  Since this is already the default value, why not use a
different value?  Otherwise, there would be no practical need to include
that port number in the FSL creation request.

Section 5.1.3.1, 1st paragraph after LDIF definition: "up to date" ->
"up-to-date"

Section 5.1.3.2, 2nd paragraph: "a" -> "an"

Section 5.1.3.2, table entry for "fedfsNfsVarSub": "substituion" ->
"substitution"

Section 5.1.4, 1st paragraph, 1st sentence: "a Fileset location" -> "an
FSL"

Section 7.3, 2nd paragraph, "Specification" value: presumably this will be
changed to the RFC number when issued?

Section 8, 1st paragraph (definition of Administrator): "an" -> "a"

Section 8, 3rd paragraph (definition of Client): "filesystem access" ->
"file-access" for consistency of usage with the rest of the document.

Section 8, 5th paragraph (definition of Fileserver): rather than
discussing "a filesystem", should this be "one or more filesystems"?  Or
is a fileserver limited to exporting one filesystem?

Section 8, 8th paragraph (definition of Filesystem Access Protocol):
following up on the 3rd paragraph, should this be "File-access Protocol"
for consistency?

Section 8, 9th paragraph (definition of FSL), 2nd sentence: "fs_location"
-> "fs_locations".




From peter@akayla.com  Sun Oct 21 20:35:44 2012
Return-Path: <peter@akayla.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49A5121F8AB9 for <gen-art@ietfa.amsl.com>; Sun, 21 Oct 2012 20:35:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.268
X-Spam-Level: 
X-Spam-Status: No, score=-0.268 tagged_above=-999 required=5 tests=[AWL=-0.010, BAYES_00=-2.599, MANGLED_LIST=2.3, MIME_BASE64_BLANKS=0.041]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XTrkwHdTIV2x for <gen-art@ietfa.amsl.com>; Sun, 21 Oct 2012 20:35:43 -0700 (PDT)
Received: from smtpauth05.prod.mesa1.secureserver.net (smtpauth05.prod.mesa1.secureserver.net [64.202.165.99]) by ietfa.amsl.com (Postfix) with SMTP id 66DD121F8A99 for <gen-art@ietf.org>; Sun, 21 Oct 2012 20:35:43 -0700 (PDT)
Received: (qmail 21731 invoked from network); 22 Oct 2012 03:35:42 -0000
Received: from unknown (64.134.68.84) by smtpauth05.prod.mesa1.secureserver.net (64.202.165.99) with ESMTP; 22 Oct 2012 03:35:40 -0000
User-Agent: Microsoft-MacOutlook/14.2.4.120824
Date: Sun, 21 Oct 2012 20:35:36 -0700
From: Peter Yee <peter@akayla.com>
To: Chuck Lever <chuck.lever@oracle.com>
Message-ID: <CCAA0CA5.11A5%peter@akayla.com>
Thread-Topic: Gen-ART review of draft-ietf-nfsv4-federated-fs-protocol-13
In-Reply-To: <8E799E97-421F-4ECE-A1F0-CFCBE605C3E6@oracle.com>
Mime-version: 1.0
Content-type: multipart/mixed; boundary="B_3433696546_3314490"
Cc: gen-art@ietf.org, "ietf@ietf.org" <ietf@ietf.org>, draft-ietf-nfsv4-federated-fs-protocol.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-nfsv4-federated-fs-protocol-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, 22 Oct 2012 03:35:44 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

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

Chuck,
	Ranges include the 0,255 that appears commonly in the document in
attribute definitions along with one case of -2147483648,2147483647.

	Kind regards,
		-Peter

On 10/21/12 3:27 PM, "Chuck Lever" <chuck.lever@oracle.com> wrote:

>
>On Oct 21, 2012, at 5:39 PM, Peter Yee <peter@akayla.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>
>> 
>> Document: draft-ietf-nfsv4-federated-fs-protocol-13
>> Reviewer: Peter Yee
>> Review Date: Oct-19-2012
>> IETF LC End Date: Oct-22-2012
>> IESG Telechat date: TBD
>> 
>> 
>> Summary: This draft is basically ready for publication, but has nits
>>that
>> should be fixed before publication. [Ready with nits.]
>> 
>> 
>> This Standards Track document describes a protocol for maintaining a
>> Namespace Database for use with federated filesystem protocols.  The
>> document is well-written with good examples and little need to jump back
>> and forth in the text to understand it.
>> 
>> General: Are ranges (in attribute values) inclusive or exclusive?  They
>> appear to be inclusive, but it might be worth saying that somewhere, if
>> only once.
>
>Can you give me an example of a range that might need clarification?
>
>I will address these comments and co-ordinate draft updates with our WG
>editor, Tom Haynes.
>
>Thanks for your review.
>
>> Section 2.7, NsdbName definition: expand NSDB to Namespace Database as
>> this is the first use of the term.
>> 
>> Section 2.8.1, 2nd sentence: "extention" -> "extension"
>> 
>> Section 2.8.3, 2nd paragraph, last sentence: in addition to checking for
>> added FSL records, shouldn't the fileserver also be checking for deleted
>> or migrated FSLs?  And why would the fileserver do this at the
>>expiration
>> of the FSN TTL instead of waiting for the next access to the that FSN?
>> Otherwise the fileserver could be generating unnecessary traffic,
>>although
>> there is a tradeoff to be made vs. performance.
>> 
>> Section 2.8.3, 3rd paragraph after bullet items, 1st sentence: "which"
>>->
>> "that".  (Yeah, I know, grammar police.)
>> 
>> Section 2.9, 3rd paragraph, 2nd sentence: "admininistrative" ->
>> "administrative"
>> 
>> Section 2.12, 2nd paragraph, last sentence: expand NCE (NSDB Container
>> Entry) as this is the first use of the term.
>> 
>> Section 3.2, item #5: "fs_location" -> "fs_locations"
>> 
>> Section 4.1, 1st paragraph, 3rd sentence: probably worth expanding "DSE"
>> to "DSA-specific entry" here.
>> 
>> Section 4.2.1.8, 1st paragraph, 2nd sentence: bracket "Section 2.8.1" in
>> "(see" and ")" for readability.
>> 
>> Section 4.2.2: "LDAP Objects" -> "LDAP Object Classes" seems
>>appropriate.
>> 
>> Section 4.2.2.1, 2nd and 3rd sentences: replace "fedfsFsn" with
>> "fedfsNsdbContainerInfo"
>> 
>> Section 4.2.2.2, 5th paragraph: how is the prohibition on referencing
>> other attributes in the fedfsFsn object class supposed to work if this
>> document is the defining document for that object class?
>> 
>> Section 5.1.3.1, 1st paragraph after LDIF definition: a port number of
>> 2049 is given.  Since this is already the default value, why not use a
>> different value?  Otherwise, there would be no practical need to include
>> that port number in the FSL creation request.
>> 
>> Section 5.1.3.1, 1st paragraph after LDIF definition: "up to date" ->
>> "up-to-date"
>> 
>> Section 5.1.3.2, 2nd paragraph: "a" -> "an"
>> 
>> Section 5.1.3.2, table entry for "fedfsNfsVarSub": "substituion" ->
>> "substitution"
>> 
>> Section 5.1.4, 1st paragraph, 1st sentence: "a Fileset location" -> "an
>> FSL"
>> 
>> Section 7.3, 2nd paragraph, "Specification" value: presumably this will
>>be
>> changed to the RFC number when issued?
>> 
>> Section 8, 1st paragraph (definition of Administrator): "an" -> "a"
>> 
>> Section 8, 3rd paragraph (definition of Client): "filesystem access" ->
>> "file-access" for consistency of usage with the rest of the document.
>> 
>> Section 8, 5th paragraph (definition of Fileserver): rather than
>> discussing "a filesystem", should this be "one or more filesystems"?  Or
>> is a fileserver limited to exporting one filesystem?
>> 
>> Section 8, 8th paragraph (definition of Filesystem Access Protocol):
>> following up on the 3rd paragraph, should this be "File-access Protocol"
>> for consistency?
>> 
>> Section 8, 9th paragraph (definition of FSL), 2nd sentence:
>>"fs_location"
>> -> "fs_locations".
>> 
>> 
>> 
>
>-- 
>Chuck Lever
>chuck[dot]lever[at]oracle[dot]com
>
>
>
>
>


--B_3433696546_3314490
Content-type: application/xml; name="default[4].xml"
Content-disposition: attachment;
	filename="default[4].xml"
Content-transfer-encoding: base64


UEsDBBQABgAIAAAAIQCb6HBP/AAAABwCAAATAAAAW0NvbnRlbnRfVHlwZXNdLnhtbKyRy2rD
MBBF94X+g9C22HK6KKXYzqKPXR+L9AMGeWyL2CMhTULy9x07LpQSAoVuBNLMvffMqFwfxkHt
MSbnqdKrvNAKyfrGUVfpz81Ldq9VYqAGBk9Y6SMmva6vr8rNMWBSoqZU6Z45PBiTbI8jpNwH
JKm0Po7Aco2dCWC30KG5LYo7Yz0xEmc8eei6fMIWdgOr54M8n0hErtXjqW+KqjSEMDgLLKBm
qpqzuohDuiDcU/OLLlvIclHO5ql3Id0sCe+ymugaVB8Q+Q1G4TAsQ+LP8xVIRov5ZeYz0b5t
ncXG290o68hn48XsTwCr/4n+zjTz39ZfAAAA//8DAFBLAwQUAAYACAAAACEApdan58AAAAA2
AQAACwAAAF9yZWxzLy5yZWxzhI/PasMwDIfvhb2D0X1R0sMYJXYvpZBDL6N9AOEof2giG9sb
69tPxwYKuwiEpO/3qT3+rov54ZTnIBaaqgbD4kM/y2jhdj2/f4LJhaSnJQhbeHCGo3vbtV+8
UNGjPM0xG6VItjCVEg+I2U+8Uq5CZNHJENJKRds0YiR/p5FxX9cfmJ4Z4DZM0/UWUtc3YK6P
qMn/s8MwzJ5PwX+vLOVFBG43lExp5GKhqC/jU72QqGWq1B7Qtbj51v0BAAD//wMAUEsDBBQA
BgAIAAAAIQBreZYWgwAAAIoAAAAcAAAAdGhlbWUvdGhlbWUvdGhlbWVNYW5hZ2VyLnhtbAzM
TQrDIBBA4X2hd5DZN2O7KEVissuuu/YAQ5waQceg0p/b1+XjgzfO3xTVm0sNWSycBw2KZc0u
iLfwfCynG6jaSBzFLGzhxxXm6XgYybSNE99JyHNRfSPVkIWttd0g1rUr1SHvLN1euSRqPYtH
V+jT9yniResrJgoCOP0BAAD//wMAUEsDBBQABgAIAAAAIQAhWqKEIQcAANsdAAAWAAAAdGhl
bWUvdGhlbWUvdGhlbWUxLnhtbOxZT28bRRS/I/EdRnsvsRMnTaI6VezYDbRpo9gt6nG8O/ZO
M7uzmhkn8Q21RyQkREEcqMSNAwIqtRKX8mkCRVCkfgXezOyud+Jxk5QAFTSH1jv7e2/e+70/
82evXD1KGDogQlKeNoP6e7UAkTTkEU1HzeB2v3tpNUBS4TTCjKekGUyIDK5uvPvOFbyuYpIQ
BPKpXMfNIFYqW19YkCEMY/kez0gK74ZcJFjBoxgtRAIfgt6ELSzWaisLCaZpgFKcgNpbwyEN
CeprlcFGobzD4DFVUg+ETPS0auJIGGy0X9cIOZFtJtABZs0A5on4YZ8cqQAxLBW8aAY18xcs
bFxZwOu5EFNzZCtyXfOXy+UC0f6imVOMBuWk9W5j7fJWqd8AmJrFdTqddqde6jMAHIbgqbWl
qrPRXa23Cp0VkP05q7tdW641XHxF/9KMzWutVmt5LbfFKjUg+7Mxg1+trTQ2Fx28AVn88gy+
0dpst1ccvAFZ/MoMvnt5baXh4g0oZjTdn0HrgHa7ufYSMuRs2wtfBfhqLYdPUZANZXbpKYY8
VfNyLcH3uOgCQAMZVjRFapKRIQ4hi9uY0YGgegK8TnDljR0K5cyQngvJUNBMNYMPMgwVMdX3
8tl3L589Qcf3nx7f//H4wYPj+z9YRY7UNk5HVakX33z6x6OP0O9Pvn7x8HM/Xlbxv3z/8c8/
feYHQvlMzXn+xeNfnz5+/uUnv3370APfFHhQhfdpQiS6SQ7RHk/AMcOKazkZiPNJ9GNMqxKb
6UjiFOtZPPo7KnbQNyeYYQ+uRVwG7whoHz7gtfE9x+BeLMYqj7fj2fU4cYA7nLMWF14Wruu5
KjT3x+nIP7kYV3F7GB/45m7j1IlvZ5xB36Q+le2YOGbuMpwqPCIpUUi/4/uEePi6S6nD6w4N
BZd8qNBdilqYeinp04GTTVOhbZpAXCY+AyHeDjc7d1CLM5/XW+TARUJVYOYxvk+YQ+M1PFY4
8ans44RVCb+BVewzsjcRYRXXkQoiPSKMo05EpPTJ3BLgbyXo16F1+MO+wyaJixSK7vt03sCc
V5FbfL8d4yTzYXs0javY9+U+pChGu1z54DvcrRD9DHHA6dxw36HECffp3eA2HTkmTRNEvxkL
TyyvEe7kb2/ChpiYVgNN3enVCU1f1bgT6Nu54xfXuKFVPv/qkcfuN7VlbwIJvprZPtGo5+FO
tuc2FxF987vzFh6nuwQKYnaJetuc3zbn4D/fnOfV88W35GkXhgatt0x2o2223cncXfeQMtZT
E0ZuSLPxlrD2RF0Y1HLmxEnKU1gWw09dyTCBgxsJbGSQ4OpDquJejDPYtNcDrWQkc9UjiTIu
4bBohr26NR42/soeNZf1IcR2DonVDo/s8JIeLs4apRpj1cgcaIuJlrSCs062dDlXCr69zmR1
bdSZZ6sb00xTdGYrXdYUm0M5UF66BoMlm7CpQbAVApZX4Myvp4bDDmYk0rzbGBVhMVH4e0KU
e20diXFEbIic4QqbdRO7IoVm/NPu2Rw5H5sla0Da6UaYtJifP2ckuVAwJRkET1YTS6u1xVJ0
2AzWlheXAxTirBkM4ZgLP5MMgib1NhCzEdwVhUrYrD21Fk2RTj1e82dVHW4u5hSMU8aZkGoL
y9jG0LzKQ8VSPZO1f3G5oZPtYhzwNJOzWbG0Cinyr1kBoXZDS4ZDEqpqsCsjmjv7mHdCPlZE
9OLoEA3YWOxhCD9wqv2JqITbClPQ+gGu1jTb5pXbW/NOU73QMjg7jlkW47xb6quZouIs3PST
0gbzVDEPfPPabpw7vyu64i/KlWoa/89c0csBXB4sRToCIdzsCox0pTQDLlTMoQtlMQ27AtZ9
0zsgW+B6Fl4D+XC/bP4X5ED/b2vO6jBlDWdAtUdHSFBYTlQsCNmFtmSy7xRl9XzpsSpZrshk
VMVcmVmzB+SAsL7ugSu6BwcohlQ33SRvAwZ3Mv/c57yCBiO9R6nWm9PJyqXT1sA/vXGxxQxO
ndhL6Pwt+C9NLFf36epn5Y14sUZWHdEvprukRlEVzuK3tpZP9ZomnGUBrqy1tmPNeLy4XBgH
UZz1GAbL/UwGV0BI/wPrHxUhsx8r9ILa53vQWxF8e7D8IcjqS7qrQQbpBml/DWDfYwdtMmlV
ltp856NZKxbrC96olvOeIFtbdpZ4n5PschPlTufU4kWSnTPscG3H5lINkT1ZojA0LM4hJjDm
K1f1QxQf3INAb8GV/5jZT1MygydTB9muMNk14NEk/8mkXXBt1ukzjEaydI8MEY2OivNHyYQt
Ift5pNgiG7QW04lWCi75Dg2uYI7Xona1LIUXTxcuJczM0LJLYXOX5lMAH8fyxq2PdoC3TdZ6
rYurYIqlf4WyMxjvp8x78jkrZfag+MpAvQZl6ujVlOVMAXmziQefNwWGo1fP9F9YdGymm5Td
+BMAAP//AwBQSwMEFAAGAAgAAAAhAA3RkJ+2AAAAGwEAACcAAAB0aGVtZS90aGVtZS9fcmVs
cy90aGVtZU1hbmFnZXIueG1sLnJlbHOEj00KwjAUhPeCdwhvb9O6EJEm3YjQrdQDhOQ1DTY/
JFHs7Q2uLAguh2G+mWm7l53JE2My3jFoqhoIOumVcZrBbbjsjkBSFk6J2TtksGCCjm837RVn
kUsoTSYkUiguMZhyDidKk5zQilT5gK44o49W5CKjpkHIu9BI93V9oPGbAXzFJL1iEHvVABmW
UJr/s/04GolnLx8WXf5RQXPZhQUoosbM4CObqkwEylu6usTfAAAA//8DAFBLAQItABQABgAI
AAAAIQCb6HBP/AAAABwCAAATAAAAAAAAAAAAAAAAAAAAAABbQ29udGVudF9UeXBlc10ueG1s
UEsBAi0AFAAGAAgAAAAhAKXWp+fAAAAANgEAAAsAAAAAAAAAAAAAAAAALQEAAF9yZWxzLy5y
ZWxzUEsBAi0AFAAGAAgAAAAhAGt5lhaDAAAAigAAABwAAAAAAAAAAAAAAAAAFgIAAHRoZW1l
L3RoZW1lL3RoZW1lTWFuYWdlci54bWxQSwECLQAUAAYACAAAACEAIVqihCEHAADbHQAAFgAA
AAAAAAAAAAAAAADTAgAAdGhlbWUvdGhlbWUvdGhlbWUxLnhtbFBLAQItABQABgAIAAAAIQAN
0ZCftgAAABsBAAAnAAAAAAAAAAAAAAAAACgKAAB0aGVtZS90aGVtZS9fcmVscy90aGVtZU1h
bmFnZXIueG1sLnJlbHNQSwUGAAAAAAUABQBdAQAAIwsAAAAA
--B_3433696546_3314490--



From wassim.haddad@ericsson.com  Sun Oct 21 23:39:11 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 04D9821F8470 for <gen-art@ietfa.amsl.com>; Sun, 21 Oct 2012 23:39:11 -0700 (PDT)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E2hiSk+v188h for <gen-art@ietfa.amsl.com>; Sun, 21 Oct 2012 23:39:10 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 0B91821F8466 for <gen-art@ietf.org>; Sun, 21 Oct 2012 23:39:09 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q9M6fU00009309; Mon, 22 Oct 2012 01:41:32 -0500
Received: from client-vpn-011.edd.ericsson.se (147.117.20.214) by eusaamw0711.eamcs.ericsson.se (147.117.20.179) with Microsoft SMTP Server id 8.3.279.1; Mon, 22 Oct 2012 02:38:45 -0400
From: Wassim Haddad <wassim.haddad@ericsson.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 21 Oct 2012 23:38:38 -0700
Message-ID: <E72B2EC7-0C45-4278-8764-4CD0762CD672@ericsson.com>
To: Gen-art <gen-art@ietf.org>
MIME-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
Cc: Alissa Cooper <acooper@cdt.org>, draft-ietf-geopriv-local-civic-09.all@tools.ietf.org
Subject: [Gen-art]  Gen-ART Review of draft-ietf-geopriv-local-civic-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 06:39:11 -0000

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

Document: draft-ietf-geopriv-local-civic-09
Reviewer:  Wassim Haddad
Review Date:  21 Oct 2012
IETF LC End Date: 04 Oct 2012
IETF Telechat Date: 25 Oct 2012

Summary:  This draft is ready for publication as proposed standard.

- Major Issues: None

- Minor Issues: None


Regards,

Wassim H.






From wassim.haddad@ericsson.com  Sun Oct 21 23:44:43 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 06C1621F887B for <gen-art@ietfa.amsl.com>; Sun, 21 Oct 2012 23:44:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YpXH4qhXMjM2 for <gen-art@ietfa.amsl.com>; Sun, 21 Oct 2012 23:44:42 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 01EB021F8842 for <gen-art@ietf.org>; Sun, 21 Oct 2012 23:44:41 -0700 (PDT)
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 q9M6l4eY009367; Mon, 22 Oct 2012 01:47:05 -0500
Received: from client-vpn-011.edd.ericsson.se (147.117.20.214) by eusaamw0707.eamcs.ericsson.se (147.117.20.92) with Microsoft SMTP Server id 8.3.279.1; Mon, 22 Oct 2012 02:44:18 -0400
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Apple Message framework v1278)
From: Wassim Haddad <wassim.haddad@ericsson.com>
Date: Sun, 21 Oct 2012 23:44:13 -0700
Content-Transfer-Encoding: quoted-printable
Message-ID: <B59B9A3F-83B7-41C9-8395-94FBCE417C90@ericsson.com>
References: <E72B2EC7-0C45-4278-8764-4CD0762CD672@ericsson.com>
To: Gen-art <gen-art@ietf.org>
X-Mailer: Apple Mail (2.1278)
Cc: Alissa Cooper <acooper@cdt.org>, draft-ietf-geopriv-local-civic.all@tools.ietf.org
Subject: [Gen-art] Fwd: Gen-ART Review of draft-ietf-geopriv-local-civic-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 06:44:43 -0000

Re-sending with the correct email address


Regards,

Wassim H.





Begin forwarded message:

> From: Wassim Haddad <wassim.haddad@ericsson.com>
> Subject: [Gen-art] Gen-ART Review of draft-ietf-geopriv-local-civic-09
> Date: October 21, 2012 11:38:38 PM PDT
> To: Gen-art <gen-art@ietf.org>
> Cc: Wassim Haddad <wassim.haddad@ericsson.com>, =
"draft-ietf-geopriv-local-civic-09.all@tools.ietf.org" =
<draft-ietf-geopriv-local-civic-09.all@tools.ietf.org>, Alissa Cooper =
<acooper@cdt.org>
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART,=20
> please see the FAQ at =
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>=20
> Document: draft-ietf-geopriv-local-civic-09
> Reviewer:  Wassim Haddad
> Review Date:  21 Oct 2012
> IETF LC End Date: 04 Oct 2012
> IETF Telechat Date: 25 Oct 2012
>=20
> Summary:  This draft is ready for publication as proposed standard.
>=20
> - Major Issues: None
>=20
> - Minor Issues: None
>=20
>=20
> Regards,
>=20
> Wassim H.
>=20
>=20
>=20
>=20
>=20


From chuck.lever@oracle.com  Sun Oct 21 15:27:35 2012
Return-Path: <chuck.lever@oracle.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 E5B7721F8C00; Sun, 21 Oct 2012 15:27:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.361
X-Spam-Level: 
X-Spam-Status: No, score=-9.361 tagged_above=-999 required=5 tests=[AWL=-1.063, BAYES_00=-2.599, MANGLED_LIST=2.3, RCVD_IN_DNSWL_HI=-8, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9oowAVDfqVp6; Sun, 21 Oct 2012 15:27:33 -0700 (PDT)
Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by ietfa.amsl.com (Postfix) with ESMTP id 86D7321F8B7C; Sun, 21 Oct 2012 15:27:33 -0700 (PDT)
Received: from acsinet21.oracle.com (acsinet21.oracle.com [141.146.126.237]) by acsinet15.oracle.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id q9LMRPew019467 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 21 Oct 2012 22:27:26 GMT
Received: from acsmt357.oracle.com (acsmt357.oracle.com [141.146.40.157]) by acsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id q9LMRPrd009147 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 21 Oct 2012 22:27:25 GMT
Received: from abhmt104.oracle.com (abhmt104.oracle.com [141.146.116.56]) by acsmt357.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id q9LMROTX032334; Sun, 21 Oct 2012 17:27:24 -0500
Received: from moret.1015granger.net (/99.26.161.222) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Sun, 21 Oct 2012 15:27:24 -0700
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Chuck Lever <chuck.lever@oracle.com>
In-Reply-To: <CCA9B9A3.11A0%peter@akayla.com>
Date: Sun, 21 Oct 2012 18:27:23 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <8E799E97-421F-4ECE-A1F0-CFCBE605C3E6@oracle.com>
References: <CCA9B9A3.11A0%peter@akayla.com>
To: Peter Yee <peter@akayla.com>
X-Mailer: Apple Mail (2.1499)
X-Source-IP: acsinet21.oracle.com [141.146.126.237]
X-Mailman-Approved-At: Sun, 21 Oct 2012 23:54:24 -0700
Cc: gen-art@ietf.org, "ietf@ietf.org" <ietf@ietf.org>, draft-ietf-nfsv4-federated-fs-protocol.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-nfsv4-federated-fs-protocol-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, 21 Oct 2012 22:27:36 -0000

On Oct 21, 2012, at 5:39 PM, Peter Yee <peter@akayla.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>=20
> Document: draft-ietf-nfsv4-federated-fs-protocol-13
> Reviewer: Peter Yee
> Review Date: Oct-19-2012
> IETF LC End Date: Oct-22-2012
> IESG Telechat date: TBD
>=20
>=20
> Summary: This draft is basically ready for publication, but has nits =
that
> should be fixed before publication. [Ready with nits.]
>=20
>=20
> This Standards Track document describes a protocol for maintaining a
> Namespace Database for use with federated filesystem protocols.  The
> document is well-written with good examples and little need to jump =
back
> and forth in the text to understand it.
>=20
> General: Are ranges (in attribute values) inclusive or exclusive?  =
They
> appear to be inclusive, but it might be worth saying that somewhere, =
if
> only once.

Can you give me an example of a range that might need clarification?

I will address these comments and co-ordinate draft updates with our WG =
editor, Tom Haynes.

Thanks for your review. =20

> Section 2.7, NsdbName definition: expand NSDB to Namespace Database as
> this is the first use of the term.
>=20
> Section 2.8.1, 2nd sentence: "extention" -> "extension"
>=20
> Section 2.8.3, 2nd paragraph, last sentence: in addition to checking =
for
> added FSL records, shouldn't the fileserver also be checking for =
deleted
> or migrated FSLs?  And why would the fileserver do this at the =
expiration
> of the FSN TTL instead of waiting for the next access to the that FSN?
> Otherwise the fileserver could be generating unnecessary traffic, =
although
> there is a tradeoff to be made vs. performance.
>=20
> Section 2.8.3, 3rd paragraph after bullet items, 1st sentence: "which" =
->
> "that".  (Yeah, I know, grammar police.)
>=20
> Section 2.9, 3rd paragraph, 2nd sentence: "admininistrative" ->
> "administrative"
>=20
> Section 2.12, 2nd paragraph, last sentence: expand NCE (NSDB Container
> Entry) as this is the first use of the term.
>=20
> Section 3.2, item #5: "fs_location" -> "fs_locations"
>=20
> Section 4.1, 1st paragraph, 3rd sentence: probably worth expanding =
"DSE"
> to "DSA-specific entry" here.
>=20
> Section 4.2.1.8, 1st paragraph, 2nd sentence: bracket "Section 2.8.1" =
in
> "(see" and ")" for readability.
>=20
> Section 4.2.2: "LDAP Objects" -> "LDAP Object Classes" seems =
appropriate.
>=20
> Section 4.2.2.1, 2nd and 3rd sentences: replace "fedfsFsn" with
> "fedfsNsdbContainerInfo"
>=20
> Section 4.2.2.2, 5th paragraph: how is the prohibition on referencing
> other attributes in the fedfsFsn object class supposed to work if this
> document is the defining document for that object class?
>=20
> Section 5.1.3.1, 1st paragraph after LDIF definition: a port number of
> 2049 is given.  Since this is already the default value, why not use a
> different value?  Otherwise, there would be no practical need to =
include
> that port number in the FSL creation request.
>=20
> Section 5.1.3.1, 1st paragraph after LDIF definition: "up to date" ->
> "up-to-date"
>=20
> Section 5.1.3.2, 2nd paragraph: "a" -> "an"
>=20
> Section 5.1.3.2, table entry for "fedfsNfsVarSub": "substituion" ->
> "substitution"
>=20
> Section 5.1.4, 1st paragraph, 1st sentence: "a Fileset location" -> =
"an
> FSL"
>=20
> Section 7.3, 2nd paragraph, "Specification" value: presumably this =
will be
> changed to the RFC number when issued?
>=20
> Section 8, 1st paragraph (definition of Administrator): "an" -> "a"
>=20
> Section 8, 3rd paragraph (definition of Client): "filesystem access" =
->
> "file-access" for consistency of usage with the rest of the document.
>=20
> Section 8, 5th paragraph (definition of Fileserver): rather than
> discussing "a filesystem", should this be "one or more filesystems"?  =
Or
> is a fileserver limited to exporting one filesystem?
>=20
> Section 8, 8th paragraph (definition of Filesystem Access Protocol):
> following up on the 3rd paragraph, should this be "File-access =
Protocol"
> for consistency?
>=20
> Section 8, 9th paragraph (definition of FSL), 2nd sentence: =
"fs_location"
> -> "fs_locations".
>=20
>=20
>=20

--=20
Chuck Lever
chuck[dot]lever[at]oracle[dot]com





From Francis.Dupont@fdupont.fr  Mon Oct 22 07:42: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 4AAA321F8B9F for <gen-art@ietfa.amsl.com>; Mon, 22 Oct 2012 07:42:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EXADRUGnusHD for <gen-art@ietfa.amsl.com>; Mon, 22 Oct 2012 07:42:08 -0700 (PDT)
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 8E37721F8B81 for <gen-art@ietf.org>; Mon, 22 Oct 2012 07:42:08 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id q9MEg68l044322; Mon, 22 Oct 2012 16:42:06 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201210221442.q9MEg68l044322@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: gen-art@ietf.org
Date: Mon, 22 Oct 2012 16:42:06 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: draft-ietf-dhc-client-id.all@tools.ietf.org
Subject: [Gen-art] review of draft-ietf-dhc-client-id-06.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 14:42: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 wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document: draft-ietf-dhc-client-id-06.txt
Reviewer: Francis Dupont
Review Date: 20121018
IETF LC End Date: 20121017
IESG Telechat date: 20121025

Summary: Ready

Major issues: None

Minor issues: None (even some questions below could be promoted to issues)

Nits/editorial comments:
 There is no real justification: I had to read the first WGLC text to
 find the reason behind: there was a bug in RFC 2131.

 - Abstract page 1 and 1 page 4:
    return client identifier' option ->
    return 'client identifier' option

 - ToC page 3 and 6 page 6: Acknowledgements -> Acknowledgments

 - 1 page 4: DHCP server allocate -> DHCP servers allocate ?

 - 2 page 4: a combination of ... and ... constitute ... and are ... ->
  constitutes ... is (i.e., combination is the subject)?

 - 2 page 4: need not be unique -> are not required to be unique?

 - 3 page 5: the draft proposed to change "MUST NOT" into "MUST",
  perhaps it is enough to change them into "SHOULD"? (note this
  question comes from the lack of justification, and the use of
  loose terms as "update" or (worse) "clarify" in place of "fix"
  or "errata"... I.e., if you are convinced there was a bug the
  right fix is "MUST")

 - 7 page 6: RFC 3315 should IMHO be an informative reference

 - Authors' Addresses pages 6 and 7: extra spaces before ZIP codes?

Regards

Francis.Dupont@fdupont.fr

From vincent.roca@inria.fr  Mon Oct 22 07:58:27 2012
Return-Path: <vincent.roca@inria.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 714D621F8C24 for <gen-art@ietfa.amsl.com>; Mon, 22 Oct 2012 07:58:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.36
X-Spam-Level: 
X-Spam-Status: No, score=-110.36 tagged_above=-999 required=5 tests=[AWL=-0.111, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O7zK+OnxiRTP for <gen-art@ietfa.amsl.com>; Mon, 22 Oct 2012 07:58:26 -0700 (PDT)
Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by ietfa.amsl.com (Postfix) with ESMTP id 59AD921F8C25 for <gen-art@ietf.org>; Mon, 22 Oct 2012 07:58:26 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.80,630,1344204000"; d="scan'208";a="159945272"
Received: from geve.inrialpes.fr ([194.199.24.116]) by mail4-relais-sop.national.inria.fr with ESMTP/TLS/AES128-SHA; 22 Oct 2012 16:58:24 +0200
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Vincent Roca <vincent.roca@inria.fr>
In-Reply-To: <507EBEE9.2030909@ericsson.com>
Date: Mon, 22 Oct 2012 16:58:24 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <09C22160-F583-47C0-99B6-386F8DE580AB@inria.fr>
References: <507EBEE9.2030909@ericsson.com>
To: Miguel A. Garcia <Miguel.A.Garcia@ericsson.com>
X-Mailer: Apple Mail (2.1085)
Cc: Greg Shepherd <gjshep@gmail.com>, Vincent Roca <vincent.roca@inria.fr>, fecframe-chairs@tools.ietf.org, draft-ietf-fecframe-simple-rs.all@tools.ietf.org, Martin Stiemerling <martin.stiemerling@neclab.eu>, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-fecframe-simple-rs-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, 22 Oct 2012 14:58:27 -0000

Dear Miguel,

Thanks a lot for your comments.

> Document: draft-ietf-fecframe-simple-rs-04
> Reviewer: Miguel Garcia <Miguel.A.Garcia@ericsson.com>
> Review Date: 2012-10-17
> IETF LC End Date: 2012-10-22
>=20
> Summary: The document is ready for publication as a standards track =
RFC, but has some Nits that should be addressed.
>=20
> Major issues: none
>=20
> Minor issues: none
>=20
> Nits/editorial comments:
>=20
> - Section 5.1.1 starts with this sentence:
>=20
>   The FEC Framework Configuration Information (or FFCI) includes
>   information that MUST be communicated between the sender and
>   receiver(s).
>=20
> This is not a normative "MUST" that you are specifying. You are merely =
describing how another specification has a normative MUST, but it is not =
of this document. Therefore, this "MUST" should be replaced by a "need" =
or perhaps a "must".

I understand. Done.

NEW:
   The FEC Framework Configuration Information (or FFCI) includes
   information that must be communicated between the sender and
   receiver(s) [RFC6363].


> - Section 5.1.1.1 reads:
>=20
>   When SDP is used to communicate the FFCI, this FEC Encoding ID is
>   carried in the 'encoding-id' parameter.
>=20
> Two points here:
> a) I am missing a normative MUST, such as "this FEC Encoding ID MUST =
be carried..."
> b) I guess it would not be such a bad idea to complete the sentence =
with the attribute name in SDP and normative reference that defines the =
attribute and the parameter.
>=20
> Proposal:
>=20
>   When SDP is used to communicate the FFCI, this FEC Encoding ID MUST =
be
>   carried in the 'encoding-id' parameter of the  'fec-repair-flow'
>   attribute specified in RFC 6364 [RFC6364].

Excellent. This paragraph now reads:

NEW:
   When SDP is used to communicate the FFCI, this FEC Encoding ID MUST
   be carried in the 'encoding-id' parameter of the 'fec-repair-flow'
   attribute specified in RFC 6364 [RFC6364].


> - Similarly in Section 5.1.1.2:
>=20
> If you agree with this changes, you should do similar changes to =
Section 5.1.1.2, the text beginning with "When SDP is used..." Notice =
also that the example following this text in Section 5.1.1.2 is =
misleading because it does not contain a single SDP line, which is =
generally considered the atomic representation element in examples, but =
just a fraction of it. I suggest to extend the example to the full =
a=3Dfec-repair-flow line.

Done. And the associated example also illustrates the use of =
encoding-id=3D...

NEW:
   When SDP is used to communicate the FFCI, this FEC scheme-specific=20
   information MUST be carried in the 'fssi' parameter of the 'fec-
   repair-flow' attribute, in textual representation as specified in RFC
   6364 [RFC6364].  For instance:
   =20
   a=3Dfec-repair-flow: encoding-id=3DXXX; fssi=3DE:1400,S:0,m:8=20


> - Section 8, IANA. Isn't the name of the registry "Reliable Multicast =
Transport (RMT) FEC Encoding IDs and FEC Instance IDs"? Or am I looking =
at the wrong registry? I think that the "FEC Framework (FECFRAME) FEC =
Encoding IDs is one of the registries included under that umbrella of =
RMT FEC Encoding IDs. As a reader, I would like to be able to find the =
right registry without doubt.

Yes, it is one of the registries of the "Reliable Multicast Transport =
(RMT) FEC Encoding IDs and FEC Instance IDs" registry.
It's a bit complex (well, historical in fact). I have clarified.

NEW:
   Values of FEC Encoding IDs are subject to IANA registration.
   [RFC6363] defines general guidelines on IANA considerations.  In
   particular it defines the "FEC Framework (FECFRAME) FEC Encoding IDs"
   subregistry of the "Reliable Multicast Transport (RMT) FEC Encoding
   IDs and FEC Instance IDs" registry, whose values are granted on an
   IETF Consensus basis.


Thanks a lot.
Cheers,

    Vincent, on behalf of the authors


From yiu_lee@cable.comcast.com  Mon Oct 22 12:48:41 2012
Return-Path: <yiu_lee@cable.comcast.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 784FC11E809C for <gen-art@ietfa.amsl.com>; Mon, 22 Oct 2012 12:48:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.973
X-Spam-Level: 
X-Spam-Status: No, score=-103.973 tagged_above=-999 required=5 tests=[AWL=1.258, BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id frogoIa9oSxG for <gen-art@ietfa.amsl.com>; Mon, 22 Oct 2012 12:48:35 -0700 (PDT)
Received: from cable.comcast.com (copdcavout01.cable.comcast.com [76.96.32.253]) by ietfa.amsl.com (Postfix) with ESMTP id D0E7621F8904 for <gen-art@ietf.org>; Mon, 22 Oct 2012 12:48:34 -0700 (PDT)
Received: from ([24.40.56.114]) by copdcavout01.cable.comcast.com with ESMTP  id C7WM3M1.38700631; Mon, 22 Oct 2012 13:24:48 -0600
Received: from PACDCEXMB05.cable.comcast.com ([169.254.7.64]) by PACDCEXHUB01.cable.comcast.com ([fe80::84e8:95f3:f13b:169e%12]) with mapi id 14.02.0318.001; Mon, 22 Oct 2012 15:48:26 -0400
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: "Black, David" <david.black@emc.com>, Maglione Roberta <roberta.maglione@telecomitalia.it>, "'draft-ietf-softwire-dslite-deployment@tools.ietf.org'" <draft-ietf-softwire-dslite-deployment@tools.ietf.org>
Thread-Topic: Gen-ART review of draft-ietf-softwire-dslite-deployment-06
Thread-Index: AQHNsI4zRZf3m76IaEG1JdT7Fnudgg==
Date: Mon, 22 Oct 2012 19:48:26 +0000
Message-ID: <E3FAB1F4F41F3A45B287E8D9C53522FD37A8513C@PACDCEXMB05.cable.comcast.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7120DFAF49C@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.4.120824
x-originating-ip: [24.40.55.72]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3433765705_1570563"
MIME-Version: 1.0
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>, "softwire-chairs@tools.ietf.org" <softwire-chairs@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-softwire-dslite-deployment-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: Mon, 22 Oct 2012 19:48:41 -0000

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

Hi David,

Since the BNG would verify the v6 packets sent by B4 and the AFTR would
NAT the RFC1918 source address to the public address, I try to find a use
case where a theft could steal the service. From the AFTR's perspective,
the IPv4 address of the host behind B4 is irrelevant. Could you help to
find a use case which will introduce security risk because the AFTR can't
identify the IPv4 address?

Thanks,
Yiu

On 10/18/12 11:10 AM, "Black, David" <david.black@emc.com> wrote:

>Hello Roberta,
>
>In that case, more text is needed to explain in Section 2.8, and
>the related theft of service concern also needs to be discussed in
>that section and/or the Security Considerations section.
>
>Thanks,
>--David
>
>> -----Original Message-----
>> From: Maglione Roberta [mailto:roberta.maglione@telecomitalia.it]
>> Sent: Thursday, October 18, 2012 3:18 AM
>> To: Black, David; Lee, Yiu; 'draft-ietf-softwire-dslite-
>> deployment@tools.ietf.org'
>> Cc: Ralph Droms; gen-art@ietf.org; softwire-chairs@tools.ietf.org
>> Subject: RE: Gen-ART review of draft-ietf-softwire-dslite-deployment-06
>> 
>> Hello Yiu and David,
>> regarding point 5:
>> 
>> > [YL] Good catch. Actually I believe AFTR "does" have both IPv4 and
>> > IPv6 to identify the customer. I suggest we remove
>> >
>> > "but it will potentially introduce some additional complexity because
>> >    the AFTR does not have detailed customer identity information."
>> 
>> The point related to the accounting is different: what I meant here with
>> accounting is RADIUS based accounting, commonly used in Broadband
>>networks.
>> 
>> Today RADIUS accounting is done at the BNG level, the problem with the
>> introduction of the AFTR is that the AFTR does not interact with
>>AAA/RADIUS
>> Server for the initial authentication/authorization/accounting phase
>>because
>> the authentication/authorization/accounting process happens between BNG
>>and
>> RADIUS Server when the session comes up.
>> The ATFR is not able to perform RADIUS accounting because as it does not
>> interact with the RADIUS Server it does not have " detailed customer
>>identity
>> information" for example it does know the accounting session ID
>>associated to
>> that session, that's why it cannot do detailed accounting for each
>>single
>> subscriber even if the ATFR can still correlated IPv6 and IPv4 traffic
>> belonging to the same user.
>> 
>> This is an important operational issue, I would suggest to keep this
>>concept.
>> If you think is needed I can add some lines of text in order to clarify
>>this
>> point.
>> 
>> Thanks
>> Regards,
>> Roberta
>> 
>> -----Original Message-----
>> From: Black, David [mailto:david.black@emc.com]
>> Sent: Thursday, October 18, 2012 3:12 AM
>> To: Lee, Yiu; Maglione Roberta; carlw@mcsr-labs.org;
>> christian.jacquenet@orange.com; mohamed.boucadair@orange.com;
>>gen-art@ietf.org
>> Cc: softwires@ietf.org; ietf@ietf.org; Ralph Droms; Black, David
>> Subject: RE: Gen-ART review of draft-ietf-softwire-dslite-deployment-06
>> 
>> Yiu,
>> 
>> Thank you for your responses - most of them look fine, and in
>> particular anything that I don't comment on here is acceptable to me.
>> 
>> > [YL] In 2.2, we will add:
>> >
>> > "Note that reassembly at Tunnel Exit-Point is resource
>> >       intensive. A large number of B4 may terminate on the same AFTR.
>>If
>> many B4
>> >       fragment the packets, it would increase sufficient load to the
>>AFTR
>> for
>> >       reassembly. We recommend the operator should increase the MTU
>>size of
>> the IPv6
>> >       network between B4 and AFTR to avoid fragmentation."
>> 
>> I would change "is" to "may be" in the first line.
>> 
>> > >[5] Section 2.8 discusses IPv4 accounting at the AFTR, but notes that
>> > >"the AFTR does not have detailed customer identity information."
>>Does
>> > >that create a theft of service possibility?  If so, that possibility
>> > >should be mentioned as a security consideration.  Also, Section 2.8
>> > >ought to be expanded with a sentence or two explaining why the AFTR
>> > >does not have that identity information, and in particular to explain
>> > >whether and why it is unreasonable in some or all cases to expect
>> > >that customer identity information be provided to the AFTR as part
>> > >of provisioning each customer's softwire.
>> >
>> > [YL] Good catch. Actually I believe AFTR "does" have both IPv4 and
>>IPv6 to
>> > identify the customer. I suggest we remove
>> >
>> > "but it will potentially introduce some additional complexity because
>> >    the AFTR does not have detailed customer identity information."
>> 
>> That's definitely an easy way to address that issue, and it's fine with
>>me.
>> 
>> > >Section 2.3 on MTU Considerations could usefully mention MTU
>>discovery
>> > >techniques, as possibilities for customer IPv4 traffic to adapt to a
>> > >smaller IPv4 MTU.  If this is done, it would be useful to mention
>> > >RFC 4821 in addition to the mention of RFC 1191 in RFC 6333.
>> >
>> > [YL] We would consider RFC 4821. However, the challenge is I don't
>>have
>> > information how many current OS support RFC 4821. Since DS-lite is a
>> > transition technology, it would be unreasonable to ask the OS company
>>to
>> > implement RFC 4821 for DS-lite.
>> 
>> That's ok - this was a nit.
>> 
>> > >- Are one or both types of logging recommended?
>> >
>> > [YL] We tempted to recommend source-specific log. However, some
>>regulators
>> > require to use both and the regulations vary country from country,
>>this is
>> > why we left it open and let the operators to decide.
>> 
>> Please add a version of your explanation to the draft.
>> 
>> > >In Section 2.7, I'm having a hard time understanding which traffic is
>> > >intended to be subject to the Outgoing Policies and the Incoming
>>Policies.
>> > >Expanding each of those two bullets to explain what traffic is
>>subject
>> > >to each class of policies would help.
>> >
>> > [YL] Does this help?
>> >
>> > Outgoing Policies apply to packets originating from B4 to IPv4
>>network.
>> > Incoming Policies apply to packets originating from IPv4 network to
>>B4.
>> 
>> Yes, that's clearer, although the B4 is not the network endpoint for any
>> of that traffic.  I suggest:
>> 
>> Outgoing Policies apply to packets originating from behind the B4 with
>> a destination on the IPv4 network.
>> 
>> Incoming Policies apply to packets originating from the IPv4 network to
>> a destination behind the B4.
>> 
>> Thanks,
>> --David
>> 
>> 
>> > -----Original Message-----
>> > From: Lee, Yiu [mailto:Yiu_Lee@cable.comcast.com]
>> > Sent: Wednesday, October 17, 2012 8:46 PM
>> > To: Black, David; roberta.maglione@telecomitalia.it;
>>carlw@mcsr-labs.org;
>> > christian.jacquenet@orange.com; mohamed.boucadair@orange.com; gen-
>> art@ietf.org
>> > Cc: softwires@ietf.org; ietf@ietf.org; Ralph Droms
>> > Subject: Re: Gen-ART review of
>>draft-ietf-softwire-dslite-deployment-06
>> >
>> > Hi David,
>> >
>> > Thanks very much for review the draft. Comments inline.
>> >
>> > Thanks,
>> > Yiu
>> >
>> > On 10/15/12 7:10 PM, "Black, David" <david.black@emc.com> wrote:
>> >
>> > >I am the assigned Gen-ART reviewer for this draft. For background on
>> > >Gen-ART, please see the FAQ at
>> > ><http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>> > >
>> > >Please resolve these comments along with any other Last Call comments
>> > >you may receive.
>> > >
>> > >Document: draft-ietf-softwire-dslite-deployment-06
>> > >Reviewer: David L. Black
>> > >Review Date: October 15, 2012
>> > >IETF LC End Date: October 16, 2012
>> > >IESG Telechat Date: October 25, 2012
>> > >
>> > >Summary:
>> > >
>> > >This draft is on the right track but has open issues, described in
>>the
>> > >review.
>> > >
>> > >This is a generally well-written draft that expands considerably on
>>the
>> brief
>> > >deployment considerations for DS-Lite in Appendix A of RFC 6333.
>>The draft
>> > >is clear and reasonably well-written, and a significant improvement
>>on that
>> > >RFC 6333 Appendix, although an understanding of RFC 6333 is
>>necessary to
>> > >understand this draft, which seems completely reasonable.
>> > >
>> > >The B4 and AFTR acronyms are clever - kudos to whomever came up with
>> > >those.
>> > >
>> > >I found five open issues, all of which are minor.
>> > >
>> > >Minor Issues:
>> > >
>> > >[1] Ironically, the first issue is that something should be said
>>about
>> > >the relationship of this draft to Appendix A of RFC 6333.  It
>>probably
>> > >suffices to say that this draft expands on the material in that
>>Appendix,
>> > >as I see no need to specify that this draft updates RFC 6333 solely
>>to
>> > >change non-normative material in an Appendix.
>> >
>> > [YL] In "Overview", we will add:
>> >
>> > "This document expands Appendix A of RFC6333 and discusses various
>> > DS-Lite deployment considerations for operators."
>> >
>> > >
>> > >[2] The MTU increase technique in Section 2.2 is a "may", which is
>> > >consistent with Section 5.3 of RFC 6333.  OTOH, Section 2.2 of this
>> > >draft should also discuss the AFTR resource exhaustion concern that
>> > >described in Section 6.3 of RFC 6333, as that is a potential
>> > >operational reason for an ISP to increase MTU size (e.g., if customer
>> > >sourcing of large IPv4 packets is not sufficiently rare).
>> >
>> > [YL] In 2.2, we will add:
>> >
>> > "Note that reassembly at Tunnel Exit-Point is resource
>> >       intensive. A large number of B4 may terminate on the same AFTR.
>>If
>> many B4
>> >       fragment the packets, it would increase sufficient load to the
>>AFTR
>> for
>> >       reassembly. We recommend the operator should increase the MTU
>>size of
>> the IPv6
>> >       network between B4 and AFTR to avoid fragmentation."
>> >
>> > >
>> > >[3] Section 2.7 refers to "the AFTR's internal interface".  There
>>may be
>> > >two internal interfaces, the physical IPv6 interface (outer header)
>>and
>> > >the tunnel's IPv4 interface (inner header).  The text should be
>>clarified
>> > >to indicate which interface is involved - it appears that the AFTR's
>> > >physical IPv6 interface is intended in this section.
>> >
>> > [YL] We replace "internal" to "IPv6"
>> >
>> > >
>> > >[4] Section 2.7 cites RFC 6333 for use of DHCPv6 with DS-Lite.  RFC
>>6334
>> > >should be cited - either in addition to or instead of RFC 6333.
>> >
>> > [YL] Fixed
>> >
>> > >
>> > >[5] Section 2.8 discusses IPv4 accounting at the AFTR, but notes that
>> > >"the AFTR does not have detailed customer identity information."
>>Does
>> > >that create a theft of service possibility?  If so, that possibility
>> > >should be mentioned as a security consideration.  Also, Section 2.8
>> > >ought to be expanded with a sentence or two explaining why the AFTR
>> > >does not have that identity information, and in particular to explain
>> > >whether and why it is unreasonable in some or all cases to expect
>> > >that customer identity information be provided to the AFTR as part
>> > >of provisioning each customer's softwire.
>> >
>> > [YL] Good catch. Actually I believe AFTR "does" have both IPv4 and
>>IPv6 to
>> > identify the customer. I suggest we remove
>> >
>> > "but it will potentially introduce some additional complexity because
>> >    the AFTR does not have detailed customer identity information."
>> >
>> > >
>> > >Nits:
>> > >
>> > >Section 2.3 on MTU Considerations could usefully mention MTU
>>discovery
>> > >techniques, as possibilities for customer IPv4 traffic to adapt to a
>> > >smaller IPv4 MTU.  If this is done, it would be useful to mention
>> > >RFC 4821 in addition to the mention of RFC 1191 in RFC 6333.
>> >
>> > [YL] We would consider RFC 4821. However, the challenge is I don't
>>have
>> > information how many current OS support RFC 4821. Since DS-lite is a
>> > transition technology, it would be unreasonable to ask the OS company
>>to
>> > implement RFC 4821 for DS-lite.
>> >
>> > >
>> > >Section 2.4 should define "lawful intercept".  It would be helpful to
>> > >cite a reference for this concept if something appropriate can be
>>found.
>> >
>> > [YL] We will find whether there is any reference to this concept. If
>>we
>> > can't find any, we would add an explanation in the draft.
>> >
>> > >
>> > >Section 2.5:
>> > >- Are one or both types of logging recommended?
>> >
>> > [YL] We tempted to recommend source-specific log. However, some
>>regulators
>> > require to use both and the regulations vary country from country,
>>this is
>> > why we left it open and let the operators to decide.
>> >
>> > >- Last paragraph on p.4, "timestamped log" is not a good verb phrase.
>> > >     "maintain a timestamped log of" would be a better replacement.
>> >
>> > [YL] Fixed
>> >
>> > >- Last paragraph in section, where is the batch file sent?
>> >
>> > [YL] We will add:
>> >
>> > "The files may be compressed before transferring to a repository
>>server
>> >       to better utilize bandwidth and storage."
>> >
>> >
>> > >
>> > >In Section 2.7, I'm having a hard time understanding which traffic is
>> > >intended to be subject to the Outgoing Policies and the Incoming
>>Policies.
>> > >Expanding each of those two bullets to explain what traffic is
>>subject
>> > >to each class of policies would help.
>> >
>> > [YL] Does this help?
>> >
>> > Outgoing Policies apply to packets originating from B4 to IPv4
>>network.
>> > Incoming Policies apply to packets originating from IPv4 network to
>>B4.
>> >
>> >
>> >
>> > >
>> > >Section 3.2.2.2 uses 192.0.0.2/32 as an example IP address for the
>> > >B4.  That section should also cross-reference Section 5.7 on RFC 6333
>> > >on IP address assignment to B4s, as other IP addresses may be used.
>> >
>> > [YL] Added the cite.
>> >
>> > >
>> > >idnits 2.12.13 found a tiny nit - draft-ietf-pcp-base is now at
>> > >version 28.
>> >
>> > [YL] Fixed.
>> >
>> > >
>> > >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
>> > >----------------------------------------------------
>> > >
>> > >
>> 
>> Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle
>> persone indicate. La diffusione, copia o qualsiasi altra azione
>>derivante
>> dalla conoscenza di queste informazioni sono rigorosamente vietate.
>>Qualora
>> abbiate ricevuto questo documento per errore siete cortesemente pregati
>>di
>> darne 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,
>> printing or use by anybody else is unauthorised. If you are not the
>>intended
>> recipient, please delete this message and any attachments and advise the
>> sender by return e-mail, Thanks.
>> 
>

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

MIIVmQYJKoZIhvcNAQcCoIIVijCCFYYCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
EzEwggU0MIIEHKADAgECAhEAzuhISIgzOwSitfbc2LN4WDANBgkqhkiG9w0BAQUFADCBkzEL
MAkGA1UEBhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2Fs
Zm9yZDEaMBgGA1UEChMRQ09NT0RPIENBIExpbWl0ZWQxOTA3BgNVBAMTMENPTU9ETyBDbGll
bnQgQXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTAeFw0xMjA4MjgwMDAwMDBa
Fw0xMzA4MjgyMzU5NTlaMCoxKDAmBgkqhkiG9w0BCQEWGXlpdV9sZWVAY2FibGUuY29tY2Fz
dC5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCscOeu5/EoYRdja1jb6L4x
o0TIevelc17NsPuRHfr2z3BGUMbfsJY1p0uXO9+inBQoBXwb07ac3SbOjA/6Ef3NlMPItWdT
RGeFL6e/sMju9RgVyJURFnFgp7tc2tffnPOupnKZeeRehXeEFjun6+GC6teb1kSMu+WMMaCa
D7/XSK+Q+F0Udc2Av0/gUCkGfTDpNnYwutfctEMRnle6EYUqmJMN4C0crEfovmYdMFFgJLKs
Wa5Cdc+naFoIqzW8AcZB6+1XUDTzFbgjqgUbFFZFPzVZqNxLDFNy4tn8VlRSp2jBhgwQHtk1
ZA+spFENaeUuebp4tczj0IHG683FhhWjAgMBAAGjggHpMIIB5TAfBgNVHSMEGDAWgBR6E04A
dFvGeGNkJ8Ev4qBbvHnFezAdBgNVHQ4EFgQUz03csl7CmjwQY+spX9VWeGb5sVQwDgYDVR0P
AQH/BAQDAgWgMAwGA1UdEwEB/wQCMAAwIAYDVR0lBBkwFwYIKwYBBQUHAwQGCysGAQQBsjEB
AwUCMBEGCWCGSAGG+EIBAQQEAwIFIDBGBgNVHSAEPzA9MDsGDCsGAQQBsjEBAgEBATArMCkG
CCsGAQUFBwIBFh1odHRwczovL3NlY3VyZS5jb21vZG8ubmV0L0NQUzBXBgNVHR8EUDBOMEyg
SqBIhkZodHRwOi8vY3JsLmNvbW9kb2NhLmNvbS9DT01PRE9DbGllbnRBdXRoZW50aWNhdGlv
bmFuZFNlY3VyZUVtYWlsQ0EuY3JsMIGIBggrBgEFBQcBAQR8MHowUgYIKwYBBQUHMAKGRmh0
dHA6Ly9jcnQuY29tb2RvY2EuY29tL0NPTU9ET0NsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2Vj
dXJlRW1haWxDQS5jcnQwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLmNvbW9kb2NhLmNvbTAk
BgNVHREEHTAbgRl5aXVfbGVlQGNhYmxlLmNvbWNhc3QuY29tMA0GCSqGSIb3DQEBBQUAA4IB
AQBG7LORtWcmzDlw0N/D5AwfsSLe93essAqKFhJ+nt7SmMVBsxGzFnSsZGQHMYQ4UXtiVq9A
NjtPk00F3DC3QGxe4mxdwF9LzeYHpHMpCHTzNyilSimKZolLNBO+MO/U0u79rdF2W+dOAwkB
dzroWBxK+yMhijJn2DCE/1pgxqBz+c9zbAtJYPVpgbeGNvvfIp6CA/JYsupQNqPX49a4MdJ3
L9yXLTiegSE8uPUlCB3sHZclQOXAttuMewpcKDoIC4wZgERKQqRH61PQO100GLKUO+VrTq+f
xNkjOAqA+dih6QO5Djbv3qcMTCcAChJQYK8BS7jved8XgEVa0Ihz7oWKMIIFGjCCBAKgAwIB
AgIQbRnqpxlPajMi5iIyeqpx3jANBgkqhkiG9w0BAQUFADCBrjELMAkGA1UEBhMCVVMxCzAJ
BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJU
UlVTVCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNV
BAMTLVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbDAeFw0x
MTA0MjgwMDAwMDBaFw0yMDA1MzAxMDQ4MzhaMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMS
R3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8g
Q0EgTGltaXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQg
U2VjdXJlIEVtYWlsIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAkoSEW0tX
mNReL4uk4UDIo1NYX2Zl8TJO958yfVXQeExVt0KU4PkncQfFxmmkuTLE8UAakMwnVmJ/F7Vx
aa7lIBvky2NeYMqiQfZq4aP/uN8fSG1lQ4wqLitjOHffsReswtqCAtbUMmrUZ28gE49cNfrl
VICv2HEKHTcKAlBTbJUdqRAUtJmVWRIx/wmi0kzcUtve4kABW0ho3cVKtODtJB86r3FfB+Os
vxQ7sCVxaD30D9YXWEYVgTxoi4uDD216IVfmNLDbMn7jSuGlUnJkJpFOpZIP/+CxYP0ab2hR
mWONGoulzEKbm30iY9OpoPzOnpDfRBn0XFs1uhbzp5v/wQIDAQABo4IBSzCCAUcwHwYDVR0j
BBgwFoAUiYJnfcSdJnAAS7RQSHzePa4Ebn0wHQYDVR0OBBYEFHoTTgB0W8Z4Y2QnwS/ioFu8
ecV7MA4GA1UdDwEB/wQEAwIBBjASBgNVHRMBAf8ECDAGAQH/AgEAMBEGA1UdIAQKMAgwBgYE
VR0gADBYBgNVHR8EUTBPME2gS6BJhkdodHRwOi8vY3JsLnVzZXJ0cnVzdC5jb20vVVROLVVT
RVJGaXJzdC1DbGllbnRBdXRoZW50aWNhdGlvbmFuZEVtYWlsLmNybDB0BggrBgEFBQcBAQRo
MGYwPQYIKwYBBQUHMAKGMWh0dHA6Ly9jcnQudXNlcnRydXN0LmNvbS9VVE5BZGRUcnVzdENs
aWVudF9DQS5jcnQwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVzZXJ0cnVzdC5jb20wDQYJ
KoZIhvcNAQEFBQADggEBAIXWvnhXVW0zf0RS/kLVBqgBA4CK+w2y/Uq/9q9BSfUbWsXSrRtz
bj7pJnzmTJjBMCjfy/tCPKElPgp11tA9OYZm0aGbtU2bb68obB2v5ep0WqjascDxdXovnrqT
ecr+4pEeVnSy+I3T4ENyG+2P/WA5IEf7i686ZUg8mD2lJb+972DgSeUWyOs/Q4Pw4O4NwdPN
M1+b0L1garM7/vrUyTo8H+2b/5tJM75CKTmD7jNpLoKdRU2oadqAGx490hpdfEeZpZsIbRKZ
htZdVwcbpzC+S0lEuJB+ytF5OOu0M/qgOl0mWJ5hVRi0IdWZ1eBDQEIwvuql55TSsP7zdfl/
bucwggSdMIIDhaADAgECAhA0PekrrCc0/4/LNJT7zHBUMA0GCSqGSIb3DQEBBQUAMG8xCzAJ
BgNVBAYTAlNFMRQwEgYDVQQKEwtBZGRUcnVzdCBBQjEmMCQGA1UECxMdQWRkVHJ1c3QgRXh0
ZXJuYWwgVFRQIE5ldHdvcmsxIjAgBgNVBAMTGUFkZFRydXN0IEV4dGVybmFsIENBIFJvb3Qw
HhcNMDUwNjA3MDgwOTEwWhcNMjAwNTMwMTA0ODM4WjCBrjELMAkGA1UEBhMCVVMxCzAJBgNV
BAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT
VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMT
LVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbDCCASIwDQYJ
KoZIhvcNAQEBBQADggEPADCCAQoCggEBALI5haTyfatBO2JGN67NwWB1vDll+UoaR6K5zEjM
apjVTTUZuaRC5c5J4oovHnzSMQfHTrSDZJ0uKdWiZMSFvYVRNXmkTmiQexx6pJKoF/KYFfKT
zMmkMpW7DE8wvZigC4vlbhuiRvp4vKJvq1lepS/Pytptqi/rrKGzaqq3Lmc1i3nhHmmI4uZG
zaCl6r4LznY6eg6b6vzaJ1s9cx8i5khhxkzzabGoLhu21DEgLLyCio6kDqXXiUP8FlqvHXHX
EVnauocNr/rz4cLwpMVnjNbWVDreCqS6A3ezZcj9HtN0YqoYymiTHqGFfvVHZcv4TVcodNI0
/zC27vZiMBSMLOsCAwEAAaOB9DCB8TAfBgNVHSMEGDAWgBStvZh6NLQm9/rEJlTvA73gJMtU
GjAdBgNVHQ4EFgQUiYJnfcSdJnAAS7RQSHzePa4Ebn0wDgYDVR0PAQH/BAQDAgEGMA8GA1Ud
EwEB/wQFMAMBAf8wEQYDVR0gBAowCDAGBgRVHSAAMEQGA1UdHwQ9MDswOaA3oDWGM2h0dHA6
Ly9jcmwudXNlcnRydXN0LmNvbS9BZGRUcnVzdEV4dGVybmFsQ0FSb290LmNybDA1BggrBgEF
BQcBAQQpMCcwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVzZXJ0cnVzdC5jb20wDQYJKoZI
hvcNAQEFBQADggEBAAG8nONjKLDzMQHC33vdYqABnSMxD5ySc1NR6h9M+tafxMovZ354Mw90
FrmRh5H1iib6ZHAA2B75CwRiUIeTgdTa9SPbNLuFVrRwNG54gzcehRzFERWSX4cXvaxq/fHC
0cyJX7F88D5R8jXzfOxgmGs6K+Dv37N9huu1G/Vb7KJ8mBPXAFC50S1z3gN4dOEFhTFey5q5
nZTGuZQ3dXLcRPtn6PD6JR5Sp9ol6UfgoMc8oE6xCjb7d0if75eK+7T+45QUqIO8XC0/0mBx
YO7CcYIM6Yg249ogtKOgbKqWS7iAjnXKSQf2OxS639wF2Z/b4LLmTaB4JufnLW5/X8YeiBUw
ggQ2MIIDHqADAgECAgEBMA0GCSqGSIb3DQEBBQUAMG8xCzAJBgNVBAYTAlNFMRQwEgYDVQQK
EwtBZGRUcnVzdCBBQjEmMCQGA1UECxMdQWRkVHJ1c3QgRXh0ZXJuYWwgVFRQIE5ldHdvcmsx
IjAgBgNVBAMTGUFkZFRydXN0IEV4dGVybmFsIENBIFJvb3QwHhcNMDAwNTMwMTA0ODM4WhcN
MjAwNTMwMTA0ODM4WjBvMQswCQYDVQQGEwJTRTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAk
BgNVBAsTHUFkZFRydXN0IEV4dGVybmFsIFRUUCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVz
dCBFeHRlcm5hbCBDQSBSb290MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAt/ca
M+byAAQtOeBOW+0fvGwPzbX6I7bO3psRM5ekKUx9k5+9SryT7QMa44/P5W1QWtaXKZRagLBJ
etsulf24yr83OC0ePpFBrXBWx/BPP+gynnTKyJBU6cZfD3idmkA8Dqxhql4Uj56HoWpQ3Nea
Tq8Fs6ZxlJxxs1BgCscTnTgHhgKo6ahpJhiQq0ywTyOrOk+E2N/On+Fpb7vXQtdrROTHre5t
QV9yWnEIN7N5ZaRZoJQ39wAvDcKSctrQOHLbFKhFxF0qfbe01sTurM0TRLfJK91DACX6Yblp
algjEbenM49WdVn1zSnXRrcKK2W200JvFbK4e/vv6V1T1TRaJwIDAQABo4HcMIHZMB0GA1Ud
DgQWBBStvZh6NLQm9/rEJlTvA73gJMtUGjALBgNVHQ8EBAMCAQYwDwYDVR0TAQH/BAUwAwEB
/zCBmQYDVR0jBIGRMIGOgBStvZh6NLQm9/rEJlTvA73gJMtUGqFzpHEwbzELMAkGA1UEBhMC
U0UxFDASBgNVBAoTC0FkZFRydXN0IEFCMSYwJAYDVQQLEx1BZGRUcnVzdCBFeHRlcm5hbCBU
VFAgTmV0d29yazEiMCAGA1UEAxMZQWRkVHJ1c3QgRXh0ZXJuYWwgQ0EgUm9vdIIBATANBgkq
hkiG9w0BAQUFAAOCAQEAsJvghSXC1iPiD5YGkp1BmJzZhHmB2R5bFAcjNmWPsNh3u6xBbEdg
g1Gw+TI95/z2JhPHgBalv1r8h894eYkhmuJMBwqGNbzy3lHE0pa33H5O7nD9HDnrDAJRFC2O
vRbgwd9Gdeckrez0QrSFk3AQZ7qdBjVKGNMresxRQqF6Y9Hmu6HFK8I2vhMN5r1jfnl7pwkN
QKtq3Y+Kw/b2jBpCBVHURfWfp2IhaBUgQzyZ53y9JNipkRdziD9WGzE4GLRxD5rNyA6eji4b
4YyYg8sfMfFETMYEc0l2YA/H+L0XgGsu6cxMDlqaeQ8gCi7VnmMmHlWSlNiCF1p70LzHj06G
BDGCAjAwggIsAgEBMIGpMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5j
aGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDE5
MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWls
IENBAhEAzuhISIgzOwSitfbc2LN4WDAJBgUrDgMCGgUAoF0wIwYJKoZIhvcNAQkEMRYEFNoM
whBKIizmmTG/9AzcgFLwBsVXMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcN
AQkFMQ8XDTEyMTAyMjE5NDgyNFowDQYJKoZIhvcNAQEBBQAEggEARbs9yc3vlTSt3Hg4SW1m
Q1PZBTL88g0YvOmTRdFFeqiYEQUqHoL8R+BqdeqKasvA2TZZJw2xCfT35k1jnpaeTcmSQLLP
zosG36feCIryV8SQ7l5+2SIPHhuioCIpQX9xTN2Ibb8DN4fJbncan1DqcxCHDHpw5XEAVDCr
uDf3Gx0uTXOh5Hi2q2ilXCkxSqSNi4nPWPBdCQQ3vVJLjYPUC8M8w2tGffYARWzKTgAo1mcm
aoTk8pqDXevTCT4YS6B5/INzJ0Qeh8FsDxVgKT9z0KBRyGBR3Z9fpmPBiSSZtg66FPPEnlFg
FVxVftRUdmw2nSCgGBDPeJOTUwwlwMjVcg==

--B_3433765705_1570563--

From chuck.lever@oracle.com  Mon Oct 22 13:10:25 2012
Return-Path: <chuck.lever@oracle.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 CE4C221F88EE; Mon, 22 Oct 2012 13:10:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.872
X-Spam-Level: 
X-Spam-Status: No, score=-8.872 tagged_above=-999 required=5 tests=[AWL=-0.574, BAYES_00=-2.599, MANGLED_LIST=2.3, RCVD_IN_DNSWL_HI=-8, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1Pav7CmHv+3I; Mon, 22 Oct 2012 13:10:25 -0700 (PDT)
Received: from rcsinet15.oracle.com (rcsinet15.oracle.com [148.87.113.117]) by ietfa.amsl.com (Postfix) with ESMTP id 0B3CE21F88EC; Mon, 22 Oct 2012 13:10:24 -0700 (PDT)
Received: from acsinet22.oracle.com (acsinet22.oracle.com [141.146.126.238]) by rcsinet15.oracle.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id q9MKAHZx004216 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 22 Oct 2012 20:10:18 GMT
Received: from acsmt357.oracle.com (acsmt357.oracle.com [141.146.40.157]) by acsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id q9MKAHeL015793 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Oct 2012 20:10:17 GMT
Received: from abhmt112.oracle.com (abhmt112.oracle.com [141.146.116.64]) by acsmt357.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id q9MKAGMQ030301; Mon, 22 Oct 2012 15:10:16 -0500
Received: from moret.1015granger.net (/99.26.161.222) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 22 Oct 2012 13:10:16 -0700
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Chuck Lever <chuck.lever@oracle.com>
In-Reply-To: <CCAA0CA5.11A5%peter@akayla.com>
Date: Mon, 22 Oct 2012 16:10:16 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F9C49DE0-5BB3-4714-96A7-96EA7DA94DF7@oracle.com>
References: <CCAA0CA5.11A5%peter@akayla.com>
To: Peter Yee <peter@akayla.com>
X-Mailer: Apple Mail (2.1499)
X-Source-IP: acsinet22.oracle.com [141.146.126.238]
Cc: gen-art@ietf.org, "ietf@ietf.org" <ietf@ietf.org>, draft-ietf-nfsv4-federated-fs-protocol.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-nfsv4-federated-fs-protocol-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, 22 Oct 2012 20:10:25 -0000

On Oct 21, 2012, at 11:35 PM, Peter Yee <peter@akayla.com> wrote:

> Chuck,
> 	Ranges include the 0,255 that appears commonly in the document =
in
> attribute definitions along with one case of -2147483648,2147483647.

Hi Peter-

Upon further review, I see the document uses "interval notation" when =
defining ranges of allowed values in attributes.  The use of square =
brackets denotes inclusivity.  If you feel readers need more, or our use =
of this notation is inconsistent, I'm happy to add clarification.

> 	Kind regards,
> 		-Peter
>=20
> On 10/21/12 3:27 PM, "Chuck Lever" <chuck.lever@oracle.com> wrote:
>=20
>>=20
>> On Oct 21, 2012, at 5:39 PM, Peter Yee <peter@akayla.com> wrote:
>>=20
>>> I am the assigned Gen-ART reviewer for this draft. For background on
>>> Gen-ART, please see the FAQ at
>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>>>=20
>>> Document: draft-ietf-nfsv4-federated-fs-protocol-13
>>> Reviewer: Peter Yee
>>> Review Date: Oct-19-2012
>>> IETF LC End Date: Oct-22-2012
>>> IESG Telechat date: TBD
>>>=20
>>>=20
>>> Summary: This draft is basically ready for publication, but has nits
>>> that
>>> should be fixed before publication. [Ready with nits.]
>>>=20
>>>=20
>>> This Standards Track document describes a protocol for maintaining a
>>> Namespace Database for use with federated filesystem protocols.  The
>>> document is well-written with good examples and little need to jump =
back
>>> and forth in the text to understand it.
>>>=20
>>> General: Are ranges (in attribute values) inclusive or exclusive?  =
They
>>> appear to be inclusive, but it might be worth saying that somewhere, =
if
>>> only once.
>>=20
>> Can you give me an example of a range that might need clarification?
>>=20
>> I will address these comments and co-ordinate draft updates with our =
WG
>> editor, Tom Haynes.
>>=20
>> Thanks for your review.
>>=20
>>> Section 2.7, NsdbName definition: expand NSDB to Namespace Database =
as
>>> this is the first use of the term.
>>>=20
>>> Section 2.8.1, 2nd sentence: "extention" -> "extension"
>>>=20
>>> Section 2.8.3, 2nd paragraph, last sentence: in addition to checking =
for
>>> added FSL records, shouldn't the fileserver also be checking for =
deleted
>>> or migrated FSLs?  And why would the fileserver do this at the
>>> expiration
>>> of the FSN TTL instead of waiting for the next access to the that =
FSN?
>>> Otherwise the fileserver could be generating unnecessary traffic,
>>> although
>>> there is a tradeoff to be made vs. performance.
>>>=20
>>> Section 2.8.3, 3rd paragraph after bullet items, 1st sentence: =
"which"
>>> ->
>>> "that".  (Yeah, I know, grammar police.)
>>>=20
>>> Section 2.9, 3rd paragraph, 2nd sentence: "admininistrative" ->
>>> "administrative"
>>>=20
>>> Section 2.12, 2nd paragraph, last sentence: expand NCE (NSDB =
Container
>>> Entry) as this is the first use of the term.
>>>=20
>>> Section 3.2, item #5: "fs_location" -> "fs_locations"
>>>=20
>>> Section 4.1, 1st paragraph, 3rd sentence: probably worth expanding =
"DSE"
>>> to "DSA-specific entry" here.
>>>=20
>>> Section 4.2.1.8, 1st paragraph, 2nd sentence: bracket "Section =
2.8.1" in
>>> "(see" and ")" for readability.
>>>=20
>>> Section 4.2.2: "LDAP Objects" -> "LDAP Object Classes" seems
>>> appropriate.
>>>=20
>>> Section 4.2.2.1, 2nd and 3rd sentences: replace "fedfsFsn" with
>>> "fedfsNsdbContainerInfo"
>>>=20
>>> Section 4.2.2.2, 5th paragraph: how is the prohibition on =
referencing
>>> other attributes in the fedfsFsn object class supposed to work if =
this
>>> document is the defining document for that object class?
>>>=20
>>> Section 5.1.3.1, 1st paragraph after LDIF definition: a port number =
of
>>> 2049 is given.  Since this is already the default value, why not use =
a
>>> different value?  Otherwise, there would be no practical need to =
include
>>> that port number in the FSL creation request.
>>>=20
>>> Section 5.1.3.1, 1st paragraph after LDIF definition: "up to date" =
->
>>> "up-to-date"
>>>=20
>>> Section 5.1.3.2, 2nd paragraph: "a" -> "an"
>>>=20
>>> Section 5.1.3.2, table entry for "fedfsNfsVarSub": "substituion" ->
>>> "substitution"
>>>=20
>>> Section 5.1.4, 1st paragraph, 1st sentence: "a Fileset location" -> =
"an
>>> FSL"
>>>=20
>>> Section 7.3, 2nd paragraph, "Specification" value: presumably this =
will
>>> be
>>> changed to the RFC number when issued?
>>>=20
>>> Section 8, 1st paragraph (definition of Administrator): "an" -> "a"
>>>=20
>>> Section 8, 3rd paragraph (definition of Client): "filesystem access" =
->
>>> "file-access" for consistency of usage with the rest of the =
document.
>>>=20
>>> Section 8, 5th paragraph (definition of Fileserver): rather than
>>> discussing "a filesystem", should this be "one or more filesystems"? =
 Or
>>> is a fileserver limited to exporting one filesystem?
>>>=20
>>> Section 8, 8th paragraph (definition of Filesystem Access Protocol):
>>> following up on the 3rd paragraph, should this be "File-access =
Protocol"
>>> for consistency?
>>>=20
>>> Section 8, 9th paragraph (definition of FSL), 2nd sentence:
>>> "fs_location"
>>> -> "fs_locations".
>>>=20
>>>=20
>>>=20
>>=20
>> --=20
>> Chuck Lever
>> chuck[dot]lever[at]oracle[dot]com
>>=20
>>=20
>>=20
>>=20
>>=20
>=20
> <default[4].xml>

--=20
Chuck Lever
chuck[dot]lever[at]oracle[dot]com





From david.black@emc.com  Mon Oct 22 13:45:35 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 595781F042B for <gen-art@ietfa.amsl.com>; Mon, 22 Oct 2012 13:45:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.608
X-Spam-Level: 
X-Spam-Status: No, score=-102.608 tagged_above=-999 required=5 tests=[AWL=-0.009, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 80-LRtyEmc1C for <gen-art@ietfa.amsl.com>; Mon, 22 Oct 2012 13:45:33 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id B00541F0429 for <gen-art@ietf.org>; Mon, 22 Oct 2012 13:45:33 -0700 (PDT)
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 q9MKjRwH017473 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Oct 2012 16:45:29 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.130]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Mon, 22 Oct 2012 16:45:12 -0400
Received: from mxhub07.corp.emc.com (mxhub07.corp.emc.com [128.222.70.204]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q9MKjBrQ009629; Mon, 22 Oct 2012 16:45:11 -0400
Received: from mx15a.corp.emc.com ([169.254.1.83]) by mxhub07.corp.emc.com ([128.222.70.204]) with mapi; Mon, 22 Oct 2012 16:45:11 -0400
From: "Black, David" <david.black@emc.com>
To: "Lee, Yiu" <Yiu_Lee@cable.comcast.com>, Maglione Roberta <roberta.maglione@telecomitalia.it>, "'draft-ietf-softwire-dslite-deployment@tools.ietf.org'" <draft-ietf-softwire-dslite-deployment@tools.ietf.org>
Date: Mon, 22 Oct 2012 16:45:10 -0400
Thread-Topic: Gen-ART review of draft-ietf-softwire-dslite-deployment-06
Thread-Index: AQHNsI4zRZf3m76IaEG1JdT7FnudgpfFxPyA
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7120E04AC0D@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE7120DFAF49C@MX15A.corp.emc.com> <E3FAB1F4F41F3A45B287E8D9C53522FD37A8513C@PACDCEXMB05.cable.comcast.com>
In-Reply-To: <E3FAB1F4F41F3A45B287E8D9C53522FD37A8513C@PACDCEXMB05.cable.comcast.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: "gen-art@ietf.org" <gen-art@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>, "softwire-chairs@tools.ietf.org" <softwire-chairs@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-softwire-dslite-deployment-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: Mon, 22 Oct 2012 20:45:35 -0000

Hi Yiu,

> Since the BNG would verify the v6 packets sent by B4 and the AFTR would
> NAT the RFC1918 source address to the public address, I try to find a use
> case where a theft could steal the service.

Important clarification - I did not originally assert that there is a
theft of service possibility, rather I only asked whether there is one -
"Does that create a theft of service possibility?".

If the answer is "no", then an explanation of why that is the answer
ought to suffice.  Here's the draft's text on this topic:

   Alternatively, AFTR is a logical place to perform IPv4 accounting,
   but it will potentially introduce some additional complexity because
   the AFTR does not have detailed customer identity information.  The
   accounting process at the AFTR is only necessary if the operator
   requires separating per user accounting records for IPv4 and IPv6
   traffic.

Continuing:

> From the AFTR's perspective,
> the IPv4 address of the host behind B4 is irrelevant. Could you help to
> find a use case which will introduce security risk because the AFTR can't
> identify the IPv4 address?

In revising the draft, please also explain how "the operator requires
separating per user accounting records for IPv4 and IPv6 traffic" is
consistent with "the IPv4 address of the host behind the B4 is irrelevant".
The answer probably starts with an explanation of the behavior of the
NAT in the AFTR, although I note that section 2.13 of the draft describes
a case in which the IPv4 address behind the B4 appears to be relevant
(e.g., for an operator who charges differently for traffic inbound to
a customer server by comparison to other customer traffic).

Backing out of this level of detail, all I'm asking for is an explanation
of why or under what circumstances the lack of identity information at
the AFTR does not pose a security concern when usage accounting is done
there and the assumptions on which that is based - e.g., it might be
appropriate to say that the BNG should verify the v6 packets sent by B4.

I'm not trying to be difficult.  In general, absence of identity informatio=
n
raises theft of service concerns in accounting systems, and if that's reall=
y
not a problem in this case, I just want to see a solid explanation of why
that's not a problem.

Thanks,
--David


> -----Original Message-----
> From: Lee, Yiu [mailto:Yiu_Lee@cable.comcast.com]
> Sent: Monday, October 22, 2012 3:48 PM
> To: Black, David; Maglione Roberta; 'draft-ietf-softwire-dslite-
> deployment@tools.ietf.org'
> Cc: Ralph Droms; gen-art@ietf.org; softwire-chairs@tools.ietf.org
> Subject: Re: Gen-ART review of draft-ietf-softwire-dslite-deployment-06
>
> Hi David,
>
> Since the BNG would verify the v6 packets sent by B4 and the AFTR would
> NAT the RFC1918 source address to the public address, I try to find a use
> case where a theft could steal the service. From the AFTR's perspective,
> the IPv4 address of the host behind B4 is irrelevant. Could you help to
> find a use case which will introduce security risk because the AFTR can't
> identify the IPv4 address?
>
> Thanks,
> Yiu
>
> On 10/18/12 11:10 AM, "Black, David" <david.black@emc.com> wrote:
>
> >Hello Roberta,
> >
> >In that case, more text is needed to explain in Section 2.8, and
> >the related theft of service concern also needs to be discussed in
> >that section and/or the Security Considerations section.
> >
> >Thanks,
> >--David
> >
> >> -----Original Message-----
> >> From: Maglione Roberta [mailto:roberta.maglione@telecomitalia.it]
> >> Sent: Thursday, October 18, 2012 3:18 AM
> >> To: Black, David; Lee, Yiu; 'draft-ietf-softwire-dslite-
> >> deployment@tools.ietf.org'
> >> Cc: Ralph Droms; gen-art@ietf.org; softwire-chairs@tools.ietf.org
> >> Subject: RE: Gen-ART review of draft-ietf-softwire-dslite-deployment-0=
6
> >>
> >> Hello Yiu and David,
> >> regarding point 5:
> >>
> >> > [YL] Good catch. Actually I believe AFTR "does" have both IPv4 and
> >> > IPv6 to identify the customer. I suggest we remove
> >> >
> >> > "but it will potentially introduce some additional complexity becaus=
e
> >> >    the AFTR does not have detailed customer identity information."
> >>
> >> The point related to the accounting is different: what I meant here wi=
th
> >> accounting is RADIUS based accounting, commonly used in Broadband netw=
orks.
> >>
> >> Today RADIUS accounting is done at the BNG level, the problem with the
> >> introduction of the AFTR is that the AFTR does not interact with AAA/R=
ADIUS
> >> Server for the initial authentication/authorization/accounting phase b=
ecause
> >> the authentication/authorization/accounting process happens between BN=
G and
> >> RADIUS Server when the session comes up.
> >> The ATFR is not able to perform RADIUS accounting because as it does n=
ot
> >> interact with the RADIUS Server it does not have " detailed customer i=
dentity
> >> information" for example it does know the accounting session ID associ=
ated to
> >> that session, that's why it cannot do detailed accounting for each sin=
gle
> >> subscriber even if the ATFR can still correlated IPv6 and IPv4 traffic
> >> belonging to the same user.
> >>
> >> This is an important operational issue, I would suggest to keep this c=
oncept.
> >> If you think is needed I can add some lines of text in order to clarif=
y this
> >> point.
> >>
> >> Thanks
> >> Regards,
> >> Roberta
> >>
> >> -----Original Message-----
> >> From: Black, David [mailto:david.black@emc.com]
> >> Sent: Thursday, October 18, 2012 3:12 AM
> >> To: Lee, Yiu; Maglione Roberta; carlw@mcsr-labs.org;
> >> christian.jacquenet@orange.com; mohamed.boucadair@orange.com;
> >>gen-art@ietf.org
> >> Cc: softwires@ietf.org; ietf@ietf.org; Ralph Droms; Black, David
> >> Subject: RE: Gen-ART review of draft-ietf-softwire-dslite-deployment-0=
6
> >>
> >> Yiu,
> >>
> >> Thank you for your responses - most of them look fine, and in
> >> particular anything that I don't comment on here is acceptable to me.
> >>
> >> > [YL] In 2.2, we will add:
> >> >
> >> > "Note that reassembly at Tunnel Exit-Point is resource
> >> >       intensive. A large number of B4 may terminate on the same AFTR=
. If many B4
> >> >       fragment the packets, it would increase sufficient load to the=
 AFTR for
> >> >       reassembly. We recommend the operator should increase the MTU =
size of the IPv6
> >> >       network between B4 and AFTR to avoid fragmentation."
> >>
> >> I would change "is" to "may be" in the first line.
> >>
> >> > >[5] Section 2.8 discusses IPv4 accounting at the AFTR, but notes th=
at
> >> > >"the AFTR does not have detailed customer identity information." Do=
es
> >> > >that create a theft of service possibility?  If so, that possibilit=
y
> >> > >should be mentioned as a security consideration.  Also, Section 2.8
> >> > >ought to be expanded with a sentence or two explaining why the AFTR
> >> > >does not have that identity information, and in particular to expla=
in
> >> > >whether and why it is unreasonable in some or all cases to expect
> >> > >that customer identity information be provided to the AFTR as part
> >> > >of provisioning each customer's softwire.
> >> >
> >> > [YL] Good catch. Actually I believe AFTR "does" have both IPv4 and
> >>IPv6 to
> >> > identify the customer. I suggest we remove
> >> >
> >> > "but it will potentially introduce some additional complexity becaus=
e
> >> >    the AFTR does not have detailed customer identity information."
> >>
> >> That's definitely an easy way to address that issue, and it's fine wit=
h
> >>me.
> >>
> >> > >Section 2.3 on MTU Considerations could usefully mention MTU
> >>discovery
> >> > >techniques, as possibilities for customer IPv4 traffic to adapt to =
a
> >> > >smaller IPv4 MTU.  If this is done, it would be useful to mention
> >> > >RFC 4821 in addition to the mention of RFC 1191 in RFC 6333.
> >> >
> >> > [YL] We would consider RFC 4821. However, the challenge is I don't
> >>have
> >> > information how many current OS support RFC 4821. Since DS-lite is a
> >> > transition technology, it would be unreasonable to ask the OS compan=
y
> >>to
> >> > implement RFC 4821 for DS-lite.
> >>
> >> That's ok - this was a nit.
> >>
> >> > >- Are one or both types of logging recommended?
> >> >
> >> > [YL] We tempted to recommend source-specific log. However, some
> >>regulators
> >> > require to use both and the regulations vary country from country,
> >>this is
> >> > why we left it open and let the operators to decide.
> >>
> >> Please add a version of your explanation to the draft.
> >>
> >> > >In Section 2.7, I'm having a hard time understanding which traffic =
is
> >> > >intended to be subject to the Outgoing Policies and the Incoming
> >>Policies.
> >> > >Expanding each of those two bullets to explain what traffic is
> >>subject
> >> > >to each class of policies would help.
> >> >
> >> > [YL] Does this help?
> >> >
> >> > Outgoing Policies apply to packets originating from B4 to IPv4
> >>network.
> >> > Incoming Policies apply to packets originating from IPv4 network to
> >>B4.
> >>
> >> Yes, that's clearer, although the B4 is not the network endpoint for a=
ny
> >> of that traffic.  I suggest:
> >>
> >> Outgoing Policies apply to packets originating from behind the B4 with
> >> a destination on the IPv4 network.
> >>
> >> Incoming Policies apply to packets originating from the IPv4 network t=
o
> >> a destination behind the B4.
> >>
> >> Thanks,
> >> --David
> >>
> >>
> >> > -----Original Message-----
> >> > From: Lee, Yiu [mailto:Yiu_Lee@cable.comcast.com]
> >> > Sent: Wednesday, October 17, 2012 8:46 PM
> >> > To: Black, David; roberta.maglione@telecomitalia.it;
> >>carlw@mcsr-labs.org;
> >> > christian.jacquenet@orange.com; mohamed.boucadair@orange.com; gen-
> >> art@ietf.org
> >> > Cc: softwires@ietf.org; ietf@ietf.org; Ralph Droms
> >> > Subject: Re: Gen-ART review of
> >>draft-ietf-softwire-dslite-deployment-06
> >> >
> >> > Hi David,
> >> >
> >> > Thanks very much for review the draft. Comments inline.
> >> >
> >> > Thanks,
> >> > Yiu
> >> >
> >> > On 10/15/12 7:10 PM, "Black, David" <david.black@emc.com> wrote:
> >> >
> >> > >I am the assigned Gen-ART reviewer for this draft. For background o=
n
> >> > >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 commen=
ts
> >> > >you may receive.
> >> > >
> >> > >Document: draft-ietf-softwire-dslite-deployment-06
> >> > >Reviewer: David L. Black
> >> > >Review Date: October 15, 2012
> >> > >IETF LC End Date: October 16, 2012
> >> > >IESG Telechat Date: October 25, 2012
> >> > >
> >> > >Summary:
> >> > >
> >> > >This draft is on the right track but has open issues, described in
> >>the
> >> > >review.
> >> > >
> >> > >This is a generally well-written draft that expands considerably on
> >>the
> >> brief
> >> > >deployment considerations for DS-Lite in Appendix A of RFC 6333.
> >>The draft
> >> > >is clear and reasonably well-written, and a significant improvement
> >>on that
> >> > >RFC 6333 Appendix, although an understanding of RFC 6333 is
> >>necessary to
> >> > >understand this draft, which seems completely reasonable.
> >> > >
> >> > >The B4 and AFTR acronyms are clever - kudos to whomever came up wit=
h
> >> > >those.
> >> > >
> >> > >I found five open issues, all of which are minor.
> >> > >
> >> > >Minor Issues:
> >> > >
> >> > >[1] Ironically, the first issue is that something should be said
> >>about
> >> > >the relationship of this draft to Appendix A of RFC 6333.  It
> >>probably
> >> > >suffices to say that this draft expands on the material in that
> >>Appendix,
> >> > >as I see no need to specify that this draft updates RFC 6333 solely
> >>to
> >> > >change non-normative material in an Appendix.
> >> >
> >> > [YL] In "Overview", we will add:
> >> >
> >> > "This document expands Appendix A of RFC6333 and discusses various
> >> > DS-Lite deployment considerations for operators."
> >> >
> >> > >
> >> > >[2] The MTU increase technique in Section 2.2 is a "may", which is
> >> > >consistent with Section 5.3 of RFC 6333.  OTOH, Section 2.2 of this
> >> > >draft should also discuss the AFTR resource exhaustion concern that
> >> > >described in Section 6.3 of RFC 6333, as that is a potential
> >> > >operational reason for an ISP to increase MTU size (e.g., if custom=
er
> >> > >sourcing of large IPv4 packets is not sufficiently rare).
> >> >
> >> > [YL] In 2.2, we will add:
> >> >
> >> > "Note that reassembly at Tunnel Exit-Point is resource
> >> >       intensive. A large number of B4 may terminate on the same AFTR=
.
> >>If
> >> many B4
> >> >       fragment the packets, it would increase sufficient load to the
> >>AFTR
> >> for
> >> >       reassembly. We recommend the operator should increase the MTU
> >>size of
> >> the IPv6
> >> >       network between B4 and AFTR to avoid fragmentation."
> >> >
> >> > >
> >> > >[3] Section 2.7 refers to "the AFTR's internal interface".  There
> >>may be
> >> > >two internal interfaces, the physical IPv6 interface (outer header)
> >>and
> >> > >the tunnel's IPv4 interface (inner header).  The text should be
> >>clarified
> >> > >to indicate which interface is involved - it appears that the AFTR'=
s
> >> > >physical IPv6 interface is intended in this section.
> >> >
> >> > [YL] We replace "internal" to "IPv6"
> >> >
> >> > >
> >> > >[4] Section 2.7 cites RFC 6333 for use of DHCPv6 with DS-Lite.  RFC
> >>6334
> >> > >should be cited - either in addition to or instead of RFC 6333.
> >> >
> >> > [YL] Fixed
> >> >
> >> > >
> >> > >[5] Section 2.8 discusses IPv4 accounting at the AFTR, but notes th=
at
> >> > >"the AFTR does not have detailed customer identity information."
> >>Does
> >> > >that create a theft of service possibility?  If so, that possibilit=
y
> >> > >should be mentioned as a security consideration.  Also, Section 2.8
> >> > >ought to be expanded with a sentence or two explaining why the AFTR
> >> > >does not have that identity information, and in particular to expla=
in
> >> > >whether and why it is unreasonable in some or all cases to expect
> >> > >that customer identity information be provided to the AFTR as part
> >> > >of provisioning each customer's softwire.
> >> >
> >> > [YL] Good catch. Actually I believe AFTR "does" have both IPv4 and
> >>IPv6 to
> >> > identify the customer. I suggest we remove
> >> >
> >> > "but it will potentially introduce some additional complexity becaus=
e
> >> >    the AFTR does not have detailed customer identity information."
> >> >
> >> > >
> >> > >Nits:
> >> > >
> >> > >Section 2.3 on MTU Considerations could usefully mention MTU
> >>discovery
> >> > >techniques, as possibilities for customer IPv4 traffic to adapt to =
a
> >> > >smaller IPv4 MTU.  If this is done, it would be useful to mention
> >> > >RFC 4821 in addition to the mention of RFC 1191 in RFC 6333.
> >> >
> >> > [YL] We would consider RFC 4821. However, the challenge is I don't
> >>have
> >> > information how many current OS support RFC 4821. Since DS-lite is a
> >> > transition technology, it would be unreasonable to ask the OS compan=
y
> >>to
> >> > implement RFC 4821 for DS-lite.
> >> >
> >> > >
> >> > >Section 2.4 should define "lawful intercept".  It would be helpful =
to
> >> > >cite a reference for this concept if something appropriate can be
> >>found.
> >> >
> >> > [YL] We will find whether there is any reference to this concept. If
> >>we
> >> > can't find any, we would add an explanation in the draft.
> >> >
> >> > >
> >> > >Section 2.5:
> >> > >- Are one or both types of logging recommended?
> >> >
> >> > [YL] We tempted to recommend source-specific log. However, some
> >>regulators
> >> > require to use both and the regulations vary country from country,
> >>this is
> >> > why we left it open and let the operators to decide.
> >> >
> >> > >- Last paragraph on p.4, "timestamped log" is not a good verb phras=
e.
> >> > >     "maintain a timestamped log of" would be a better replacement.
> >> >
> >> > [YL] Fixed
> >> >
> >> > >- Last paragraph in section, where is the batch file sent?
> >> >
> >> > [YL] We will add:
> >> >
> >> > "The files may be compressed before transferring to a repository
> >>server
> >> >       to better utilize bandwidth and storage."
> >> >
> >> >
> >> > >
> >> > >In Section 2.7, I'm having a hard time understanding which traffic =
is
> >> > >intended to be subject to the Outgoing Policies and the Incoming
> >>Policies.
> >> > >Expanding each of those two bullets to explain what traffic is
> >>subject
> >> > >to each class of policies would help.
> >> >
> >> > [YL] Does this help?
> >> >
> >> > Outgoing Policies apply to packets originating from B4 to IPv4
> >>network.
> >> > Incoming Policies apply to packets originating from IPv4 network to
> >>B4.
> >> >
> >> >
> >> >
> >> > >
> >> > >Section 3.2.2.2 uses 192.0.0.2/32 as an example IP address for the
> >> > >B4.  That section should also cross-reference Section 5.7 on RFC 63=
33
> >> > >on IP address assignment to B4s, as other IP addresses may be used.
> >> >
> >> > [YL] Added the cite.
> >> >
> >> > >
> >> > >idnits 2.12.13 found a tiny nit - draft-ietf-pcp-base is now at
> >> > >version 28.
> >> >
> >> > [YL] Fixed.
> >> >
> >> > >
> >> > >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
> >> > >----------------------------------------------------
> >> > >
> >> > >
> >>
> >> Questo messaggio e i suoi allegati sono indirizzati esclusivamente all=
e
> >> persone indicate. La diffusione, copia o qualsiasi altra azione
> >>derivante
> >> dalla conoscenza di queste informazioni sono rigorosamente vietate.
> >>Qualora
> >> abbiate ricevuto questo documento per errore siete cortesemente pregat=
i
> >>di
> >> darne 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=
,
> >> printing or use by anybody else is unauthorised. If you are not the
> >>intended
> >> recipient, please delete this message and any attachments and advise t=
he
> >> sender by return e-mail, Thanks.
> >>
> >

From yiu_lee@cable.comcast.com  Mon Oct 22 14:54:15 2012
Return-Path: <yiu_lee@cable.comcast.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 2468021F846B for <gen-art@ietfa.amsl.com>; Mon, 22 Oct 2012 14:54:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.225
X-Spam-Level: 
X-Spam-Status: No, score=-104.225 tagged_above=-999 required=5 tests=[AWL=1.006, BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8GEUm5BmgQZA for <gen-art@ietfa.amsl.com>; Mon, 22 Oct 2012 14:54:13 -0700 (PDT)
Received: from cable.comcast.com (copdcavout01.cable.comcast.com [76.96.32.253]) by ietfa.amsl.com (Postfix) with ESMTP id 56FB821F8460 for <gen-art@ietf.org>; Mon, 22 Oct 2012 14:54:13 -0700 (PDT)
Received: from ([24.40.56.114]) by copdcavout01.cable.comcast.com with ESMTP  id C7WM3M1.38725524; Mon, 22 Oct 2012 15:30:28 -0600
Received: from PACDCEXMB05.cable.comcast.com ([169.254.7.64]) by PACDCEXHUB01.cable.comcast.com ([fe80::84e8:95f3:f13b:169e%12]) with mapi id 14.02.0318.001; Mon, 22 Oct 2012 17:54:07 -0400
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: "Black, David" <david.black@emc.com>, Maglione Roberta <roberta.maglione@telecomitalia.it>, "'draft-ietf-softwire-dslite-deployment@tools.ietf.org'" <draft-ietf-softwire-dslite-deployment@tools.ietf.org>
Thread-Topic: Gen-ART review of draft-ietf-softwire-dslite-deployment-06
Thread-Index: AQHNsI4zRZf3m76IaEG1JdT7FnudgpfFxPyAgAAZaAA=
Date: Mon, 22 Oct 2012 21:54:06 +0000
Message-ID: <E3FAB1F4F41F3A45B287E8D9C53522FD37A8550E@PACDCEXMB05.cable.comcast.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7120E04AC0D@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.4.120824
x-originating-ip: [24.40.55.73]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3433773245_11682"
MIME-Version: 1.0
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>, "softwire-chairs@tools.ietf.org" <softwire-chairs@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-softwire-dslite-deployment-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: Mon, 22 Oct 2012 21:54:15 -0000

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

Hi David,

Got it. We will capture all these comments in the next revision.

Thanks again for reviewing the draft.

Yiu

On 10/22/12 4:45 PM, "Black, David" <david.black@emc.com> wrote:

>Hi Yiu,
>
>> Since the BNG would verify the v6 packets sent by B4 and the AFTR would
>> NAT the RFC1918 source address to the public address, I try to find a
>>use
>> case where a theft could steal the service.
>
>Important clarification - I did not originally assert that there is a
>theft of service possibility, rather I only asked whether there is one -
>"Does that create a theft of service possibility?".
>
>If the answer is "no", then an explanation of why that is the answer
>ought to suffice.  Here's the draft's text on this topic:
>
>   Alternatively, AFTR is a logical place to perform IPv4 accounting,
>   but it will potentially introduce some additional complexity because
>   the AFTR does not have detailed customer identity information.  The
>   accounting process at the AFTR is only necessary if the operator
>   requires separating per user accounting records for IPv4 and IPv6
>   traffic.
>
>Continuing:
>
>> From the AFTR's perspective,
>> the IPv4 address of the host behind B4 is irrelevant. Could you help to
>> find a use case which will introduce security risk because the AFTR
>>can't
>> identify the IPv4 address?
>
>In revising the draft, please also explain how "the operator requires
>separating per user accounting records for IPv4 and IPv6 traffic" is
>consistent with "the IPv4 address of the host behind the B4 is
>irrelevant".
>The answer probably starts with an explanation of the behavior of the
>NAT in the AFTR, although I note that section 2.13 of the draft describes
>a case in which the IPv4 address behind the B4 appears to be relevant
>(e.g., for an operator who charges differently for traffic inbound to
>a customer server by comparison to other customer traffic).
>
>Backing out of this level of detail, all I'm asking for is an explanation
>of why or under what circumstances the lack of identity information at
>the AFTR does not pose a security concern when usage accounting is done
>there and the assumptions on which that is based - e.g., it might be
>appropriate to say that the BNG should verify the v6 packets sent by B4.
>
>I'm not trying to be difficult.  In general, absence of identity
>information
>raises theft of service concerns in accounting systems, and if that's
>really
>not a problem in this case, I just want to see a solid explanation of why
>that's not a problem.
>
>Thanks,
>--David
>
>
>> -----Original Message-----
>> From: Lee, Yiu [mailto:Yiu_Lee@cable.comcast.com]
>> Sent: Monday, October 22, 2012 3:48 PM
>> To: Black, David; Maglione Roberta; 'draft-ietf-softwire-dslite-
>> deployment@tools.ietf.org'
>> Cc: Ralph Droms; gen-art@ietf.org; softwire-chairs@tools.ietf.org
>> Subject: Re: Gen-ART review of draft-ietf-softwire-dslite-deployment-06
>>
>> Hi David,
>>
>> Since the BNG would verify the v6 packets sent by B4 and the AFTR would
>> NAT the RFC1918 source address to the public address, I try to find a
>>use
>> case where a theft could steal the service. From the AFTR's perspective,
>> the IPv4 address of the host behind B4 is irrelevant. Could you help to
>> find a use case which will introduce security risk because the AFTR
>>can't
>> identify the IPv4 address?
>>
>> Thanks,
>> Yiu
>>
>> On 10/18/12 11:10 AM, "Black, David" <david.black@emc.com> wrote:
>>
>> >Hello Roberta,
>> >
>> >In that case, more text is needed to explain in Section 2.8, and
>> >the related theft of service concern also needs to be discussed in
>> >that section and/or the Security Considerations section.
>> >
>> >Thanks,
>> >--David
>> >
>> >> -----Original Message-----
>> >> From: Maglione Roberta [mailto:roberta.maglione@telecomitalia.it]
>> >> Sent: Thursday, October 18, 2012 3:18 AM
>> >> To: Black, David; Lee, Yiu; 'draft-ietf-softwire-dslite-
>> >> deployment@tools.ietf.org'
>> >> Cc: Ralph Droms; gen-art@ietf.org; softwire-chairs@tools.ietf.org
>> >> Subject: RE: Gen-ART review of
>>draft-ietf-softwire-dslite-deployment-06
>> >>
>> >> Hello Yiu and David,
>> >> regarding point 5:
>> >>
>> >> > [YL] Good catch. Actually I believe AFTR "does" have both IPv4 and
>> >> > IPv6 to identify the customer. I suggest we remove
>> >> >
>> >> > "but it will potentially introduce some additional complexity
>>because
>> >> >    the AFTR does not have detailed customer identity information."
>> >>
>> >> The point related to the accounting is different: what I meant here
>>with
>> >> accounting is RADIUS based accounting, commonly used in Broadband
>>networks.
>> >>
>> >> Today RADIUS accounting is done at the BNG level, the problem with
>>the
>> >> introduction of the AFTR is that the AFTR does not interact with
>>AAA/RADIUS
>> >> Server for the initial authentication/authorization/accounting phase
>>because
>> >> the authentication/authorization/accounting process happens between
>>BNG and
>> >> RADIUS Server when the session comes up.
>> >> The ATFR is not able to perform RADIUS accounting because as it does
>>not
>> >> interact with the RADIUS Server it does not have " detailed customer
>>identity
>> >> information" for example it does know the accounting session ID
>>associated to
>> >> that session, that's why it cannot do detailed accounting for each
>>single
>> >> subscriber even if the ATFR can still correlated IPv6 and IPv4
>>traffic
>> >> belonging to the same user.
>> >>
>> >> This is an important operational issue, I would suggest to keep this
>>concept.
>> >> If you think is needed I can add some lines of text in order to
>>clarify this
>> >> point.
>> >>
>> >> Thanks
>> >> Regards,
>> >> Roberta
>> >>
>> >> -----Original Message-----
>> >> From: Black, David [mailto:david.black@emc.com]
>> >> Sent: Thursday, October 18, 2012 3:12 AM
>> >> To: Lee, Yiu; Maglione Roberta; carlw@mcsr-labs.org;
>> >> christian.jacquenet@orange.com; mohamed.boucadair@orange.com;
>> >>gen-art@ietf.org
>> >> Cc: softwires@ietf.org; ietf@ietf.org; Ralph Droms; Black, David
>> >> Subject: RE: Gen-ART review of
>>draft-ietf-softwire-dslite-deployment-06
>> >>
>> >> Yiu,
>> >>
>> >> Thank you for your responses - most of them look fine, and in
>> >> particular anything that I don't comment on here is acceptable to me.
>> >>
>> >> > [YL] In 2.2, we will add:
>> >> >
>> >> > "Note that reassembly at Tunnel Exit-Point is resource
>> >> >       intensive. A large number of B4 may terminate on the same
>>AFTR. If many B4
>> >> >       fragment the packets, it would increase sufficient load to
>>the AFTR for
>> >> >       reassembly. We recommend the operator should increase the
>>MTU size of the IPv6
>> >> >       network between B4 and AFTR to avoid fragmentation."
>> >>
>> >> I would change "is" to "may be" in the first line.
>> >>
>> >> > >[5] Section 2.8 discusses IPv4 accounting at the AFTR, but notes
>>that
>> >> > >"the AFTR does not have detailed customer identity information."
>>Does
>> >> > >that create a theft of service possibility?  If so, that
>>possibility
>> >> > >should be mentioned as a security consideration.  Also, Section
>>2.8
>> >> > >ought to be expanded with a sentence or two explaining why the
>>AFTR
>> >> > >does not have that identity information, and in particular to
>>explain
>> >> > >whether and why it is unreasonable in some or all cases to expect
>> >> > >that customer identity information be provided to the AFTR as part
>> >> > >of provisioning each customer's softwire.
>> >> >
>> >> > [YL] Good catch. Actually I believe AFTR "does" have both IPv4 and
>> >>IPv6 to
>> >> > identify the customer. I suggest we remove
>> >> >
>> >> > "but it will potentially introduce some additional complexity
>>because
>> >> >    the AFTR does not have detailed customer identity information."
>> >>
>> >> That's definitely an easy way to address that issue, and it's fine
>>with
>> >>me.
>> >>
>> >> > >Section 2.3 on MTU Considerations could usefully mention MTU
>> >>discovery
>> >> > >techniques, as possibilities for customer IPv4 traffic to adapt
>>to a
>> >> > >smaller IPv4 MTU.  If this is done, it would be useful to mention
>> >> > >RFC 4821 in addition to the mention of RFC 1191 in RFC 6333.
>> >> >
>> >> > [YL] We would consider RFC 4821. However, the challenge is I don't
>> >>have
>> >> > information how many current OS support RFC 4821. Since DS-lite is
>>a
>> >> > transition technology, it would be unreasonable to ask the OS
>>company
>> >>to
>> >> > implement RFC 4821 for DS-lite.
>> >>
>> >> That's ok - this was a nit.
>> >>
>> >> > >- Are one or both types of logging recommended?
>> >> >
>> >> > [YL] We tempted to recommend source-specific log. However, some
>> >>regulators
>> >> > require to use both and the regulations vary country from country,
>> >>this is
>> >> > why we left it open and let the operators to decide.
>> >>
>> >> Please add a version of your explanation to the draft.
>> >>
>> >> > >In Section 2.7, I'm having a hard time understanding which
>>traffic is
>> >> > >intended to be subject to the Outgoing Policies and the Incoming
>> >>Policies.
>> >> > >Expanding each of those two bullets to explain what traffic is
>> >>subject
>> >> > >to each class of policies would help.
>> >> >
>> >> > [YL] Does this help?
>> >> >
>> >> > Outgoing Policies apply to packets originating from B4 to IPv4
>> >>network.
>> >> > Incoming Policies apply to packets originating from IPv4 network to
>> >>B4.
>> >>
>> >> Yes, that's clearer, although the B4 is not the network endpoint for
>>any
>> >> of that traffic.  I suggest:
>> >>
>> >> Outgoing Policies apply to packets originating from behind the B4
>>with
>> >> a destination on the IPv4 network.
>> >>
>> >> Incoming Policies apply to packets originating from the IPv4 network
>>to
>> >> a destination behind the B4.
>> >>
>> >> Thanks,
>> >> --David
>> >>
>> >>
>> >> > -----Original Message-----
>> >> > From: Lee, Yiu [mailto:Yiu_Lee@cable.comcast.com]
>> >> > Sent: Wednesday, October 17, 2012 8:46 PM
>> >> > To: Black, David; roberta.maglione@telecomitalia.it;
>> >>carlw@mcsr-labs.org;
>> >> > christian.jacquenet@orange.com; mohamed.boucadair@orange.com; gen-
>> >> art@ietf.org
>> >> > Cc: softwires@ietf.org; ietf@ietf.org; Ralph Droms
>> >> > Subject: Re: Gen-ART review of
>> >>draft-ietf-softwire-dslite-deployment-06
>> >> >
>> >> > Hi David,
>> >> >
>> >> > Thanks very much for review the draft. Comments inline.
>> >> >
>> >> > Thanks,
>> >> > Yiu
>> >> >
>> >> > On 10/15/12 7:10 PM, "Black, David" <david.black@emc.com> wrote:
>> >> >
>> >> > >I am the assigned Gen-ART reviewer for this draft. For background
>>on
>> >> > >Gen-ART, please see the FAQ at
>> >> > ><http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>> >> > >
>> >> > >Please resolve these comments along with any other Last Call
>>comments
>> >> > >you may receive.
>> >> > >
>> >> > >Document: draft-ietf-softwire-dslite-deployment-06
>> >> > >Reviewer: David L. Black
>> >> > >Review Date: October 15, 2012
>> >> > >IETF LC End Date: October 16, 2012
>> >> > >IESG Telechat Date: October 25, 2012
>> >> > >
>> >> > >Summary:
>> >> > >
>> >> > >This draft is on the right track but has open issues, described in
>> >>the
>> >> > >review.
>> >> > >
>> >> > >This is a generally well-written draft that expands considerably
>>on
>> >>the
>> >> brief
>> >> > >deployment considerations for DS-Lite in Appendix A of RFC 6333.
>> >>The draft
>> >> > >is clear and reasonably well-written, and a significant
>>improvement
>> >>on that
>> >> > >RFC 6333 Appendix, although an understanding of RFC 6333 is
>> >>necessary to
>> >> > >understand this draft, which seems completely reasonable.
>> >> > >
>> >> > >The B4 and AFTR acronyms are clever - kudos to whomever came up
>>with
>> >> > >those.
>> >> > >
>> >> > >I found five open issues, all of which are minor.
>> >> > >
>> >> > >Minor Issues:
>> >> > >
>> >> > >[1] Ironically, the first issue is that something should be said
>> >>about
>> >> > >the relationship of this draft to Appendix A of RFC 6333.  It
>> >>probably
>> >> > >suffices to say that this draft expands on the material in that
>> >>Appendix,
>> >> > >as I see no need to specify that this draft updates RFC 6333
>>solely
>> >>to
>> >> > >change non-normative material in an Appendix.
>> >> >
>> >> > [YL] In "Overview", we will add:
>> >> >
>> >> > "This document expands Appendix A of RFC6333 and discusses various
>> >> > DS-Lite deployment considerations for operators."
>> >> >
>> >> > >
>> >> > >[2] The MTU increase technique in Section 2.2 is a "may", which is
>> >> > >consistent with Section 5.3 of RFC 6333.  OTOH, Section 2.2 of
>>this
>> >> > >draft should also discuss the AFTR resource exhaustion concern
>>that
>> >> > >described in Section 6.3 of RFC 6333, as that is a potential
>> >> > >operational reason for an ISP to increase MTU size (e.g., if
>>customer
>> >> > >sourcing of large IPv4 packets is not sufficiently rare).
>> >> >
>> >> > [YL] In 2.2, we will add:
>> >> >
>> >> > "Note that reassembly at Tunnel Exit-Point is resource
>> >> >       intensive. A large number of B4 may terminate on the same
>>AFTR.
>> >>If
>> >> many B4
>> >> >       fragment the packets, it would increase sufficient load to
>>the
>> >>AFTR
>> >> for
>> >> >       reassembly. We recommend the operator should increase the MTU
>> >>size of
>> >> the IPv6
>> >> >       network between B4 and AFTR to avoid fragmentation."
>> >> >
>> >> > >
>> >> > >[3] Section 2.7 refers to "the AFTR's internal interface".  There
>> >>may be
>> >> > >two internal interfaces, the physical IPv6 interface (outer
>>header)
>> >>and
>> >> > >the tunnel's IPv4 interface (inner header).  The text should be
>> >>clarified
>> >> > >to indicate which interface is involved - it appears that the
>>AFTR's
>> >> > >physical IPv6 interface is intended in this section.
>> >> >
>> >> > [YL] We replace "internal" to "IPv6"
>> >> >
>> >> > >
>> >> > >[4] Section 2.7 cites RFC 6333 for use of DHCPv6 with DS-Lite.
>>RFC
>> >>6334
>> >> > >should be cited - either in addition to or instead of RFC 6333.
>> >> >
>> >> > [YL] Fixed
>> >> >
>> >> > >
>> >> > >[5] Section 2.8 discusses IPv4 accounting at the AFTR, but notes
>>that
>> >> > >"the AFTR does not have detailed customer identity information."
>> >>Does
>> >> > >that create a theft of service possibility?  If so, that
>>possibility
>> >> > >should be mentioned as a security consideration.  Also, Section
>>2.8
>> >> > >ought to be expanded with a sentence or two explaining why the
>>AFTR
>> >> > >does not have that identity information, and in particular to
>>explain
>> >> > >whether and why it is unreasonable in some or all cases to expect
>> >> > >that customer identity information be provided to the AFTR as part
>> >> > >of provisioning each customer's softwire.
>> >> >
>> >> > [YL] Good catch. Actually I believe AFTR "does" have both IPv4 and
>> >>IPv6 to
>> >> > identify the customer. I suggest we remove
>> >> >
>> >> > "but it will potentially introduce some additional complexity
>>because
>> >> >    the AFTR does not have detailed customer identity information."
>> >> >
>> >> > >
>> >> > >Nits:
>> >> > >
>> >> > >Section 2.3 on MTU Considerations could usefully mention MTU
>> >>discovery
>> >> > >techniques, as possibilities for customer IPv4 traffic to adapt
>>to a
>> >> > >smaller IPv4 MTU.  If this is done, it would be useful to mention
>> >> > >RFC 4821 in addition to the mention of RFC 1191 in RFC 6333.
>> >> >
>> >> > [YL] We would consider RFC 4821. However, the challenge is I don't
>> >>have
>> >> > information how many current OS support RFC 4821. Since DS-lite is
>>a
>> >> > transition technology, it would be unreasonable to ask the OS
>>company
>> >>to
>> >> > implement RFC 4821 for DS-lite.
>> >> >
>> >> > >
>> >> > >Section 2.4 should define "lawful intercept".  It would be
>>helpful to
>> >> > >cite a reference for this concept if something appropriate can be
>> >>found.
>> >> >
>> >> > [YL] We will find whether there is any reference to this concept.
>>If
>> >>we
>> >> > can't find any, we would add an explanation in the draft.
>> >> >
>> >> > >
>> >> > >Section 2.5:
>> >> > >- Are one or both types of logging recommended?
>> >> >
>> >> > [YL] We tempted to recommend source-specific log. However, some
>> >>regulators
>> >> > require to use both and the regulations vary country from country,
>> >>this is
>> >> > why we left it open and let the operators to decide.
>> >> >
>> >> > >- Last paragraph on p.4, "timestamped log" is not a good verb
>>phrase.
>> >> > >     "maintain a timestamped log of" would be a better
>>replacement.
>> >> >
>> >> > [YL] Fixed
>> >> >
>> >> > >- Last paragraph in section, where is the batch file sent?
>> >> >
>> >> > [YL] We will add:
>> >> >
>> >> > "The files may be compressed before transferring to a repository
>> >>server
>> >> >       to better utilize bandwidth and storage."
>> >> >
>> >> >
>> >> > >
>> >> > >In Section 2.7, I'm having a hard time understanding which
>>traffic is
>> >> > >intended to be subject to the Outgoing Policies and the Incoming
>> >>Policies.
>> >> > >Expanding each of those two bullets to explain what traffic is
>> >>subject
>> >> > >to each class of policies would help.
>> >> >
>> >> > [YL] Does this help?
>> >> >
>> >> > Outgoing Policies apply to packets originating from B4 to IPv4
>> >>network.
>> >> > Incoming Policies apply to packets originating from IPv4 network to
>> >>B4.
>> >> >
>> >> >
>> >> >
>> >> > >
>> >> > >Section 3.2.2.2 uses 192.0.0.2/32 as an example IP address for the
>> >> > >B4.  That section should also cross-reference Section 5.7 on RFC
>>6333
>> >> > >on IP address assignment to B4s, as other IP addresses may be
>>used.
>> >> >
>> >> > [YL] Added the cite.
>> >> >
>> >> > >
>> >> > >idnits 2.12.13 found a tiny nit - draft-ietf-pcp-base is now at
>> >> > >version 28.
>> >> >
>> >> > [YL] Fixed.
>> >> >
>> >> > >
>> >> > >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
>> >> > >----------------------------------------------------
>> >> > >
>> >> > >
>> >>
>> >> Questo messaggio e i suoi allegati sono indirizzati esclusivamente
>>alle
>> >> persone indicate. La diffusione, copia o qualsiasi altra azione
>> >>derivante
>> >> dalla conoscenza di queste informazioni sono rigorosamente vietate.
>> >>Qualora
>> >> abbiate ricevuto questo documento per errore siete cortesemente
>>pregati
>> >>di
>> >> darne 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,
>> >> printing or use by anybody else is unauthorised. If you are not the
>> >>intended
>> >> recipient, please delete this message and any attachments and advise
>>the
>> >> sender by return e-mail, Thanks.
>> >>
>> >

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

MIIVmQYJKoZIhvcNAQcCoIIVijCCFYYCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
EzEwggU0MIIEHKADAgECAhEAzuhISIgzOwSitfbc2LN4WDANBgkqhkiG9w0BAQUFADCBkzEL
MAkGA1UEBhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2Fs
Zm9yZDEaMBgGA1UEChMRQ09NT0RPIENBIExpbWl0ZWQxOTA3BgNVBAMTMENPTU9ETyBDbGll
bnQgQXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTAeFw0xMjA4MjgwMDAwMDBa
Fw0xMzA4MjgyMzU5NTlaMCoxKDAmBgkqhkiG9w0BCQEWGXlpdV9sZWVAY2FibGUuY29tY2Fz
dC5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCscOeu5/EoYRdja1jb6L4x
o0TIevelc17NsPuRHfr2z3BGUMbfsJY1p0uXO9+inBQoBXwb07ac3SbOjA/6Ef3NlMPItWdT
RGeFL6e/sMju9RgVyJURFnFgp7tc2tffnPOupnKZeeRehXeEFjun6+GC6teb1kSMu+WMMaCa
D7/XSK+Q+F0Udc2Av0/gUCkGfTDpNnYwutfctEMRnle6EYUqmJMN4C0crEfovmYdMFFgJLKs
Wa5Cdc+naFoIqzW8AcZB6+1XUDTzFbgjqgUbFFZFPzVZqNxLDFNy4tn8VlRSp2jBhgwQHtk1
ZA+spFENaeUuebp4tczj0IHG683FhhWjAgMBAAGjggHpMIIB5TAfBgNVHSMEGDAWgBR6E04A
dFvGeGNkJ8Ev4qBbvHnFezAdBgNVHQ4EFgQUz03csl7CmjwQY+spX9VWeGb5sVQwDgYDVR0P
AQH/BAQDAgWgMAwGA1UdEwEB/wQCMAAwIAYDVR0lBBkwFwYIKwYBBQUHAwQGCysGAQQBsjEB
AwUCMBEGCWCGSAGG+EIBAQQEAwIFIDBGBgNVHSAEPzA9MDsGDCsGAQQBsjEBAgEBATArMCkG
CCsGAQUFBwIBFh1odHRwczovL3NlY3VyZS5jb21vZG8ubmV0L0NQUzBXBgNVHR8EUDBOMEyg
SqBIhkZodHRwOi8vY3JsLmNvbW9kb2NhLmNvbS9DT01PRE9DbGllbnRBdXRoZW50aWNhdGlv
bmFuZFNlY3VyZUVtYWlsQ0EuY3JsMIGIBggrBgEFBQcBAQR8MHowUgYIKwYBBQUHMAKGRmh0
dHA6Ly9jcnQuY29tb2RvY2EuY29tL0NPTU9ET0NsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2Vj
dXJlRW1haWxDQS5jcnQwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLmNvbW9kb2NhLmNvbTAk
BgNVHREEHTAbgRl5aXVfbGVlQGNhYmxlLmNvbWNhc3QuY29tMA0GCSqGSIb3DQEBBQUAA4IB
AQBG7LORtWcmzDlw0N/D5AwfsSLe93essAqKFhJ+nt7SmMVBsxGzFnSsZGQHMYQ4UXtiVq9A
NjtPk00F3DC3QGxe4mxdwF9LzeYHpHMpCHTzNyilSimKZolLNBO+MO/U0u79rdF2W+dOAwkB
dzroWBxK+yMhijJn2DCE/1pgxqBz+c9zbAtJYPVpgbeGNvvfIp6CA/JYsupQNqPX49a4MdJ3
L9yXLTiegSE8uPUlCB3sHZclQOXAttuMewpcKDoIC4wZgERKQqRH61PQO100GLKUO+VrTq+f
xNkjOAqA+dih6QO5Djbv3qcMTCcAChJQYK8BS7jved8XgEVa0Ihz7oWKMIIFGjCCBAKgAwIB
AgIQbRnqpxlPajMi5iIyeqpx3jANBgkqhkiG9w0BAQUFADCBrjELMAkGA1UEBhMCVVMxCzAJ
BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJU
UlVTVCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNV
BAMTLVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbDAeFw0x
MTA0MjgwMDAwMDBaFw0yMDA1MzAxMDQ4MzhaMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMS
R3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8g
Q0EgTGltaXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQg
U2VjdXJlIEVtYWlsIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAkoSEW0tX
mNReL4uk4UDIo1NYX2Zl8TJO958yfVXQeExVt0KU4PkncQfFxmmkuTLE8UAakMwnVmJ/F7Vx
aa7lIBvky2NeYMqiQfZq4aP/uN8fSG1lQ4wqLitjOHffsReswtqCAtbUMmrUZ28gE49cNfrl
VICv2HEKHTcKAlBTbJUdqRAUtJmVWRIx/wmi0kzcUtve4kABW0ho3cVKtODtJB86r3FfB+Os
vxQ7sCVxaD30D9YXWEYVgTxoi4uDD216IVfmNLDbMn7jSuGlUnJkJpFOpZIP/+CxYP0ab2hR
mWONGoulzEKbm30iY9OpoPzOnpDfRBn0XFs1uhbzp5v/wQIDAQABo4IBSzCCAUcwHwYDVR0j
BBgwFoAUiYJnfcSdJnAAS7RQSHzePa4Ebn0wHQYDVR0OBBYEFHoTTgB0W8Z4Y2QnwS/ioFu8
ecV7MA4GA1UdDwEB/wQEAwIBBjASBgNVHRMBAf8ECDAGAQH/AgEAMBEGA1UdIAQKMAgwBgYE
VR0gADBYBgNVHR8EUTBPME2gS6BJhkdodHRwOi8vY3JsLnVzZXJ0cnVzdC5jb20vVVROLVVT
RVJGaXJzdC1DbGllbnRBdXRoZW50aWNhdGlvbmFuZEVtYWlsLmNybDB0BggrBgEFBQcBAQRo
MGYwPQYIKwYBBQUHMAKGMWh0dHA6Ly9jcnQudXNlcnRydXN0LmNvbS9VVE5BZGRUcnVzdENs
aWVudF9DQS5jcnQwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVzZXJ0cnVzdC5jb20wDQYJ
KoZIhvcNAQEFBQADggEBAIXWvnhXVW0zf0RS/kLVBqgBA4CK+w2y/Uq/9q9BSfUbWsXSrRtz
bj7pJnzmTJjBMCjfy/tCPKElPgp11tA9OYZm0aGbtU2bb68obB2v5ep0WqjascDxdXovnrqT
ecr+4pEeVnSy+I3T4ENyG+2P/WA5IEf7i686ZUg8mD2lJb+972DgSeUWyOs/Q4Pw4O4NwdPN
M1+b0L1garM7/vrUyTo8H+2b/5tJM75CKTmD7jNpLoKdRU2oadqAGx490hpdfEeZpZsIbRKZ
htZdVwcbpzC+S0lEuJB+ytF5OOu0M/qgOl0mWJ5hVRi0IdWZ1eBDQEIwvuql55TSsP7zdfl/
bucwggSdMIIDhaADAgECAhA0PekrrCc0/4/LNJT7zHBUMA0GCSqGSIb3DQEBBQUAMG8xCzAJ
BgNVBAYTAlNFMRQwEgYDVQQKEwtBZGRUcnVzdCBBQjEmMCQGA1UECxMdQWRkVHJ1c3QgRXh0
ZXJuYWwgVFRQIE5ldHdvcmsxIjAgBgNVBAMTGUFkZFRydXN0IEV4dGVybmFsIENBIFJvb3Qw
HhcNMDUwNjA3MDgwOTEwWhcNMjAwNTMwMTA0ODM4WjCBrjELMAkGA1UEBhMCVVMxCzAJBgNV
BAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT
VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMT
LVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbDCCASIwDQYJ
KoZIhvcNAQEBBQADggEPADCCAQoCggEBALI5haTyfatBO2JGN67NwWB1vDll+UoaR6K5zEjM
apjVTTUZuaRC5c5J4oovHnzSMQfHTrSDZJ0uKdWiZMSFvYVRNXmkTmiQexx6pJKoF/KYFfKT
zMmkMpW7DE8wvZigC4vlbhuiRvp4vKJvq1lepS/Pytptqi/rrKGzaqq3Lmc1i3nhHmmI4uZG
zaCl6r4LznY6eg6b6vzaJ1s9cx8i5khhxkzzabGoLhu21DEgLLyCio6kDqXXiUP8FlqvHXHX
EVnauocNr/rz4cLwpMVnjNbWVDreCqS6A3ezZcj9HtN0YqoYymiTHqGFfvVHZcv4TVcodNI0
/zC27vZiMBSMLOsCAwEAAaOB9DCB8TAfBgNVHSMEGDAWgBStvZh6NLQm9/rEJlTvA73gJMtU
GjAdBgNVHQ4EFgQUiYJnfcSdJnAAS7RQSHzePa4Ebn0wDgYDVR0PAQH/BAQDAgEGMA8GA1Ud
EwEB/wQFMAMBAf8wEQYDVR0gBAowCDAGBgRVHSAAMEQGA1UdHwQ9MDswOaA3oDWGM2h0dHA6
Ly9jcmwudXNlcnRydXN0LmNvbS9BZGRUcnVzdEV4dGVybmFsQ0FSb290LmNybDA1BggrBgEF
BQcBAQQpMCcwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVzZXJ0cnVzdC5jb20wDQYJKoZI
hvcNAQEFBQADggEBAAG8nONjKLDzMQHC33vdYqABnSMxD5ySc1NR6h9M+tafxMovZ354Mw90
FrmRh5H1iib6ZHAA2B75CwRiUIeTgdTa9SPbNLuFVrRwNG54gzcehRzFERWSX4cXvaxq/fHC
0cyJX7F88D5R8jXzfOxgmGs6K+Dv37N9huu1G/Vb7KJ8mBPXAFC50S1z3gN4dOEFhTFey5q5
nZTGuZQ3dXLcRPtn6PD6JR5Sp9ol6UfgoMc8oE6xCjb7d0if75eK+7T+45QUqIO8XC0/0mBx
YO7CcYIM6Yg249ogtKOgbKqWS7iAjnXKSQf2OxS639wF2Z/b4LLmTaB4JufnLW5/X8YeiBUw
ggQ2MIIDHqADAgECAgEBMA0GCSqGSIb3DQEBBQUAMG8xCzAJBgNVBAYTAlNFMRQwEgYDVQQK
EwtBZGRUcnVzdCBBQjEmMCQGA1UECxMdQWRkVHJ1c3QgRXh0ZXJuYWwgVFRQIE5ldHdvcmsx
IjAgBgNVBAMTGUFkZFRydXN0IEV4dGVybmFsIENBIFJvb3QwHhcNMDAwNTMwMTA0ODM4WhcN
MjAwNTMwMTA0ODM4WjBvMQswCQYDVQQGEwJTRTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAk
BgNVBAsTHUFkZFRydXN0IEV4dGVybmFsIFRUUCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVz
dCBFeHRlcm5hbCBDQSBSb290MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAt/ca
M+byAAQtOeBOW+0fvGwPzbX6I7bO3psRM5ekKUx9k5+9SryT7QMa44/P5W1QWtaXKZRagLBJ
etsulf24yr83OC0ePpFBrXBWx/BPP+gynnTKyJBU6cZfD3idmkA8Dqxhql4Uj56HoWpQ3Nea
Tq8Fs6ZxlJxxs1BgCscTnTgHhgKo6ahpJhiQq0ywTyOrOk+E2N/On+Fpb7vXQtdrROTHre5t
QV9yWnEIN7N5ZaRZoJQ39wAvDcKSctrQOHLbFKhFxF0qfbe01sTurM0TRLfJK91DACX6Yblp
algjEbenM49WdVn1zSnXRrcKK2W200JvFbK4e/vv6V1T1TRaJwIDAQABo4HcMIHZMB0GA1Ud
DgQWBBStvZh6NLQm9/rEJlTvA73gJMtUGjALBgNVHQ8EBAMCAQYwDwYDVR0TAQH/BAUwAwEB
/zCBmQYDVR0jBIGRMIGOgBStvZh6NLQm9/rEJlTvA73gJMtUGqFzpHEwbzELMAkGA1UEBhMC
U0UxFDASBgNVBAoTC0FkZFRydXN0IEFCMSYwJAYDVQQLEx1BZGRUcnVzdCBFeHRlcm5hbCBU
VFAgTmV0d29yazEiMCAGA1UEAxMZQWRkVHJ1c3QgRXh0ZXJuYWwgQ0EgUm9vdIIBATANBgkq
hkiG9w0BAQUFAAOCAQEAsJvghSXC1iPiD5YGkp1BmJzZhHmB2R5bFAcjNmWPsNh3u6xBbEdg
g1Gw+TI95/z2JhPHgBalv1r8h894eYkhmuJMBwqGNbzy3lHE0pa33H5O7nD9HDnrDAJRFC2O
vRbgwd9Gdeckrez0QrSFk3AQZ7qdBjVKGNMresxRQqF6Y9Hmu6HFK8I2vhMN5r1jfnl7pwkN
QKtq3Y+Kw/b2jBpCBVHURfWfp2IhaBUgQzyZ53y9JNipkRdziD9WGzE4GLRxD5rNyA6eji4b
4YyYg8sfMfFETMYEc0l2YA/H+L0XgGsu6cxMDlqaeQ8gCi7VnmMmHlWSlNiCF1p70LzHj06G
BDGCAjAwggIsAgEBMIGpMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5j
aGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDE5
MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWls
IENBAhEAzuhISIgzOwSitfbc2LN4WDAJBgUrDgMCGgUAoF0wIwYJKoZIhvcNAQkEMRYEFD5b
oSNok6h8LKpJgMYxlH1HRCszMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcN
AQkFMQ8XDTEyMTAyMjIxNTQwNFowDQYJKoZIhvcNAQEBBQAEggEAjDSpCmuzodf+W94QsjTo
GaUlKmCITUYzyboYc0ceR7fqpSr5gE2ThCffSnMFZOKFxYNwx3cfTqsU1RmUfkKZ0rywFPbE
4mxO99uM5AYKWWifSar0dW7+t5rCCxFesbK1zhMQkqU6F5h4q3BUYEeJVwjmwXUTgL2tkJbJ
EFaXZJJ8IXdMinEWPx+Lia5Soe3zJ4azI1GR3zNE/2vh4tNbIujGYG18urOddXjt8KXvhCUO
Hy1XiviUHqMaX0WCAY+QU6AFeNvCdgte8Oxum1fZ9xDNaecot4PN/ALShjTBnmQhCWimREey
nDqGfEHPU2XFdZf3LGRc9/OurxwWvamTaw==

--B_3433773245_11682--

From peter@akayla.com  Mon Oct 22 18:24:06 2012
Return-Path: <peter@akayla.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E107321F88EE; Mon, 22 Oct 2012 18:24:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.097
X-Spam-Level: *
X-Spam-Status: No, score=1.097 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MANGLED_LIST=2.3, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tbnLWoVmY6-0; Mon, 22 Oct 2012 18:24:04 -0700 (PDT)
Received: from m1plsmtpa01-04.prod.mesa1.secureserver.net (m1plsmtpa01-04.prod.mesa1.secureserver.net [64.202.165.6]) by ietfa.amsl.com (Postfix) with ESMTP id 5DB2521F841E; Mon, 22 Oct 2012 18:24:03 -0700 (PDT)
Received: from [10.1.168.230] ([198.228.207.143]) by m1plsmtpa01-04.prod.mesa1.secureserver.net with  id ERQ01k00436ACtS01RQ1yU; Mon, 22 Oct 2012 18:24:02 -0700
References: <CCAA0CA5.11A5%peter@akayla.com> <F9C49DE0-5BB3-4714-96A7-96EA7DA94DF7@oracle.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <F9C49DE0-5BB3-4714-96A7-96EA7DA94DF7@oracle.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <1ACD4B0A-FA94-46BE-8343-2B3D6A6ACCDB@akayla.com>
X-Mailer: iPhone Mail (10A405)
From: Peter Yee <peter@akayla.com>
Date: Mon, 22 Oct 2012 21:24:00 -0400
To: Chuck Lever <chuck.lever@oracle.com>
Cc: "<gen-art@ietf.org>" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "<draft-ietf-nfsv4-federated-fs-protocol.all@tools.ietf.org>" <draft-ietf-nfsv4-federated-fs-protocol.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-nfsv4-federated-fs-protocol-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: Tue, 23 Oct 2012 01:24:06 -0000

Chuck,

I'll cheerfully settle for the status quo. Please ignore that comment.=20

Thanks.=20

                                -Peter


On Oct 22, 2012, at 4:10 PM, Chuck Lever <chuck.lever@oracle.com> wrote:

>=20
> On Oct 21, 2012, at 11:35 PM, Peter Yee <peter@akayla.com> wrote:
>=20
>> Chuck,
>>    Ranges include the 0,255 that appears commonly in the document in
>> attribute definitions along with one case of -2147483648,2147483647.
>=20
> Hi Peter-
>=20
> Upon further review, I see the document uses "interval notation" when defi=
ning ranges of allowed values in attributes.  The use of square brackets den=
otes inclusivity.  If you feel readers need more, or our use of this notatio=
n is inconsistent, I'm happy to add clarification.
>=20
>>    Kind regards,
>>        -Peter
>>=20
>> On 10/21/12 3:27 PM, "Chuck Lever" <chuck.lever@oracle.com> wrote:
>>=20
>>>=20
>>> On Oct 21, 2012, at 5:39 PM, Peter Yee <peter@akayla.com> wrote:
>>>=20
>>>> I am the assigned Gen-ART reviewer for this draft. For background on
>>>> Gen-ART, please see the FAQ at
>>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>>>>=20
>>>> Document: draft-ietf-nfsv4-federated-fs-protocol-13
>>>> Reviewer: Peter Yee
>>>> Review Date: Oct-19-2012
>>>> IETF LC End Date: Oct-22-2012
>>>> IESG Telechat date: TBD
>>>>=20
>>>>=20
>>>> Summary: This draft is basically ready for publication, but has nits
>>>> that
>>>> should be fixed before publication. [Ready with nits.]
>>>>=20
>>>>=20
>>>> This Standards Track document describes a protocol for maintaining a
>>>> Namespace Database for use with federated filesystem protocols.  The
>>>> document is well-written with good examples and little need to jump bac=
k
>>>> and forth in the text to understand it.
>>>>=20
>>>> General: Are ranges (in attribute values) inclusive or exclusive?  They=

>>>> appear to be inclusive, but it might be worth saying that somewhere, if=

>>>> only once.
>>>=20
>>> Can you give me an example of a range that might need clarification?
>>>=20
>>> I will address these comments and co-ordinate draft updates with our WG
>>> editor, Tom Haynes.
>>>=20
>>> Thanks for your review.
>>>=20
>>>> Section 2.7, NsdbName definition: expand NSDB to Namespace Database as
>>>> this is the first use of the term.
>>>>=20
>>>> Section 2.8.1, 2nd sentence: "extention" -> "extension"
>>>>=20
>>>> Section 2.8.3, 2nd paragraph, last sentence: in addition to checking fo=
r
>>>> added FSL records, shouldn't the fileserver also be checking for delete=
d
>>>> or migrated FSLs?  And why would the fileserver do this at the
>>>> expiration
>>>> of the FSN TTL instead of waiting for the next access to the that FSN?
>>>> Otherwise the fileserver could be generating unnecessary traffic,
>>>> although
>>>> there is a tradeoff to be made vs. performance.
>>>>=20
>>>> Section 2.8.3, 3rd paragraph after bullet items, 1st sentence: "which"
>>>> ->
>>>> "that".  (Yeah, I know, grammar police.)
>>>>=20
>>>> Section 2.9, 3rd paragraph, 2nd sentence: "admininistrative" ->
>>>> "administrative"
>>>>=20
>>>> Section 2.12, 2nd paragraph, last sentence: expand NCE (NSDB Container
>>>> Entry) as this is the first use of the term.
>>>>=20
>>>> Section 3.2, item #5: "fs_location" -> "fs_locations"
>>>>=20
>>>> Section 4.1, 1st paragraph, 3rd sentence: probably worth expanding "DSE=
"
>>>> to "DSA-specific entry" here.
>>>>=20
>>>> Section 4.2.1.8, 1st paragraph, 2nd sentence: bracket "Section 2.8.1" i=
n
>>>> "(see" and ")" for readability.
>>>>=20
>>>> Section 4.2.2: "LDAP Objects" -> "LDAP Object Classes" seems
>>>> appropriate.
>>>>=20
>>>> Section 4.2.2.1, 2nd and 3rd sentences: replace "fedfsFsn" with
>>>> "fedfsNsdbContainerInfo"
>>>>=20
>>>> Section 4.2.2.2, 5th paragraph: how is the prohibition on referencing
>>>> other attributes in the fedfsFsn object class supposed to work if this
>>>> document is the defining document for that object class?
>>>>=20
>>>> Section 5.1.3.1, 1st paragraph after LDIF definition: a port number of
>>>> 2049 is given.  Since this is already the default value, why not use a
>>>> different value?  Otherwise, there would be no practical need to includ=
e
>>>> that port number in the FSL creation request.
>>>>=20
>>>> Section 5.1.3.1, 1st paragraph after LDIF definition: "up to date" ->
>>>> "up-to-date"
>>>>=20
>>>> Section 5.1.3.2, 2nd paragraph: "a" -> "an"
>>>>=20
>>>> Section 5.1.3.2, table entry for "fedfsNfsVarSub": "substituion" ->
>>>> "substitution"
>>>>=20
>>>> Section 5.1.4, 1st paragraph, 1st sentence: "a Fileset location" -> "an=

>>>> FSL"
>>>>=20
>>>> Section 7.3, 2nd paragraph, "Specification" value: presumably this will=

>>>> be
>>>> changed to the RFC number when issued?
>>>>=20
>>>> Section 8, 1st paragraph (definition of Administrator): "an" -> "a"
>>>>=20
>>>> Section 8, 3rd paragraph (definition of Client): "filesystem access" ->=

>>>> "file-access" for consistency of usage with the rest of the document.
>>>>=20
>>>> Section 8, 5th paragraph (definition of Fileserver): rather than
>>>> discussing "a filesystem", should this be "one or more filesystems"?  O=
r
>>>> is a fileserver limited to exporting one filesystem?
>>>>=20
>>>> Section 8, 8th paragraph (definition of Filesystem Access Protocol):
>>>> following up on the 3rd paragraph, should this be "File-access Protocol=
"
>>>> for consistency?
>>>>=20
>>>> Section 8, 9th paragraph (definition of FSL), 2nd sentence:
>>>> "fs_location"
>>>> -> "fs_locations".
>>>=20
>>> --=20
>>> Chuck Lever
>>> chuck[dot]lever[at]oracle[dot]com
>>=20
>> <default[4].xml>
>=20
> --=20
> Chuck Lever
> chuck[dot]lever[at]oracle[dot]com
>=20
>=20
>=20
>=20
>=20

From mccap@petoni.org  Mon Oct 22 18:42:29 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 D6B351F0C89 for <gen-art@ietfa.amsl.com>; Mon, 22 Oct 2012 18:42:29 -0700 (PDT)
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=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M7OmWmAyCWiK for <gen-art@ietfa.amsl.com>; Mon, 22 Oct 2012 18:42:27 -0700 (PDT)
Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 52F641F0429 for <gen-art@ietf.org>; Mon, 22 Oct 2012 18:42:13 -0700 (PDT)
Received: by mail-gh0-f172.google.com with SMTP id g10so667356ghb.31 for <gen-art@ietf.org>; Mon, 22 Oct 2012 18:42:12 -0700 (PDT)
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=CjPBLpHlp+0PZ9ogVy8VYvtKWS+/qb8JsLJG5YxGIxo=; b=D4UMlS7mKhrLuTaeaOWOPKAtukubkINP29akuJc1Y3TLoB5kYRH2FkCbgUQSaO8VGg Sqc/pXAGzqBcWY02SMG4OghyKUV0b8GzMF8doW82mrVDLwzIGpdlhcD8ot5anVx9A75y Rx6mWdKhnNhSxPe2y1DO7BqFzxBlUeX3WtJJg=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=CjPBLpHlp+0PZ9ogVy8VYvtKWS+/qb8JsLJG5YxGIxo=; b=gFI824ukFbnyhEp7E4k03kRIK71GEPOfMTvRYysuWdNK7URWTEnRZsewfYjFI9infV FahV9txXiaOFlG0PY1gBCxc+qXgPaYloL/XHPlDiwj6zcjOeUT3LM3q36Yx7HNdvd5EX vUrJT8PIYhbaMpZRXlfeQLMSCikhWqlolm7c+a640iOwBzxGZRJq9TPD+aUO9SDIhaKt mCXyIq/GUyVIDOLCiU/x2p0RLNaYyAvKTkDnrnSAtGWFWmshV4VZcA6x8yNXdPj+NkZ8 MKyS/Eh9jt+CfpGZaWntm5QqxYgAMgGJ1IH3vn9U1RwdhfUjJKhvVRVbx/x4ScltmjrM uvug==
MIME-Version: 1.0
Received: by 10.236.86.73 with SMTP id v49mr10326282yhe.31.1350956532874; Mon, 22 Oct 2012 18:42:12 -0700 (PDT)
Received: by 10.101.117.7 with HTTP; Mon, 22 Oct 2012 18:42:12 -0700 (PDT)
X-Originating-IP: [68.45.157.93]
Date: Mon, 22 Oct 2012 21:42:12 -0400
Message-ID: <CACvMsLHpd7hqx0A8JzLst_o05cdMRpGcQtgPoMC=kD6xh6u4Tw@mail.gmail.com>
From: Pete McCann <mccap@petoni.org>
To: gen-art@ietf.org, ietf@ietf.org, draft-ietf-storm-iser.all@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQn3LHaTAX7tSHAq7iSym1TFO1n7RM90wZlr8L6tRC70Wqe9Qac7l2S43fTB/Xw4gzcUThBV
Subject: [Gen-art] Gen-ART LC Review of draft-ietf-storm-iser-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: Tue, 23 Oct 2012 01:42:30 -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-storm-iser-12
Reviewer:  Peter McCann
Review Date:  2012-10-22
IETF LC End Date:  2012-10-22
IESG Telechat date: unknown

Summary: Ready

Major issues: None

Minor issues: None

Nits/editorial comments:

page 38:
   iSERHelloREquired
SHOULD BE:
   iSERHelloRequired

From miguel.a.garcia@ericsson.com  Mon Oct 22 22:45:54 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 C30EE21F8A62 for <gen-art@ietfa.amsl.com>; Mon, 22 Oct 2012 22:45:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.24
X-Spam-Level: 
X-Spam-Status: No, score=-6.24 tagged_above=-999 required=5 tests=[AWL=0.009,  BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZOO1UnNJ-Spb for <gen-art@ietfa.amsl.com>; Mon, 22 Oct 2012 22:45:53 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 78D5021F8A4F for <gen-art@ietf.org>; Mon, 22 Oct 2012 22:45:52 -0700 (PDT)
X-AuditID: c1b4fb25-b7f956d0000011c3-0f-50862f0e86a2
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 14.D4.04547.E0F26805; Tue, 23 Oct 2012 07:45:50 +0200 (CEST)
Received: from [159.107.24.225] (153.88.115.8) by esessmw0184.eemea.ericsson.se (153.88.115.82) with Microsoft SMTP Server id 8.3.279.1; Tue, 23 Oct 2012 07:45:50 +0200
Message-ID: <50862F0C.5090002@ericsson.com>
Date: Tue, 23 Oct 2012 07:45:48 +0200
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Vincent Roca <vincent.roca@inria.fr>
References: <507EBEE9.2030909@ericsson.com> <09C22160-F583-47C0-99B6-386F8DE580AB@inria.fr>
In-Reply-To: <09C22160-F583-47C0-99B6-386F8DE580AB@inria.fr>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrILMWRmVeSWpSXmKPExsUyM+JvrS6ffluAwZl9khabjx9ntrh5qYXV 4uqrzywWW+bkWXT0XWWz6FnVz+LA5rFz1l12jyVLfjJ5THpxiMVjxrGX7B5fLn9mC2CN4rJJ Sc3JLEst0rdL4MrYtf8DS8EKhYrufZvZGxj3SnYxcnBICJhI/H2m0sXICWSKSVy4t54NxBYS OMUoceh2dRcjF5C9hlHi0YlHrCAJXgFtiUXHV4EVsQioSkw8tYsJxGYTMJdo3biRHWSmqECw RNdhMYhyQYmTM5+wgNgiAhoSdx++ZgaZySzwgFHi7uxDzCAJYQF7iTvbP7NDLI6WmDJ/GthM TgEbiYX97xlBbGYBW4kLc66zQNjyEtvfzmGGqNeUmHxzKfMERsFZSPbNQtIyC0nLAkbmVYzC uYmZOenlRnqpRZnJxcX5eXrFqZsYgcF+cMtv1R2Md86JHGKU5mBREue13rrHX0ggPbEkNTs1 tSC1KL6oNCe1+BAjEwenVAMjc02N2a+zG4KdTmalCHoIPr0cyCnY9mjGdebQg8vCXuyx4HJf 53RMM2Med/xH5/q9m5N/i4YtTIpo/h98PUz6zESjvMoy7qVyRk7To66H+2QL3J7nk/rx7o1P T083z4l++FPtjICU4kSZW70FXr6/b61rZTkYylY4OeV56Su+9Cfz/XN2C6QpsRRnJBpqMRcV JwIAAA8qUkQCAAA=
Cc: draft-ietf-fecframe-simple-rs.all@tools.ietf.org, Greg Shepherd <gjshep@gmail.com>, fecframe-chairs@tools.ietf.org, General Area Review Team <gen-art@ietf.org>, Martin Stiemerling <martin.stiemerling@neclab.eu>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-fecframe-simple-rs-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, 23 Oct 2012 05:45:54 -0000

Excellent. All agreed.

/Miguel

On 22/10/2012 16:58, Vincent Roca wrote:
> Dear Miguel,
>
> Thanks a lot for your comments.
>
>> Document: draft-ietf-fecframe-simple-rs-04
>> Reviewer: Miguel Garcia <Miguel.A.Garcia@ericsson.com>
>> Review Date: 2012-10-17
>> IETF LC End Date: 2012-10-22
>>
>> Summary: The document is ready for publication as a standards track RFC, but has some Nits that should be addressed.
>>
>> Major issues: none
>>
>> Minor issues: none
>>
>> Nits/editorial comments:
>>
>> - Section 5.1.1 starts with this sentence:
>>
>>    The FEC Framework Configuration Information (or FFCI) includes
>>    information that MUST be communicated between the sender and
>>    receiver(s).
>>
>> This is not a normative "MUST" that you are specifying. You are merely describing how another specification has a normative MUST, but it is not of this document. Therefore, this "MUST" should be replaced by a "need" or perhaps a "must".
>
> I understand. Done.
>
> NEW:
>     The FEC Framework Configuration Information (or FFCI) includes
>     information that must be communicated between the sender and
>     receiver(s) [RFC6363].
>
>
>> - Section 5.1.1.1 reads:
>>
>>    When SDP is used to communicate the FFCI, this FEC Encoding ID is
>>    carried in the 'encoding-id' parameter.
>>
>> Two points here:
>> a) I am missing a normative MUST, such as "this FEC Encoding ID MUST be carried..."
>> b) I guess it would not be such a bad idea to complete the sentence with the attribute name in SDP and normative reference that defines the attribute and the parameter.
>>
>> Proposal:
>>
>>    When SDP is used to communicate the FFCI, this FEC Encoding ID MUST be
>>    carried in the 'encoding-id' parameter of the  'fec-repair-flow'
>>    attribute specified in RFC 6364 [RFC6364].
>
> Excellent. This paragraph now reads:
>
> NEW:
>     When SDP is used to communicate the FFCI, this FEC Encoding ID MUST
>     be carried in the 'encoding-id' parameter of the 'fec-repair-flow'
>     attribute specified in RFC 6364 [RFC6364].
>
>
>> - Similarly in Section 5.1.1.2:
>>
>> If you agree with this changes, you should do similar changes to Section 5.1.1.2, the text beginning with "When SDP is used..." Notice also that the example following this text in Section 5.1.1.2 is misleading because it does not contain a single SDP line, which is generally considered the atomic representation element in examples, but just a fraction of it. I suggest to extend the example to the full a=fec-repair-flow line.
>
> Done. And the associated example also illustrates the use of encoding-id=...
>
> NEW:
>     When SDP is used to communicate the FFCI, this FEC scheme-specific
>     information MUST be carried in the 'fssi' parameter of the 'fec-
>     repair-flow' attribute, in textual representation as specified in RFC
>     6364 [RFC6364].  For instance:
>
>     a=fec-repair-flow: encoding-id=XXX; fssi=E:1400,S:0,m:8
>
>
>> - Section 8, IANA. Isn't the name of the registry "Reliable Multicast Transport (RMT) FEC Encoding IDs and FEC Instance IDs"? Or am I looking at the wrong registry? I think that the "FEC Framework (FECFRAME) FEC Encoding IDs is one of the registries included under that umbrella of RMT FEC Encoding IDs. As a reader, I would like to be able to find the right registry without doubt.
>
> Yes, it is one of the registries of the "Reliable Multicast Transport (RMT) FEC Encoding IDs and FEC Instance IDs" registry.
> It's a bit complex (well, historical in fact). I have clarified.
>
> NEW:
>     Values of FEC Encoding IDs are subject to IANA registration.
>     [RFC6363] defines general guidelines on IANA considerations.  In
>     particular it defines the "FEC Framework (FECFRAME) FEC Encoding IDs"
>     subregistry of the "Reliable Multicast Transport (RMT) FEC Encoding
>     IDs and FEC Instance IDs" registry, whose values are granted on an
>     IETF Consensus basis.
>
>
> Thanks a lot.
> Cheers,
>
>      Vincent, on behalf of the authors
>

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

From ben@nostrum.com  Tue Oct 23 15:06:14 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 CBDA01F0424; Tue, 23 Oct 2012 15:06:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.59
X-Spam-Level: 
X-Spam-Status: No, score=-102.59 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 05MVDloJu4zb; Tue, 23 Oct 2012 15:06:14 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id BFDD81F0C9C; Tue, 23 Oct 2012 15:06:13 -0700 (PDT)
Received: from [10.0.1.12] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id q9NM6CPt051092 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 23 Oct 2012 17:06:13 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Date: Tue, 23 Oct 2012 17:06:15 -0500
Message-Id: <5D777775-C4B8-4AEF-A445-D38EF47B0AD1@nostrum.com>
To: draft-leiba-extended-doc-shepherd-all@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
Received-SPF: pass (nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
Subject: [Gen-art] Gen-ART LC Review of draft-leiba-extended-doc-shepherd-00
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, 23 Oct 2012 22:06: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-leiba-extended-doc-shepherd-00

Reviewer: Ben Campbell
Review Date: 2012-10-23
IETF LC End Date: 2012-10-23

Summary: I'm not sure what to make of this draft. I think the opinions =
herein are worth capturing, but have mixed feelings about it belong in =
an informational RFC.

Major issues:

-- Process: I share some of the concerns that have been mentioned by =
others, namely that I'm not sure whether an individual opinion paper =
should be published as an informational RFC. OTOH, I'm not sure that it =
shouldn't. The operative words here are "I'm not sure." The opinions =
contained in the document are interesting, and likely of use to the =
community. I just wonder if another publication form might not be more =
appropriate.

-- Content: It's hard to disagree with most of the activities in =
general, but it seems to me that much of the pre pubreq processes here =
are just things that Chairs should be doing anyway. I guess it doesn't =
hurt to call all of that "shepherding", but I don't think it's the same =
thing as "having a shepherd" in the PROTO sense.  I see the potential =
value of having continuity of responsibility throughout the entire =
process, but I also see value in the flexibility of deferring the =
shepherd selection until time for the proto writeup. (I recognize that =
you don't necessarily expect the same person to shepherd all phases--but =
if I read correctly you also seem to indicate a preference that they do =
so.)

Minor issues:

-- section 1, 4th paragraph: "It adds to what=92s in RFC 4858, intending =
to extend it, not replace it."

Do you intend this to formally update 4858? It doesn't seem like it from =
the rest of the text, but one might infer otherwise from this sentence.

-- section 4, 2nd paragraph: "... What it all boils down to is setting =
up one person who takes responsibility for following the progress of a =
document from Call for Adoption through Publication ..."

The text offers examples of changing the responsible person during the =
process, but also mentions the advantages of continuity. If continuity =
is the real goal, then are the examples that show the role changing over =
the life of the draft are counterproductive?


Nits/editorial comments:

None.=

From ben@nostrum.com  Tue Oct 23 15:07:48 2012
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FC6B1F0C96; Tue, 23 Oct 2012 15:07:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.59
X-Spam-Level: 
X-Spam-Status: No, score=-102.59 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2NxH8WFEovrg; Tue, 23 Oct 2012 15:07:48 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 753821F0424; Tue, 23 Oct 2012 15:07:45 -0700 (PDT)
Received: from [10.0.1.12] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id q9NM7heR051231 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 23 Oct 2012 17:07:43 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Date: Tue, 23 Oct 2012 17:07:45 -0500
Message-Id: <8414B0C3-C97E-4A1A-8F21-6387E85C8D84@nostrum.com>
To: draft-leiba-extended-doc-shepherd.all@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
Received-SPF: pass (nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
Subject: [Gen-art] Gen-ART LC Review of draft-leiba-extended-doc-shepherd-00
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, 23 Oct 2012 22:07:48 -0000

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

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

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

Document:  draft-leiba-extended-doc-shepherd-00

Reviewer: Ben Campbell
Review Date: 2012-10-23
IETF LC End Date: 2012-10-23

Summary: I'm not sure what to make of this draft. I think the opinions =
herein are worth capturing, but have mixed feelings about it belong in =
an informational RFC.

Major issues:

-- Process: I share some of the concerns that have been mentioned by =
others, namely that I'm not sure whether an individual opinion paper =
should be published as an informational RFC. OTOH, I'm not sure that it =
shouldn't. The operative words here are "I'm not sure." The opinions =
contained in the document are interesting, and likely of use to the =
community. I just wonder if another publication form might not be more =
appropriate.

-- Content: It's hard to disagree with most of the activities in =
general, but it seems to me that much of the pre pubreq processes here =
are just things that Chairs should be doing anyway. I guess it doesn't =
hurt to call all of that "shepherding", but I don't think it's the same =
thing as "having a shepherd" in the PROTO sense.  I see the potential =
value of having continuity of responsibility throughout the entire =
process, but I also see value in the flexibility of deferring the =
shepherd selection until time for the proto writeup. (I recognize that =
you don't necessarily expect the same person to shepherd all phases--but =
if I read correctly you also seem to indicate a preference that they do =
so.)

Minor issues:

-- section 1, 4th paragraph: "It adds to what=92s in RFC 4858, intending =
to extend it, not replace it."

Do you intend this to formally update 4858? It doesn't seem like it from =
the rest of the text, but one might infer otherwise from this sentence.

-- section 4, 2nd paragraph: "... What it all boils down to is setting =
up one person who takes responsibility for following the progress of a =
document from Call for Adoption through Publication ..."

The text offers examples of changing the responsible person during the =
process, but also mentions the advantages of continuity. If continuity =
is the real goal, then are the examples that show the role changing over =
the life of the draft are counterproductive?


Nits/editorial comments:

None.=

From kathleen.moriarty@emc.com  Thu Oct 25 13:36:28 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 483D021F88CA; Thu, 25 Oct 2012 13:36:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lxHdQOxyy6AU; Thu, 25 Oct 2012 13:36:27 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 73A7521F8829; Thu, 25 Oct 2012 13:36:27 -0700 (PDT)
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 q9PKaPiY031608 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 25 Oct 2012 16:36:25 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.130]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Thu, 25 Oct 2012 16:36:03 -0400
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 q9PKa2OM025024; Thu, 25 Oct 2012 16:36:02 -0400
Received: from mx15a.corp.emc.com ([169.254.1.83]) by mxhub21.corp.emc.com ([128.222.70.133]) with mapi; Thu, 25 Oct 2012 16:36:02 -0400
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-gont-intarea-obsolete-eid-option.all@tools.ietf.org" <draft-gont-intarea-obsolete-eid-option.all@tools.ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Date: Thu, 25 Oct 2012 16:36:01 -0400
Thread-Topic: Gen-art review of draft-gont-intarea-obsolete-eid-option-01
Thread-Index: Ac2y8FijuUx3W+T7THW0XKh0yMuSaw==
Message-ID: <182B306DD37FAD4882AB1C1EBE2CA9020DCDDF9129@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "fgont@si6networks.com" <fgont@si6networks.com>
Subject: [Gen-art] Gen-art review of draft-gont-intarea-obsolete-eid-option-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, 25 Oct 2012 20:36:28 -0000

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

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

Document:  draft-gont-intarea-obsolete-eid-option-01
Reviewer: Kathleen Moriarty
Review Date: 10/25/12
IETF LC End Date: 11/1/12
IESG Telechat date: (if known)

Summary:  The document needs a few small revisions.
This document formally deprecates the IPv6 Endpoint Identification (EID) op=
tion (hex value 0x8a).

Major issues:

Minor issues:
RFC2119 is referenced, but not used.  I don't see the use of any RFC2119 la=
nguage in the document, so it may be safe to remove this reference.

I don't think the reference for EID option is valid.  I also looked at the =
reference in the IANA page and that no longer contains a link.  From a goog=
le search, it looks like this was an internet draft that was never publishe=
d as an RFC and expired, http://ana-3.lcs.mit.edu/~jnc/nimrod/eidoption.txt
Listing it as "A work in progress" when it is an expired draft s not approp=
riate.

Nits/editorial comments:

I recommend changing the following portion of the abstract to state what is=
 accomplished in this draft as the language is a little confusing:
"possibly serving as a basis for providing advice"
Since this draft doesn't actually provide the advice, just says it may prov=
ide a basis for providing the advice, I would recommend leaving this out of=
 the abstract.

Recommend removing "e.g." fromt he last sentence int he Security Considerat=
ions section as it is not needed.
Change from:
"However, formally deprecating this option
   may serve as a basis for e.g. providing advice about filtering
   packets containing such option (in a similar way to
   [I-D.ietf-opsec-ip-options-filtering] for the IPv4 case)."
TO:
"However, formally deprecating this option
   may serve as a basis for providing advice about filtering
   packets containing such option (in a similar way to
   [I-D.ietf-opsec-ip-options-filtering] for the IPv4 case)."


Thank you,
Kathleen=

From mahoney@nostrum.com  Thu Oct 25 14:49:09 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 39C7221F84F1 for <gen-art@ietfa.amsl.com>; Thu, 25 Oct 2012 14:49:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.593
X-Spam-Level: 
X-Spam-Status: No, score=-2.593 tagged_above=-999 required=5 tests=[AWL=0.007,  BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gLa5UPlxC5Zo for <gen-art@ietfa.amsl.com>; Thu, 25 Oct 2012 14:49:08 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 9468E21F847D for <gen-art@ietf.org>; Thu, 25 Oct 2012 14:49:08 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-57-93-208.dllstx.fios.verizon.net [173.57.93.208]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id q9PLmw1J064820 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 25 Oct 2012 16:49:03 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <5089B3CA.5080505@nostrum.com>
Date: Thu, 25 Oct 2012 16:48:58 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:15.0) Gecko/20120907 Thunderbird/15.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.93.208 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2012-10-25
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, 25 Oct 2012 21:49:09 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end        Draft

Ben Campbell      2012-11-19 draft-ietf-karp-routing-tcp-analysis-05

Brian Carpenter   2012-11-09 draft-ietf-mpls-ipv6-pw-lsp-ping-03 *

Richard Barnes    2012-11-02    draft-ietf-pkix-caa-15 *, **

Suresh Krishnan   2012-11-09 draft-ietf-mpls-mldp-in-band-signaling-07 *

* On the 2012-11-15 telechat

** 2nd last call


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

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


The standard template is included below.

Thanks,

Jean

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

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

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

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

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

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

From rbonica@juniper.net  Fri Oct 26 06:47:11 2012
Return-Path: <rbonica@juniper.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB62621F85B4; Fri, 26 Oct 2012 06:47:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.402
X-Spam-Level: 
X-Spam-Status: No, score=-103.402 tagged_above=-999 required=5 tests=[AWL=-1.935, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_RAND_6=2, UNRESOLVED_TEMPLATE=3.132, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G+pSDN7lda2s; Fri, 26 Oct 2012 06:47:11 -0700 (PDT)
Received: from exprod7og122.obsmtp.com (exprod7og122.obsmtp.com [64.18.2.22]) by ietfa.amsl.com (Postfix) with ESMTP id 2F01521F85B3; Fri, 26 Oct 2012 06:47:11 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob122.postini.com ([64.18.6.12]) with SMTP ID DSNKUIqUXt6mGdp2azMEczkq7rbTebroGeFo@postini.com; Fri, 26 Oct 2012 06:47:11 PDT
Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 26 Oct 2012 06:46:35 -0700
Received: from o365mail.juniper.net (207.17.137.149) by o365mail.juniper.net (172.24.192.60) with Microsoft SMTP Server id 14.1.355.2; Fri, 26 Oct 2012 06:46:34 -0700
Received: from ch1outboundpool.messaging.microsoft.com (216.32.181.181) by o365mail.juniper.net (207.17.137.149) with Microsoft SMTP Server (TLS) id 14.1.355.2; Fri, 26 Oct 2012 06:48:37 -0700
Received: from mail69-ch1-R.bigfish.com (10.43.68.233) by CH1EHSOBE018.bigfish.com (10.43.70.68) with Microsoft SMTP Server id 14.1.225.23; Fri, 26 Oct 2012 13:46:32 +0000
Received: from mail69-ch1 (localhost [127.0.0.1])	by mail69-ch1-R.bigfish.com (Postfix) with ESMTP id C16D31C00F4; Fri, 26 Oct 2012 13:46:32 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.245.197; KIP:(null); UIP:(null); (null); H:CH1PRD0511HT002.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -29
X-BigFish: PS-29(zzbb2dI9371I542M1432I1447Izz1202h1d1ah1d2ahzz1033IL17326ah8275bh8275dhz2dh2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh1155h)
Received: from mail69-ch1 (localhost.localdomain [127.0.0.1]) by mail69-ch1 (MessageSwitch) id 1351259190745524_30222; Fri, 26 Oct 2012 13:46:30 +0000 (UTC)
Received: from CH1EHSMHS001.bigfish.com (snatpool2.int.messaging.microsoft.com [10.43.68.239])	by mail69-ch1.bigfish.com (Postfix) with ESMTP id A893B2E0088;	Fri, 26 Oct 2012 13:46:30 +0000 (UTC)
Received: from CH1PRD0511HT002.namprd05.prod.outlook.com (157.56.245.197) by CH1EHSMHS001.bigfish.com (10.43.70.1) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 26 Oct 2012 13:46:29 +0000
Received: from CH1PRD0511MB418.namprd05.prod.outlook.com ([169.254.9.10]) by CH1PRD0511HT002.namprd05.prod.outlook.com ([10.255.159.37]) with mapi id 14.16.0224.004; Fri, 26 Oct 2012 13:46:28 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "draft-gont-intarea-obsolete-eid-option.all@tools.ietf.org" <draft-gont-intarea-obsolete-eid-option.all@tools.ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Thread-Topic: Gen-art review of draft-gont-intarea-obsolete-eid-option-01
Thread-Index: Ac2y8FijuUx3W+T7THW0XKh0yMuSawAj9yYw
Date: Fri, 26 Oct 2012 13:46:27 +0000
Message-ID: <2CF4CB03E2AA464BA0982EC92A02CE2502CD94@CH1PRD0511MB418.namprd05.prod.outlook.com>
References: <182B306DD37FAD4882AB1C1EBE2CA9020DCDDF9129@MX15A.corp.emc.com>
In-Reply-To: <182B306DD37FAD4882AB1C1EBE2CA9020DCDDF9129@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.232.2]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%EMC.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%TOOLS.IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%SI6NETWORKS.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
Cc: "fgont@si6networks.com" <fgont@si6networks.com>
Subject: Re: [Gen-art] Gen-art review of draft-gont-intarea-obsolete-eid-option-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: Fri, 26 Oct 2012 13:47:12 -0000

Thanks for these comments. They have all been addressed by means of an RFC =
editor note.

                                             Ron


> -----Original Message-----
> From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of
> Moriarty, Kathleen
> Sent: Thursday, October 25, 2012 4:36 PM
> To: gen-art@ietf.org; draft-gont-intarea-obsolete-eid-
> option.all@tools.ietf.org; iesg@ietf.org
> Cc: fgont@si6networks.com
> Subject: Gen-art review of draft-gont-intarea-obsolete-eid-option-01
>=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-gont-intarea-obsolete-eid-option-01
> Reviewer: Kathleen Moriarty
> Review Date: 10/25/12
> IETF LC End Date: 11/1/12
> IESG Telechat date: (if known)
>=20
> Summary:  The document needs a few small revisions.
> This document formally deprecates the IPv6 Endpoint Identification
> (EID) option (hex value 0x8a).
>=20
> Major issues:
>=20
> Minor issues:
> RFC2119 is referenced, but not used.  I don't see the use of any
> RFC2119 language in the document, so it may be safe to remove this
> reference.
>=20
> I don't think the reference for EID option is valid.  I also looked at
> the reference in the IANA page and that no longer contains a link.
> From a google search, it looks like this was an internet draft that was
> never published as an RFC and expired, http://ana-
> 3.lcs.mit.edu/~jnc/nimrod/eidoption.txt
> Listing it as "A work in progress" when it is an expired draft s not
> appropriate.
>=20
> Nits/editorial comments:
>=20
> I recommend changing the following portion of the abstract to state
> what is accomplished in this draft as the language is a little
> confusing:
> "possibly serving as a basis for providing advice"
> Since this draft doesn't actually provide the advice, just says it may
> provide a basis for providing the advice, I would recommend leaving
> this out of the abstract.
>=20
> Recommend removing "e.g." fromt he last sentence int he Security
> Considerations section as it is not needed.
> Change from:
> "However, formally deprecating this option
>    may serve as a basis for e.g. providing advice about filtering
>    packets containing such option (in a similar way to
>    [I-D.ietf-opsec-ip-options-filtering] for the IPv4 case)."
> TO:
> "However, formally deprecating this option
>    may serve as a basis for providing advice about filtering
>    packets containing such option (in a similar way to
>    [I-D.ietf-opsec-ip-options-filtering] for the IPv4 case)."
>=20
>=20
> Thank you,
> Kathleen


From brian.e.carpenter@gmail.com  Tue Oct 30 04:02:05 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F91721F850A for <gen-art@ietfa.amsl.com>; Tue, 30 Oct 2012 04:02:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HAE6oTQawVpg for <gen-art@ietfa.amsl.com>; Tue, 30 Oct 2012 04:02:05 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id D0D0A21F84E7 for <gen-art@ietf.org>; Tue, 30 Oct 2012 04:02:04 -0700 (PDT)
Received: by mail-bk0-f44.google.com with SMTP id jc3so86417bkc.31 for <gen-art@ietf.org>; Tue, 30 Oct 2012 04:02:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type; bh=TmxXpCb/GYJgstqsVzwq/BJ4lK/UsG3BlJhB/OcNaYQ=; b=MDvkM4mOuSf0V0bjePf7bFnDtjKeMPGCP2qQ6W3rsVfZuryLkBLZ3N6ANw/m9DGQ0o DeJKr0TEpWMvFYdFyP6B3N60hJKe4D/oxzphct7uK+IV/zMjqwQsSbsh/t+VVuHWsBkv Fmsfq6A1PJ0f+UydRYcPycL9AI0wp+I6DauOxuSgReeUaxO66Ggq18FL35ZFJGwz1eFF CqhmSr/tvITK1IUMMZQ4Wxum8ruVtoIs4XIjAR22dZ1eMT+X1xTFkOeJxXhe7jVuaR83 v7wAr/kRL59GytpMOfd3AO1BahN3wnT2TYmnDYXRK8Kg/IrIBZcmsSYjvSaWK4muLJni oP3g==
Received: by 10.204.11.213 with SMTP id u21mr9892999bku.42.1351594923770; Tue, 30 Oct 2012 04:02:03 -0700 (PDT)
Received: from [128.232.110.79] (c079.al.cl.cam.ac.uk. [128.232.110.79]) by mx.google.com with ESMTPS id x13sm545875bkv.16.2012.10.30.04.02.02 (version=SSLv3 cipher=OTHER); Tue, 30 Oct 2012 04:02:02 -0700 (PDT)
Message-ID: <508FB3B0.6070903@gmail.com>
Date: Tue, 30 Oct 2012 11:02:08 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: draft-ietf-mpls-ipv6-pw-lsp-ping.all@tools.ietf.org,  General Area Review Team <gen-art@ietf.org>
Content-Type: multipart/mixed; boundary="------------070903030501050201050906"
Subject: [Gen-art] Gen-ART LC review of draft-ietf-mpls-ipv6-pw-lsp-ping-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: Tue, 30 Oct 2012 11:02:05 -0000

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

Please see attached review.

     Brian


--------------070903030501050201050906
Content-Type: text/plain;
 name="draft-ietf-mpls-ipv6-pw-lsp-ping-03-carpenter.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="draft-ietf-mpls-ipv6-pw-lsp-ping-03-carpenter.txt"

SSBhbSB0aGUgYXNzaWduZWQgR2VuLUFSVCByZXZpZXdlciBmb3IgdGhpcyBkcmFmdC4gRm9y
IGJhY2tncm91bmQgb24NCkdlbi1BUlQsIHBsZWFzZSBzZWUgdGhlIEZBUSBhdA0KPGh0dHA6
Ly93aWtpLnRvb2xzLmlldGYub3JnL2FyZWEvZ2VuL3RyYWMvd2lraS9HZW5BcnRmYXE+Lg0K
DQpQbGVhc2UgcmVzb2x2ZSB0aGVzZSBjb21tZW50cyBhbG9uZyB3aXRoIGFueSBvdGhlciBM
YXN0IENhbGwgY29tbWVudHMNCnlvdSBtYXkgcmVjZWl2ZS4NCg0KRG9jdW1lbnQ6IGRyYWZ0
LWlldGYtbXBscy1pcHY2LXB3LWxzcC1waW5nLTAzLnR4dA0KUmV2aWV3ZXI6IEJyaWFuIENh
cnBlbnRlcg0KUmV2aWV3IERhdGU6IDIwMTItMTAtMzANCklFVEYgTEMgRW5kIERhdGU6IDIw
MTItMTEtMDkNCklFU0cgVGVsZWNoYXQgZGF0ZTogMjAxMi0xMS0xNQ0KDQpTdW1tYXJ5OiAg
UmVhZHkNCi0tLS0tLS0tDQoNCkNvbW1lbnQ6ICBJIGNhbid0IGZpbmQgYW55dGhpbmcgdG8g
Y29tbWVudCBvbiENCi0tLS0tLS0t
--------------070903030501050201050906--

From cpignata@cisco.com  Tue Oct 30 04:04:49 2012
Return-Path: <cpignata@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 DD11B21F850D for <gen-art@ietfa.amsl.com>; Tue, 30 Oct 2012 04:04:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ttgN4mTRKhCR for <gen-art@ietfa.amsl.com>; Tue, 30 Oct 2012 04:04:48 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 5E42A21F8511 for <gen-art@ietf.org>; Tue, 30 Oct 2012 04:04:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=289; q=dns/txt; s=iport; t=1351595088; x=1352804688; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=hpqwBDYgHqu+ZddWmPEHWzU9446YYkDkkMGYkWK2qUE=; b=i6rUSDpToICCRgOTTXifHORd49V+j593BXox2JNh0OIRe8c+Ivq/HvRe bl9hL6p9Sh0AtMuKJlXaRH3A2mDXxO7D2VGrjoppXraEev4v9Sj8EvVPO 1uGMm7Ina3HKSdc4cyE9/0lWoXxDLn4k06mHIKiSWIkBSAB55GXEq/8rX I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AggFALqzj1CtJXHB/2dsb2JhbABEhVG9ZIEIgh4BAQEDARIBJz8FCwIBCDYQIRElAgQOBSKHUgMJBpxhj2eGTg2JVIsOZ4V8YQOUH4FVizGDJoFrgm8
X-IronPort-AV: E=Sophos;i="4.80,679,1344211200"; d="scan'208";a="136835228"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-7.cisco.com with ESMTP; 30 Oct 2012 11:04:47 +0000
Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id q9UB4lCJ002955 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 30 Oct 2012 11:04:47 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.217]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.02.0318.001; Tue, 30 Oct 2012 06:04:47 -0500
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Thread-Topic: Gen-ART LC review of draft-ietf-mpls-ipv6-pw-lsp-ping-03.txt
Thread-Index: AQHNto4Tyk2WLBppQEmYolxTVG/C6JfRr6LM
Date: Tue, 30 Oct 2012 11:04:46 +0000
Message-ID: <5FBE122B-CC9D-44A7-8DE4-F387FCCE65B9@cisco.com>
References: <508FB3B0.6070903@gmail.com>
In-Reply-To: <508FB3B0.6070903@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19320.004
x-tm-as-result: No--31.251000-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-ietf-mpls-ipv6-pw-lsp-ping.all@tools.ietf.org" <draft-ietf-mpls-ipv6-pw-lsp-ping.all@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-mpls-ipv6-pw-lsp-ping-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: Tue, 30 Oct 2012 11:04:50 -0000

Thank you, Brian!

Thumb typed by Carlos Pignataro.
Excuze typofraphicak errows

On Oct 30, 2012, at 7:02 AM, "Brian E Carpenter" <brian.e.carpenter@gmail.c=
om> wrote:

> Please see attached review.
>=20
>     Brian
>=20
> <draft-ietf-mpls-ipv6-pw-lsp-ping-03-carpenter.txt>

From meral.shirazipour@ericsson.com  Wed Oct 31 21:10:54 2012
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01DFD21F8581 for <gen-art@ietfa.amsl.com>; Wed, 31 Oct 2012 21:10:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e7gcVSjlvcgx for <gen-art@ietfa.amsl.com>; Wed, 31 Oct 2012 21:10:53 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 56F6F21F843B for <gen-art@ietf.org>; Wed, 31 Oct 2012 21:10:53 -0700 (PDT)
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 qA14F0Lm026963; Wed, 31 Oct 2012 23:15:01 -0500
Received: from EUSAAHC002.ericsson.se (147.117.188.78) by eusaamw0707.eamcs.ericsson.se (147.117.20.32) with Microsoft SMTP Server (TLS) id 8.3.279.1; Thu, 1 Nov 2012 00:10:46 -0400
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC002.ericsson.se ([147.117.188.78]) with mapi id 14.02.0318.001; Thu, 1 Nov 2012 00:10:45 -0400
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Last Call review of RFC5011
Thread-Index: Ac235tR/ZLwYAWKpT52fsFDnc4Y2jQ==
Date: Thu, 1 Nov 2012 04:10:45 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939AD5C5@EUSAAMB107.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.135]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dnsext-chairs@tools.ietf.org" <dnsext-chairs@tools.ietf.org>, "mstjohns@comcast.net" <mstjohns@comcast.net>
Subject: [Gen-art] Gen-ART Last Call review of RFC5011
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, 01 Nov 2012 04:10:54 -0000

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

Please resolve any Last Call comments you may receive.

Document: RFC5011
Reviewer: Meral Shirazipour
Review Date: 2012-10-31
IETF LC End Date: 2012-11-02
IESG Telechat date: -


Summary: This RFC is ready for publication as an Internet Standard.

Comment: All my comments are already answered by http://www.ietf.org/mail-a=
rchive/web/ietf-announce/current/msg10765.html =20


Best Regards,
Meral
---
Meral Shirazipour
Ericsson Research
www.ericsson.com
