Re: [Softwires] Provisioning Hub-and-spoke in MAP - How?

Rémi Després <despres.remi@laposte.net> Tue, 10 April 2012 10:01 UTC

Return-Path: <despres.remi@laposte.net>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4F6E21F883E for <softwires@ietfa.amsl.com>; Tue, 10 Apr 2012 03:01:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.17
X-Spam-Level:
X-Spam-Status: No, score=-2.17 tagged_above=-999 required=5 tests=[AWL=0.128, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uvje4JHVRRSu for <softwires@ietfa.amsl.com>; Tue, 10 Apr 2012 03:01:30 -0700 (PDT)
Received: from smtpout.laposte.net (smtpout1.laposte.net [193.253.67.226]) by ietfa.amsl.com (Postfix) with ESMTP id B76B721F881A for <softwires@ietf.org>; Tue, 10 Apr 2012 03:01:29 -0700 (PDT)
Received: from [192.168.0.21] ([88.166.221.144]) by mwinf8502-out with ME id wA1P1i00F37Y3f403A1Qj5; Tue, 10 Apr 2012 12:01:28 +0200
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary="Apple-Mail-49--737401646"
From: Rémi Després <despres.remi@laposte.net>
In-Reply-To: <CAFFjW4jAzOVbGQCQy+TyqA6V1c2ca3BN9yMrCu3fbQgcAfMBkg@mail.gmail.com>
Date: Tue, 10 Apr 2012 12:01:23 +0200
Message-Id: <54550967-246A-45E3-9E78-D6633A8A2CE1@laposte.net>
References: <B3BD62F0-364C-4BCA-B1CF-5F103388471B@cisco.com> <87158690-27BE-4777-B70E-5991DEDEA78C@laposte.net> <CAFFjW4jAzOVbGQCQy+TyqA6V1c2ca3BN9yMrCu3fbQgcAfMBkg@mail.gmail.com>
To: Wojciech Dec <wdec.ietf@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Softwires WG <softwires@ietf.org>, int-ads@tools.ietf.org, Softwire Chairs <softwire-chairs@tools.ietf.org>
Subject: Re: [Softwires] Provisioning Hub-and-spoke in MAP - How?
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Apr 2012 10:01:31 -0000

Wojciech,

This isn't answers to questions I asked.
They remain open.

RD

Le 2012-04-10 à 11:51, Wojciech Dec a écrit :

> Remi,
> 
> you're apparently confusing matters. There is no need to have a DHCPv6 option, or a million node deployment to test MAP implementations. DS-lite is a good example, with implementations and standards track before the DHCPv6 option.
> 
> Needless to say, if you're implying that tests of MAP without testing the standards based DHCPv6 option are insufficient, then any test of 4rd-u or anything for that matter without using the fully standards DHCP option would be equally flawed. 
> At the very least however, MAP does not need to prove on thing: Compatibility with IPv6, which 4rd-u would need to.
> 
> -Woj.
> 
> On 10 April 2012 11:37, Rémi Després <despres.remi@laposte.net> wrote:
> Hello, all,
> 
> We have heard many times that MAP is completely specified, and has been extensively tested.
> Yet:
> - mapping rules of tested configurations have not been provided
> - several missing points of the MAP-T+E specification have been identified (ref (*) www.ietf.org/mail-archive/web/softwires/current/msg04049.html)
> 
> This mail is just about ONE of these, the hub-and-spoke issue.
> It has been discussed several times but AFAIK still without a complete answer.
> 
> The difficulty is that:
> - The MAP-DHCPv6 draft has no parameter to indicate whether the ISP-chosen topology is mesh or hub-and-spoke.
> - According to the MAP-address-and-port draft, "each MAP node in the domain has the same set of rules".
> - As answered in the mail below, the choice "needs to be provisioned. either explicitly or implicitly (via the rules)".
> 
> Questions I have are then:
> - Is the choice provisioned explicitly, implicitly, or possibly both?
> - How?
> - Which tests have confirmed that it worked?
> 
> Answer by any one who asserts he or she understands how MAP works will be welcome.
> 
> Thanks,
> RD
> 
> 
> 
> 
> 
> 
> 
> > De : Ole Trøan <ot@cisco.com>
> > Date : 2012-03-14 14:29
> > À : Rémi Després <despres.remi@laposte.net>
> > Cc : Tomasz Mrugalski <tomasz.mrugalski@gmail.com>, Softwires WG <softwires@ietf.org>
> > Objet : Rép : [Softwires] Question about hub-and-spoke operation in MAP
> >
> > Remi,
> >
> >> I couldn't figure out by how CEs can be required to work hub-and-spoke without some DHCPv6 indication:
> >> - If two CEs apply the same BMR to their delegated IPv6 prefixes, how do they know whether their ISP expects direct paths between them (mesh) or BR hairpinning (hub-and-spoke)?
> >>
> >
> > that's correct it needs to be provisioned. either explicitly or implicitly (via the rules).
> >
> > cheers,
> > Ole
> 
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>