Re: [Autoconf] Summary of topologies and addressing discussed recently
HyungJin Lim <dream.hjlim@gmail.com> Tue, 03 March 2009 16:20 UTC
Return-Path: <dream.hjlim@gmail.com>
X-Original-To: autoconf@core3.amsl.com
Delivered-To: autoconf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 684FD28C1AC for <autoconf@core3.amsl.com>; Tue, 3 Mar 2009 08:20:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.373
X-Spam-Level:
X-Spam-Status: No, score=-1.373 tagged_above=-999 required=5 tests=[AWL=-1.075, BAYES_00=-2.599, HTML_MESSAGE=0.001, MANGLED_LIST=2.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pfaJX86IQ-fC for <autoconf@core3.amsl.com>; Tue, 3 Mar 2009 08:20:36 -0800 (PST)
Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.191]) by core3.amsl.com (Postfix) with ESMTP id CBFFE3A6835 for <Autoconf@ietf.org>; Tue, 3 Mar 2009 08:20:35 -0800 (PST)
Received: by ti-out-0910.google.com with SMTP id 11so3097602tim.25 for <Autoconf@ietf.org>; Tue, 03 Mar 2009 08:21:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=7ZYP2hmOtOhYSVDQjac22T7F7ZRp0e3kKLXd8s+Zpk0=; b=Cj4qdzjPm7fa1ih0vuDBfFsV8/Qh15XgPnaAnljyXUxg/0EygleS91UVQL22c9dvNr qlUp0HF1zCFPg0X+DWI1bimHME6TiYiaOLkrj3hoCkUuXJESc1QlKkQJlqcWKLV5i28w FpkfzXj275/gQAiqoPvzUIxVQZItF7CLMr1Hg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=RH2/zg3Z5ti/VKIuvpcs+i3Mg/NUSy4zIZhvIpAJZ0vW1wRTZSHbTkVEHP8EXpU9J4 f7SwDtCFEMZtFTsfB85zBwYzC7Ig3+9Tpq9HT0AIt45g/CSvOGMVuBE7gQj6AVRBIjj7 x0taxUQMP3vXrufNzaXtFxkydcwJnL0rwC4Yc=
MIME-Version: 1.0
Received: by 10.110.95.11 with SMTP id s11mr10620902tib.24.1236097258216; Tue, 03 Mar 2009 08:20:58 -0800 (PST)
In-Reply-To: <49AD55AB.5040304@gmail.com>
References: <49AD55AB.5040304@gmail.com>
Date: Wed, 04 Mar 2009 01:20:58 +0900
Message-ID: <7e8d02d40903030820o728288c4l11dc7db8f5d1c02b@mail.gmail.com>
From: HyungJin Lim <dream.hjlim@gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Content-Type: multipart/alternative; boundary="0016e64e9300fbdc6c0464395163"
Cc: Autoconf@ietf.org
Subject: Re: [Autoconf] Summary of topologies and addressing discussed recently
X-BeenThere: autoconf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Ad-Hoc Network Autoconfiguration WG discussion list <autoconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/autoconf>, <mailto:autoconf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/autoconf>
List-Post: <mailto:autoconf@ietf.org>
List-Help: <mailto:autoconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/autoconf>, <mailto:autoconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Mar 2009 16:20:38 -0000
Hi, Alex I think we should identify the impacts from address model we can choice. for example, whether packet forwarding or packet routing. The packet routing needs a satisfied route distributed time. While the packet forwarding needs additional processing time for tunneling. What do we should choice for proper address model? I don't think only simplest scenario is important. Thanks Hyung-Jin, Lim 2009/3/4 Alexandru Petrescu <alexandru.petrescu@gmail.com> > Dear AUTOCONFers, > > Recently there was discussion on the mailing list about topologies and > addressing for AUTOCONF. Some topologies for AUTOCONF were named and > classified as: > -only-MANET > -MANET-to-Internet and > -MANET-to-MANET-to-Internet (three or more levels) > -MANET-to-Internet-to-MANET > > Some topologies were pictured in more detail - they're listed below as > a summary. Some participants seemed to agree on these topologies or > on some of their variations. > > A simple topology: > > ----- wifi "adhoc1" ------ wifi "adhoc2" ----- > |Host1|---------------|Router|---------------|Host2| > ----- LL1 LL2 ------ LL3 LL4 ----- > G1 G4 > > > "adhoc1" and "adhoc2": 802.11 ESSIDs in "ad-hoc" mode. > Each is an IPv6 subnet. > LL1...4: IPv6 link-local addresses. > Self-formed according to rfc2464. > G1, G4: IPv6 global addresses, for example > 2001:db8:1::1/64 and > 2001:db8:2::4/64 > Manually assigned, or pre-configured with SNMP > or formed according to stateless autoconf rfc4862; > the prefixes are advertised by Router in RAs. > > > A simple topology with Routers: > > ------- wifi "adhoc1" ------- wifi "adhoc2" ------- > |Router1|---------------|Router2|---------------|Router3| > ------ LL1 LL2 -------LL3 LL4 ------- > G1 G4 > > G1, G4: ? > > > More details on the simple topology with Routers, /64 prefixes and > /128 addresses: > > ----- wifi "adhoc1" ------ wifi "adhoc2" ----- > |Host1|---------------|Router|---------------|Host2| > ----- LL1 P1 LL2 ------ LL3 P2 LL4 ----- > G1 G4 > > G1, G4: IPv6 global addresses, for example > 2001:db8:1::1/128 and > 2001:db8:2::4/128 > Manually assigned, or pre-configured with SNMP > or formed according to stateless autoconf rfc4862; > the prefixes are advertised by Router in RAs. > P1, P2: IPv6 global prefixes, for example > 2001:db8:1::/64 and > 2001:db8:2::/64 > Manually assigned, or pre-configured with SNMP. > > Connecting it to Internet: > > ----- wifi "adhoc1" ------ wifi "adhoc2" -------- / > |Host1|---------------|Router|---------------|Gatewway|---| Internet > ----- LL1 LL2 ------ LL3 LL4 -------- \ > G1 G4 > > > "adhoc1" and "adhoc2": 802.11 ESSIDs in "ad-hoc" mode. > Each is an IPv6 subnet. > LL1...4: IPv6 link-local addresses. > Self-formed according to rfc2464. > G1, G4: ? > > > Connecting it to Internet via a Satellite link: > > ------ wifi "adhoc1" ------ wifi "adhoc2" -------- Satelite / > |NEMOMR|---------------|Router|---------------|Gatewway|--------Int'net > ------ LL1 LL2 ------ LL3 LL4 -------- TCA1 \ > G1 G4 > > LL1...4: IPv6 link-local addresses. > Self-formed according to rfc2464. > G1: address formed by NEMOMR either from RA sent by Router, or > by DHCPv6 considering Router is a DHCPRelay and Gateway is > a DHCPServer. > G4: ? > TCA: Topologically-Correct Address, for Gateway. It can be > manually configured on Gateway, or DHCP, or stateless > autoconf. > > > > In the multi-hop network below only /64 prefixes are present in > Routers' routing tables, no /128 (host-based) routes: > > > ----- wifi "adhoc1" ------ wifi "adhoc2" ------- "adhoc3"----- > |Host1|---------------|Router|---------------|Router2|-------|Host2| > ----- LL1 P1 LL2 ------ LL3 P2 LL4 -------LL5 P3 LL6--- > G1 G4 > > P1, P2, P3: /64 prefixes, such as: > 2001:db8:1::/64 > 2001:db8:2::/64 and > 2001:db8:3::/64 > > > Breaking the connectivity: > > ------- wifi "adhoc1" ----- ???? ----- "adhoc2" -------- > |Router1|---------------|Host1|--/ /--|Host2|---------|Router2| > ------- LL2 P1 LL1 --- ----LL6 P2 LL6------ > G1 G4 > > Adding more interfaces of different types: > > Router1 and Router2 are out of range. So R1 <--> H2 and H1 <--> R2. > Host1 MUST communicate to Host2, this is critical (live or dead). > > +-------+ wifi "adhoc1" +-------+ wifi "adhoc2" +-------+ > |Router1|>-------------<|Router2|>-------------<|Router3| > +---L---+ LL1 LL21 +---L---+ LL22 LL3 +---L---+ > |M1 |M2 |M3 > > "adhoc1" and "adhoc2": 802.11 SSIDs in "IBSS" mode. > Each IBSS is an IPv6 subnet. > > L: Loopback interface. > > >, <: MANET interface. > > LL1, LL21, LL22, LL3: IPv6 link-local addresses. > Self-formed according to rfc2464. > > M1, M2, M3: IPv6 MANET local addresses, for example > FD01:db8::1/128, FD01:db8::2/128 and FD01:db8::3/128. > Manually assigned, or pre-configured (e.g. with SNMP) > or formed according to a to be defined [Autoconf for MANETs] > protocol, with a to-be-defined prefix (e.g. ULA, RFC4193). > > > Again connecting to the Internet, this time via an Access Router: > > Internet > | > | > +-------+-------+ > | Access Router | > +-------+-------+ > | > | | Prefix information > | V > | > +-------+ wifi "adhoc1" +---+---+ wifi "adhoc2" +-------+ > |Router1|>-------------<|Router2|>-------------<|Router3| > +---L---+ LL1 LL21 +---L---+ LL22 LL3 +---L---+ > |M1 |M2 |M3 > |G1 |G2 |G3 > <------- -------> > Prefix information Prefix information > > > G1, G2, G3: IPv6 globally unique addresses, for example > 2001:db8:G:1/128, 2001:db8:G:2/128 and 2001:db8:G:3/128. > Formed according to a to be defined [Autoconf for MANETs] > protocol, with the prefix provided by (via) the Access Router. > > > Adding Multi-homing: > > ---+-------Internet--------+--- > | | > | | > +-------+-------+ +-------+-------+ > |Access Router H| |Access Router G| > +-------+-------+ +-------+-------+ > | | > ||Prefix information H | |Prefix information G > |V | V > | | > +---+---+ wifi "adhoc1" +---+---+ wifi "adhoc2" +-------+ > |Router1|>-------------<|Router2|>-------------<|Router3| > +---L---+ LL1 LL21 +---L---+ LL22 LL3 +---L---+ > |M1 |M2 |M3 > |G1 |G2 |G3 > |H1 |H2 |H3 > <------- -------> > Prefix information G Prefix information G, H > ---------> > Prefix information H > > H1, H2, H3: IPv6 globally unique addresses, for example > 2001:db8:H:1/128, 2001:db8:H:2/128 and 2001:db8:H:3/128. > Formed according to a to be defined [Autoconf for MANETs] > protocol, with the prefix provided by (via) Access Router H. > > > Effect of some links disappearing: > > > ---+-------Internet------ > | > | > +-------+-------+ > |Access Router H| > +-------+-------+ > | > ||Prefix information H > |V wifi "adhoc1" > | <---------------------------v--------> > <------|--v----------------------> | > |<-|--------------------v-----------------------|---> > | | | | > +---+--'+ +---'---+ +---'---+ > |Router1|>-------------<|Router2|>-------------<|Router4| > +---L---+ LL1 LL21 +---L---+ LL22 LL4 +---L---+ > |M1 |M2 |M4 > |H1 |H2 |H4 > > ---------> ---------> > Prefix information H Prefix information H > > > No computer movement, but obstacle mouvement: > > (802.11 term: STA is station) > > +------------------------+ +------------------------+ > | | | | > | ____STA-B | | ____STA-B | > | ___/ | | | ___/ | > | STA-A | | | STA-A OBSTACLE | > | '--_ | | | '--_ | > | '----STA-C | | '----STA-C | > | OBSTACLE | | | > +------------------------+ +------------------------+ > 1-1: No hindrance 1-2: B-C blocked > > +------------------------+ +------------------------+ > | | | O | > | ____STA-B | | B STA-B | > | ___/ | | | S | | > | STA-A OB | | | STA-A T | | > | ST | | | A | | > | AC STA-C | | C STA-C | > | LE | | LE | > +------------------------+ +------------------------+ > 1-3: A-C blocked 1-4: A-B & A-C blocked > > MANET Scenarios with blocking obstacle > > > Compare with this one: > > (802.11 term: AP is access point) > > +------------------------+ +------------------------+ > | | | | > | ____STA-B | | ____STA-B | > | ___/ | | ___/ | > | AP-A | | AP-A OBSTACLE | > | '--_ | | '--_ | > | '----STA-C | | '----STA-C | > | OBSTACLE | | | > +------------------------+ +------------------------+ > 4-1: No hindrance 4-2: No hindrance > > +------------------------+ +------------------------+ > | | | O | > | ____STA-B | | B STA-B | > | ___/ | | S | > | AP-A OB | | AP-A T | > | ST | | A | > | AC STA-C | | C STA-C | > | LE | | LE | > +------------------------+ +------------------------+ > 4-3: A-C & B-C blocked 4-4: All blocked > > 802.11 BSS L2 topology with blocking obstacle > > > |HAving them pictured, may I ask you: do you think anything will ever be > |able to communicate through Obstacles? > > > Yes, of course. > > > +------------------------+ +------------------------+ > | | | | > | ____STA-B | | ____STA-B | > | ___/ 1 | | | ___/ 1 . | > | STA-A | 1 | | STA-A obstacle 5 | > | '--_ 1 | | | '--_ 1 . | > | '----STA-C | | '----STA-C | > | obstacle | | | > +------------------------+ +------------------------+ > 2-1: No hindrance 2-2: B-C degraded > > +------------------------+ +------------------------+ > | | | o | > | ____STA-B | | 5 b ...STA-B | > | ___/ 1 | | | ...s. | | > | STA-A ob | 1 | | STA-A t | 1 | > | ... st | | | ...a. | | > | 5 .ac..STA-C | | 5 c ...STA-C | > | le | | le | > +------------------------+ +------------------------+ > 2-3: A-C degraded 2-4: A-B & A-C degraded > > Scenarios with degrading obstacle > > > I depicted the metrics: 1 is good, 5 is degraded. > > Here the routing tables, with metrics: > > ROUTER DEST NEXTHOP METRIC ROUTER DEST NEXTHOP METRIC > +-------+-------+-------+------+ +-------+-------+-------+------+ > | A | B | B | 1 | | A | B | B | 1 | > | | C | C | 1 | | | C | C | 1 | > +-------+-------+-------+------+ +-------+-------+-------+------+ > | B | A | A | 1 | | B | A | A | 1 | > | | C | C | 1 | | | C | C | 5 | > +-------+-------+-------+------+ +-------+-------+-------+------+ > | C | A | A | 1 | | C | A | A | 1 | > | | B | B | 1 | | | B | B | 5 | > +-------+-------+-------+------+ +-------+-------+-------+------+ > 11-1: No hindrance 11-2: B-C is degraded > > +-------+-------+-------+------+ +-------+-------+-------+------+ > | A | B | B | 1 | | A | B | B | 5 | > | | C | C | 5 | | | C | C | 5 | > +-------+-------+-------+------+ +-------+-------+-------+------+ > | B | A | A | 1 | | B | A | A | 5 | > | | C | C | 1 | | | C | C | 1 | > +-------+-------+-------+------+ +-------+-------+-------+------+ > | C | A | A | 5 | | C | A | A | 5 | > | | B | B | 1 | | | B | B | 1 | > +-------+-------+-------+------+ +-------+-------+-------+------+ > 11-3: A-C degraded 11-4: A-B & A-C degraded > > Alex thanking the participants. > > _______________________________________________ > Autoconf mailing list > Autoconf@ietf.org > https://www.ietf.org/mailman/listinfo/autoconf >
- Re: [Autoconf] Summary of topologies and addressi… Alexandru Petrescu
- [Autoconf] Summary of topologies and addressing d… Alexandru Petrescu
- Re: [Autoconf] Summary of topologies and addressi… HyungJin Lim