Re: [shara] First draft of the shara use cases for review

marcelo bagnulo braun <marcelo@it.uc3m.es> Thu, 19 March 2009 17:10 UTC

Return-Path: <marcelo@it.uc3m.es>
X-Original-To: shara@core3.amsl.com
Delivered-To: shara@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C6B8B3A6B63 for <shara@core3.amsl.com>; Thu, 19 Mar 2009 10:10:21 -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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SGaQXXC8yMhn for <shara@core3.amsl.com>; Thu, 19 Mar 2009 10:10:20 -0700 (PDT)
Received: from smtp02.uc3m.es (smtp02.uc3m.es [163.117.176.132]) by core3.amsl.com (Postfix) with ESMTP id 721813A687F for <shara@ietf.org>; Thu, 19 Mar 2009 10:10:20 -0700 (PDT)
Received: from marcelo-bagnulos-macbook-pro.local (13.pool85-53-142.dynamic.orange.es [85.53.142.13]) by smtp02.uc3m.es (Postfix) with ESMTP id 17A916BAB9C; Thu, 19 Mar 2009 18:11:04 +0100 (CET)
Message-ID: <49C27CA6.1070703@it.uc3m.es>
Date: Thu, 19 Mar 2009 18:11:02 +0100
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: mohamed.boucadair@orange-ftgroup.com
References: <49BEB0D2.6080700@it.uc3m.es> <6CF039C5B32037498B02251E11CDE6B007DB7B84@ftrdmel3>
In-Reply-To: <6CF039C5B32037498B02251E11CDE6B007DB7B84@ftrdmel3>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-TM-AS-Product-Ver: IMSS-7.0.0.3116-5.6.0.1016-16528.007
Cc: shara@ietf.org
Subject: Re: [shara] First draft of the shara use cases for review
X-BeenThere: shara@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Sharing of an IPv4 Address discussion list <shara.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shara>, <mailto:shara-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shara>
List-Post: <mailto:shara@ietf.org>
List-Help: <mailto:shara-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shara>, <mailto:shara-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Mar 2009 17:10:21 -0000

Hi,

thanks for the comments


mohamed.boucadair@orange-ftgroup.com escribió:
> Dear Marcelo, all
>
> Thank you for these slides. Please find below some comments:
>
> - Slide 4: 
> 1/ To avoid confusion with overlapped port ranges, I suggest to have something like (IP1, PR1), (IP1, PR2) etc, assigned to port restricted devices instead of P1...P2, P2...P2 notation. 
>   
done

> 2/ Port Range Router is not **necessarily** connected to what you call "rest of Internet IPv4".
>   
It, is by definition of the Rest of the Internet :-)
No, more seriously, I basically was including there all the rest of the 
IP world, so, by definition, it is connected to the rest of the 
internet. But i understand that you find this confusing somehow. If you 
explain what  bothers you, i can try to fix it.
> 3/ What is the role of the two represented PRRs? 
>
> - Slide 5: Idem as slide 4
>
>   
I understand that you have a hierarchy of Port routers, so that a port 
router on the top of the hierarchy delegates a  port raneg to another 
port router, which in turn delegated sub ranges of this initial port 
range to other port routers or to port resticted nats or to end hosts, 
and that is what i want to describe by including multiple port routers 
and the tunnel technology between them... makes sense?

> - Slide 7: 
> 1/ Why you need a tunnel between represented two routers? 
>
>
>   
see the answer above

> FYI, additional IPv6-related use cases are defined in draft-boucadair-behave-ipv6-portrange-01. Two modes are defined: encapsulation and translation mode:
>   
AFAIU, the encapsulation mode is covered in Use case #2 and the 
translation mode is covered in Use case #3
I mean, in use case #2, IPv4 over IPv6 tunnels are considered and in the 
use case#3 we cover the case where the IPv6 client wants to connect to 
an IPv4 server.

I agree that the NAT64 function can be located in different parts of the 
network, but i understand than the closer we keep the nat function tothe 
customer, the better.

Do you think i am missing something?

Regards, marcelo
PS: Updated slides with the modification and slide number to facilitate 
comments have been posted
http://www.ietf.org/proceedings/09mar/slides/shara-0.pdf

