IETF Logo Mail Archive

Re: [v6ops] draft-xiao-v6ops-nd-deployment-guidelines

Chongfeng XIE <xiechf@chinatelecom.cn> Mon, 27 June 2022 13:26 UTC

Return-Path: <xiechf@chinatelecom.cn>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA15DC14F73A for <v6ops@ietfa.amsl.com>; Mon, 27 Jun 2022 06:26:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wnlJc78LHO7b for <v6ops@ietfa.amsl.com>; Mon, 27 Jun 2022 06:26:04 -0700 (PDT)
Received: from chinatelecom.cn (prt-mail.chinatelecom.cn [42.123.76.228]) by ietfa.amsl.com (Postfix) with ESMTP id D3B5FC14F738 for <v6ops@ietf.org>; Mon, 27 Jun 2022 06:26:02 -0700 (PDT)
HMM_SOURCE_IP: 172.18.0.188:35328.556535582
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_TYPE: SMTP
Received: from clientip-114.250.176.130 (unknown [172.18.0.188]) by chinatelecom.cn (HERMES) with SMTP id 3D7BD280029; Mon, 27 Jun 2022 21:25:57 +0800 (CST)
X-189-SAVE-TO-SEND: 66040161@chinatelecom.cn
Received: from ([172.18.0.188]) by app0023 with ESMTP id c61aa513e1634ffeae164e566f230a9f for xipengxiao=40huawei.com@dmarc.ietf.org; Mon, 27 Jun 2022 21:25:59 CST
X-Transaction-ID: c61aa513e1634ffeae164e566f230a9f
X-Real-From: xiechf@chinatelecom.cn
X-Receive-IP: 172.18.0.188
X-MEDUSA-Status: 0
Sender: xiechf@chinatelecom.cn
Date: Mon, 27 Jun 2022 21:25:58 +0800
From: Chongfeng XIE <xiechf@chinatelecom.cn>
To: Xipengxiao <xipengxiao=40huawei.com@dmarc.ietf.org>, "fredbaker.ietf" <fredbaker.ietf@gmail.com>, list <v6ops@ietf.org>
References: <CABKBHwfbSb3zsWqB1-_SfktSWdzU1oVWgBk1RqBborW7rMoJsg@mail.gmail.com>, <3211bc43c94a428f91893bdc8cebfc4a@huawei.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.2.23.121[cn]
Mime-Version: 1.0
Message-ID: <2022062721255777237036@chinatelecom.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart501003326774_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/M0GnFI11LMzcEvKIFrsd2xuw1yw>
Subject: Re: [v6ops] draft-xiao-v6ops-nd-deployment-guidelines
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jun 2022 13:26:08 -0000

Hi， Xipeng,

In section 5, there is the following statement,
             
      "MBB and FBB will end at Step 1.a: isolating hosts in L2 and in subnet, with MBBv6 as the solution with SLAAC and FBBv6 as the solution with DHCPv6, respectively;"

I have two questions,
1) What are the fist-hop in MBB and FBB respectively? As far as I know, in FBB, the link from user terminal to the edge equipment, such as BNG, comprises two segments, the segment from user terminal to home gateway and the segment from home gateway to the BNG.  But In MBB, generally there is only one hop between user terminal and the edge of the network, such as PGW/UPF,  in some cases, the mobile user terminal may play a hotsport to provide access service to other termianls.  I think the illustration of the ND solution should be in combination with the network architecture.

2) The second question may be related to the first one, why MBBv6 uses SLAAC but FBBv6 use DHCPv6, for the  isolation hosts in L2 and in subnet? As far as I know, SLAAC has been widely used in FBB too, and it can allocate different prefixes for different users, so as to provide some kind of isolation.

Best regards
Chongfeng  



xiechf@chinatelecom.cn
 
From: Xipengxiao
Date: 2022-06-27 06:43
To: Fred Baker; v6ops list
Subject: Re: [v6ops] draft-xiao-v6ops-nd-deployment-guidelines
Hi folks,
 
We will post another new version this week.  Please wait for that.  Thank you.
 
XiPeng 
 
From: v6ops <v6ops-bounces@ietf.org> On Behalf Of Fred Baker
Sent: Sunday, June 26, 2022 8:00 PM
To: v6ops list <v6ops@ietf.org>
Subject: [v6ops] draft-xiao-v6ops-nd-deployment-guidelines
 
With this email, let me invite commentary on draft-xiao-v6ops-nd-deployment-guidelines. Please read the draft and raise any issues you might have with it.

v2.23.0 | Report a Bug | By Email