[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ipng
Subject:    =?utf-8?B?562U5aSNOiBIb3N0IHN1cHBvcnQ/?=
From:       "Yangfan (IP Standard)" <shirley.yangfan () huawei ! com>
Date:       2021-03-10 10:17:12
Message-ID: 137711934fd64589bf03eb04436d984c () huawei ! com
[Download RAW message or body]

All, 
There is no intention to divide an IP connection into pieces, no matter the entity is \
a host or router (or called "network edge"). Based on the use cases we have \
recognized so far, they are applications taken from operator's perspective. Thus, we \
are focusing on the associated channel used between routers. But you are right, ACH \
over IPv6 should not be limited between routers. If there is a need of control/mgmt \
messages transmitted on an IP path, ACH should fit. So the authors encourage people \
to provide more use cases, to utilize ACH thoroughly. Thanks in advance!

Cheers, 
Fan 


-----邮件原件-----
发件人: ipv6 [mailto:ipv6-bounces@ietf.org] 代表 Ola Thoresen
发送时间: 2021年3月9日 21:17
收件人: ipv6@ietf.org
主题: Re: Host support?

On 09.03.2021 13:58, Fred Baker wrote:

> I'm in the IETF 110 6man meeting, and Fan Yang just said, in Q&A following her \
> presentation, that there is no intention that ACH might be used between hosts. I'm \
> not advocating that it should be, but the prohibition surprises me. What is the \
> reason to restrict this to network nodes such as routers? 

Why are some people still differentiating between a "host" and a "router"?

My mobile phone is a router, forwarding packets between the 4G/5G network and the \
connected "internet sharing" clients.

My laptop is a router, forwarding packets between VMs, containers, the host OS, \
internet and peripherals connected over e.g. USB.

Even some of the VMs running on the laptop are actually routers, forwarding packets \
from and to other virtual instances...

And all of these changes their role dynamically, based on what application is used, \
and whenever clients are connected or disconnected, VMs and containers are created \
and destroyed...   You can't know in advance if something is a "host" or a "router", \
and whatever it is right now, might not be what it is in 5 minutes.

To restrict anything to either a "host" or a "router" in this day and age does not \
make any sense.


/Ola (T)


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------


[prev in list] [next in list] [prev in thread] [next in thread]