Regards, marcelo



> The encapsulation mode uses a stateless function called SMAP (Stateless A+P Mapping). A SMAP function may be embedded in a PRR or a port restricted device. A port restricted device may be a CPE, PDA, terminal, etc. I reproduce hereafter these use cases:
>
> - Use IPv6 for incoming traffic destined to a shared IP address. No alteration is required for outgoing traffic.
>
>                   +----------+
>          --IPv4---|----------|------------IPv4--------------------\
>          ---------|----------|------------------------------------/
>                   |          |
>                   | +------+ |               +------+
>                   | |      | | /----IPv6-----|      |
>          /--IPv4--| | SMAP | |//---IPv4----  | SMAP |/---IPv4----
>          \--------| |      | |\\-----------  |      |\-----------
>                   | |      | | \-------------|      |
>                   | +------+ |               +------+
>                   |          |
>                   +----------+
>                      node A                    node B
>
> - IPv6 is used in both directions
>
>                        +------+             +------+
>                        |      |----IPv6---\ |      |
>            ----IPv4---\|      |----IPv4---\\|      |----IPv4---\
>            -----------/|      |-----------//|      |-----------/
>                        |      |-----------/ |      |
>                        | SMAP |             | SMAP |
>                        |      | /----IPv6---|      |
>            /---IPv4----|      |//---IPv4----|      |/---IPv4----
>            \-----------|      |\\-----------|      |\-----------
>                        |      | \-----------|      |
>                        +------+             +------+
>                         node A               node B
>
> Two interconnection scenarios may be envisaged as listed below:
>
> - Interconnection scenario 1:
>
> +------+           +------+   +--------+   +------+           +------+
> |      |--IPv6---\ |      |   |        |   |      |---IPv6--\ |      |
> |      |--IPv4---\\|      |---|-IPv4---|--\|      |---IPv4--\\|      |
> |      |---------//|      |---|--------|--/|      |---------//|      |
> |      |---------/ |      |   |Internet|   |      |---------/ |      |
> | SMAP |           | SMAP |   |  IPv4  |   | SMAP |           | SMAP |
> |      | /---IPv6--|      |   |        |   |      | /---IPv6--|      |
> |      |//---IPv4--|      |/--|-IPv4---|---|      |//--IPv4---|      |
> |      |\\---------|      |\--|--------|---|      |\\---------|      |
> |      | \---------|      |   |        |   |      | \---------|      |
> +------+           +------+   +--------+   +------+           +------+
>   Source            node A                  node B           Destination
>
>
> - Interconnection scenario 2:
>
>    +------+             +------------+              +------+
>    |      |             |            |              |      |
>    |      |----IPv6-----|----IPv6----|----IPv6----\ |      |
>    |      |----IPv4-----|------------|----IPv4----\\|      |
>    |      |-------------|------------|------------//|      |
>    |      |-------------|------------|------------/ |      |
>    | SMAP |             | Internet v6|              | SMAP |
>    |      | /-----IPv6--|------------|-----IPv6-----|      |
>    |      |//---IPv4----|------------|-------IPv4---|      |
>    |      |\\-----------|------------|--------------|      |
>    |      | \-----------|------------|--------------|      |
>    |      |             |            |              |      |
>    +------+             +------------+              +------+
>     Source                                            Destination
>
> Cheers
> Med
>  
>
> -----Message d'origine-----
> De : shara-bounces@ietf.org [mailto:shara-bounces@ietf.org] De la part de marcelo bagnulo braun
> Envoyé : lundi 16 mars 2009 21:05
> À : shara@ietf.org
> Objet : [shara] First draft of the shara use cases for review
>
> Hi,
>
> I have done a first version of the slides describing the SHARA use cases Find them at:
> http://www.ietf.org/proceedings/09mar/slides/shara-0.pdf
>
> Comments are welcome.
> The suppose to reflect the recent disucssion on scenarios on the ml
>
> Regards, marcelo
>
> _______________________________________________
> shara mailing list
> shara@ietf.org
> https://www.ietf.org/mailman/listinfo/shara
>
>