Re: [renum] Working Group Last Call: draft-ietf-6renum-gap-analysis-03.txt

Marc Lampo <marc.lampo.ietf@gmail.com> Tue, 18 September 2012 07:54 UTC

Return-Path: <marc.lampo.ietf@gmail.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9245521F847A for <renum@ietfa.amsl.com>; Tue, 18 Sep 2012 00:54:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Huh1r6y+Jb8b for <renum@ietfa.amsl.com>; Tue, 18 Sep 2012 00:54:35 -0700 (PDT)
Received: from mail-qc0-f194.google.com (mail-qc0-f194.google.com [209.85.216.194]) by ietfa.amsl.com (Postfix) with ESMTP id B330221F8476 for <renum@ietf.org>; Tue, 18 Sep 2012 00:54:35 -0700 (PDT)
Received: by qcbb18 with SMTP id b18so2309922qcb.1 for <renum@ietf.org>; Tue, 18 Sep 2012 00:54:35 -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 :cc:content-type:content-transfer-encoding; bh=uMv46bcojMTzokYJN2dKFxtIiXF6ovimVKKuCFxMkZ0=; b=Ymps9KYnhrxuWVWt3OksBUG3v/iGw9KcKKqVnjSn57kVO5ITUzzusSzzFBd753nwD9 FlSoyoQ0KXkZJv2qK7Gf2/8GV1osVaDx5DejoeM5MyXmvQDqfzkS3BQVgrJ8nSDLsgkf A33okR7zMU6Jb51m4xANqAh45zD7BF2mmKgVkoEKAF+hTt0ZhTkQogfPsdFVbZxAI1rC fy5JhKBi91wdnRv5ULISml8j99xXH1KZnADHKl0/4p+leK3jE7QdDSJMrZdiZblTd/4F v43INBrDjlhnaDxkK8IvVY3tOY2sgIsnAikGhE8oEqvek8qO/8FgZyHyKM2gNlSvuuoj 5gYA==
MIME-Version: 1.0
Received: by 10.229.137.18 with SMTP id u18mr9108557qct.20.1347954875046; Tue, 18 Sep 2012 00:54:35 -0700 (PDT)
Received: by 10.49.133.195 with HTTP; Tue, 18 Sep 2012 00:54:34 -0700 (PDT)
In-Reply-To: <99B887114EDB1449941CFBC8EC279FA12CB43E09@PRVPEXVS17.corp.twcable.com>
References: <99B887114EDB1449941CFBC8EC279FA12CB43E09@PRVPEXVS17.corp.twcable.com>
Date: Tue, 18 Sep 2012 09:54:34 +0200
Message-ID: <CAB0C4xOdmHpTN2hVY6R4MAeGZU4kKruMuL0u1wPFgqCkXAsbzg@mail.gmail.com>
From: Marc Lampo <marc.lampo.ietf@gmail.com>
To: "Howard, Lee" <lee.howard@twcable.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: "renum@ietf.org" <renum@ietf.org>
Subject: Re: [renum] Working Group Last Call: draft-ietf-6renum-gap-analysis-03.txt
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Sep 2012 07:54:36 -0000

Hello (and sorry to jump in so late, but as I just changed employer ...),

my remark is about impact of renumbering on IPSEC VPN definitions.
In my opinion this area is not addressed (enough).

I understand that, via a reference to RFC5887 these is a suggestion to
define addresses on either side of an IPSEC VPN via DNS.
One element is that in practice, not all devices "out there" (some
very widely used) are not capable of defining the valid addresses on
an IPSEC endpoint via DNS.

The second element is about the DNS aspect itself.
Suppose there is a site-to-site VPN between organisations A and B.
Suppose organisation A is capable of defining "valid addresses behind
VPN endpoint" via DNS.
Problem is that device at organisation A needs access to a NS that
"knows" about internal addresses at organisation B.
But if organisation B renumbers its internal network !
How can DNS server accessible/used by VPN endpoint at organisation A
know about new addresses in an automatic way ?


Because there is so little about this subject, in the present version,
I think it is not addressed enough.
Either explicitly, in a paragraph firmly stating recommendations and procedures;
or in section 9, Gaps considered unresolvable, where it can be added
why this is a problem and what admins will have to do manually, if
they renumber.


Kind regards,

Marc Lampo

On Thu, Sep 6, 2012 at 6:17 PM, Howard, Lee <lee.howard@twcable.com> wrote:
> We are requesting a Working Group Last Call on this document.  Please review and provide comments before September 19, since this may be the final review of this document.
>
> Thanks,
>
> Lee
>
>
>> -----Original Message-----
>> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf
>> Of internet- drafts@ietf.org
>> Sent: Monday, September 03, 2012 11:38 PM
>> To: i-d-announce@ietf.org
>> Cc: renum@ietf.org
>> Subject: [renum] I-D Action: draft-ietf-6renum-gap-analysis-03.txt
>>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>>  This draft is a work item of the IPv6 Site Renumbering Working Group of the IETF.
>>
>>       Title           : IPv6 Site Renumbering Gap Analysis
>>       Author(s)       : Bing Liu
>>                           Sheng Jiang
>>                           Brian Carpenter
>>                           Stig Venaas
>>       Filename        : draft-ietf-6renum-gap-analysis-03.txt
>>       Pages           : 20
>>       Date            : 2012-09-03
>>
>> Abstract:
>>    This document briefly introduces the existing mechanisms could be
>>    utilized by IPv6 site renumbering and tries to cover most of the
>>    explicit issues and requirements of IPv6 renumbering. Through the gap
>>    analysis, the document provides a basis for future works that
>>    identify and develop solutions or to stimulate such development as
>>    appropriate. The gap analysis is presented following a renumbering
>>    event procedure clue.
>>
>>
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-6renum-gap-analysis
>>
>> There's also a htmlized version available at:
>> http://tools.ietf.org/html/draft-ietf-6renum-gap-analysis-03
>>
>> A diff from the previous version is available at:
>> http://www.ietf.org/rfcdiff?url2=draft-ietf-6renum-gap-analysis-03
>>
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> renum mailing list
>> renum@ietf.org
>> https://www.ietf.org/mailman/listinfo/renum
>
> Lee Howard
> Director, Network Technology
> Time Warner Cable
> (703) 345-3513
> 13820 Sunrise Valley Drive, Herndon VA 20171
>
>
>
> This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum