Re: [IPsec] AD review of draft-ietf-ipsecme-ad-vpn-problem

Vishwas Manral <vishwas.ietf@gmail.com> Tue, 29 January 2013 19:47 UTC

Return-Path: <vishwas.ietf@gmail.com>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00E1B21F85C3 for <ipsec@ietfa.amsl.com>; Tue, 29 Jan 2013 11:47:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.632
X-Spam-Level:
X-Spam-Status: No, score=-1.632 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_LOW=-1, SARE_HTML_USL_OBFU=1.666]
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 HXz6slkbpxkt for <ipsec@ietfa.amsl.com>; Tue, 29 Jan 2013 11:47:16 -0800 (PST)
Received: from mail-qa0-f41.google.com (mail-qa0-f41.google.com [209.85.216.41]) by ietfa.amsl.com (Postfix) with ESMTP id 2302521F85D4 for <ipsec@ietf.org>; Tue, 29 Jan 2013 11:47:16 -0800 (PST)
Received: by mail-qa0-f41.google.com with SMTP id hy16so1835740qab.14 for <ipsec@ietf.org>; Tue, 29 Jan 2013 11:47:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=3E9ddiMAku+RiFrVqSaNlQlPvvIz5ud+vvsNwCctTts=; b=gEAD/5GXGdtKQ/dNV8LzcZgM4L7qM/wSjuMKc5oAeJNXeay6x6YIVI9NJx/UQTXJOG h4ihBPysVeZq2P1V3aYQVOfCC2dDC+ZJmUazVfOhmIzQ9avkIhZV4kSzS6ys6Elx6Ekw 6rO/6P2yewqKsGBiewYch8uXA9iJY2ONJTi2aEGCDN7lol38FD+DCU2FOraE9qMhfO8g 8ATFQpDbPurUi8EqQqiu2uU2T+7Cjk73Xl7n0U/SZX5P5V5P7oHJ3OaUgtzZUKznaVwD e87El+LBF23F7TQqGiSku9xCJzWi88v7EsDDfbhqO98lrChG6K4QMnlm7+9Lx1subZAg 7+RQ==
MIME-Version: 1.0
X-Received: by 10.224.199.70 with SMTP id er6mr2401781qab.19.1359488831128; Tue, 29 Jan 2013 11:47:11 -0800 (PST)
Received: by 10.229.92.77 with HTTP; Tue, 29 Jan 2013 11:47:11 -0800 (PST)
In-Reply-To: <50ED7C03.7090303@ieca.com>
References: <50ED7C03.7090303@ieca.com>
Date: Tue, 29 Jan 2013 11:47:11 -0800
Message-ID: <CAOyVPHSykFG=c_C8QNJUr_ZQdfUzx+iiXm1uWh+egHA-GLj=nA@mail.gmail.com>
From: Vishwas Manral <vishwas.ietf@gmail.com>
To: Sean Turner <turners@ieca.com>
Content-Type: multipart/alternative; boundary="20cf30050e8adb040d04d472a823"
Cc: ipsec@ietf.org, draft-ietf-ipsecme-ad-vpn-problem@tools.ietf.org
Subject: Re: [IPsec] AD review of draft-ietf-ipsecme-ad-vpn-problem
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipsec>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jan 2013 19:47:17 -0000

Hi Sean,

I realized I missed this email. I will work on this draft this week and
next.

Thanks,
Vishwas
On Wed, Jan 9, 2013 at 6:17 AM, Sean Turner <turners@ieca.com> wrote:

> These are pretty much just nits.  Please address Tero's comments as well.
>
> 1. We charter WGs and I'm going to go with the thought that it will
> succeed ;)
>
> a: r/is chartered to/will
>
> 2. s1.1: Hub definition.
>
> Verb choice:
>
> r/there is no devices/there are no devices
>
> 3. s1.1.: Spoke definition:
>
> Extra the:
>
> r/in the a star/in a star
>
> Need some ses:
>
> r/it encrypt data coming from cleartext device
>  /it encrypts data coming from cleartext devices
>
> 4. s2: Use administrative domain in s1 but organization here.  Is
> consistency needed?
>
> Not sure what you'd think about this, but what do you think about not
> using lowercase 2119 words in any of the s2 subsections?  Reviewers should
> be able to piece together that this is the use case section and not the
> requirements section and therefore there shouldn't be any 2119 language
> here - but they don't always.  To be clear, I'm not hard over on this.
>
> r/must use/need
> r/must/need to
> r/should/ought to
>
> 5. s2.1:
>
> Can you remove direct from "direct, point-to-point"?  Isn't direct in the
> definition?
>
> Shouldn't "hub and spoke topology" be "star topology"?  "hub and spoke
> topology" isn't defined in s1.1.
>
> I think you might need an "a" to match the previous sentence:
>
> r/Such use case/Such a use case ?
>
> r/expose them/expose themselves
>
> 6. s2.2:
>
> An extra the:
>
> r/for the voice and other/for voice and other
>
> Nit picking here but I think this is clearer:
>
> r/endpoints are administrated by separate management domains
>  /endpoints are in different administrative domains
>
> Please expand: L3VPNs and GRE.
>
> 7. s4.1:
>
> r/firewall, NAT box/firewalls, NAT boxes
>
> 8. Req 10 + 11: Is the requirement driver under 11 for both 10 and 11? If
> so then it should be "These requirements".  If you're going to do this
> couldn't you just group 10-14 as they're the same driver for all 5? Or, is
> the driver under 10 missing?
>
> 9 s5: To match the title:
>
> r/Problem state and requirement/problem statement and requirements
>
> 10. General: Sometimes it's ADVPN and other times it's AD VPN.
>
> 11. Allied and federated environments should be defined in the terminology
> section or at least introduced earlier in the draft.
>
> spt
> ______________________________**_________________
> IPsec mailing list
> IPsec@ietf.org
> https://www.ietf.org/mailman/**listinfo/ipsec<https://www.ietf.org/mailman/listinfo/ipsec>
>