IETF Logo Mail Archive

Re: [ippm] Mail regarding draft-fz-6man-ipv6-alt-mark

Haoyu Song <haoyu.song@futurewei.com> Sun, 20 October 2019 21:57 UTC

Return-Path: <haoyu.song@futurewei.com>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5691D12000F; Sun, 20 Oct 2019 14:57:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RsF_ipzctqjP; Sun, 20 Oct 2019 14:57:21 -0700 (PDT)
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-eopbgr760113.outbound.protection.outlook.com [40.107.76.113]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93E3612003F; Sun, 20 Oct 2019 14:57:21 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=j+RlvYRKSMHl4N+i+rrP6dwHERJ2rH6r98G4Re1xluuATUcjEhUhvhWsRU2Itihkz+k6BHST0npQlQYAcgPCaS5TE5UZBxvxvzDoKn9Zqp10eY+cajQCNf4BIWpjCWTytlZGMPkoZbS7BG1War4fw33VWai5qH2Ciw/54w2sXOCH1Jdh2FE6QjqgiD+kbk5Z5TaJNxI/YiIec+JmYPg0T33MMF9sp3nf1tW2Zf2+bqk16JRMBJb0BEdG++TZ0kKAfRNl2hn0r2xS8fwEl27kHStZCozvGxAd+ZyOGCIuJE70/c7nGXcqd//KXfQqqTyyCh27CRtW5qlba/0TAqKdhQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=xDVs6nDEA523yJ/NpjsoRT6gnZi+65PHeu76uw6jAEU=; b=EWURzXI648zMVhzqJ6vbhSCeE1n1acWunNfgLUxgwfpxtwxCiAVbEOER+fyma9j5NhH9ofkGuFhpSZM9iXTaN9QGqrFSH7ysbDYlRmY9jY9VA6tnWmYABzo2iCDQ4ZEUVlTF4m/ksnnTiHniqj3ERtaRUxAiOvxrbmaPFpI54XQ6IYENSIVWBN3+EbEYZmelALxfhDMlen2ziJ3vxoNykjhkKymzP1nIR44hPtjSgxOwviIoV8A6J4n1QUtlXqFjr8/TiE1yT3/wRxYXfIPUwfRdfoiQNtqAqHCnEHxhHbJ1w7dnEgsskHsiOMr9fhy6NH5gwZRiqd6DfJGQ5ZNkEQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=xDVs6nDEA523yJ/NpjsoRT6gnZi+65PHeu76uw6jAEU=; b=MJkVs1i1PGdkPQRSKwHVQLhcP6t3TiFAaEl4wdLVsOINsEQYTCaRj7s1NVnRsf950wFfM5sa5d0On+Dn3VXp+hmO0lD1myxs/KxOJVup91+H9ykp44MdrMfTrc/L9qk9XOuk1h3j/3Svf5eetn37wTbc1tXkaZvCdF/NcnOx5Ww=
Received: from MN2PR13MB3582.namprd13.prod.outlook.com (10.255.239.156) by MN2PR13MB3567.namprd13.prod.outlook.com (10.255.237.202) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2387.14; Sun, 20 Oct 2019 21:57:18 +0000
Received: from MN2PR13MB3582.namprd13.prod.outlook.com ([fe80::6dcb:88a5:b3a9:e05c]) by MN2PR13MB3582.namprd13.prod.outlook.com ([fe80::6dcb:88a5:b3a9:e05c%4]) with mapi id 15.20.2387.014; Sun, 20 Oct 2019 21:57:17 +0000
From: Haoyu Song <haoyu.song@futurewei.com>
To: Tom Herbert <tom@quantonium.net>
CC: "draft-fz-6man-ipv6-alt-mark@ietf.org" <draft-fz-6man-ipv6-alt-mark@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, IETF IPPM WG <ippm@ietf.org>
Thread-Topic: [ippm] Mail regarding draft-fz-6man-ipv6-alt-mark
Thread-Index: AdWFiuts9lClw3kCQaWaKSoqvpT0FwBB466AAD+R0aA=
Date: Sun, 20 Oct 2019 21:57:17 +0000
Message-ID: <MN2PR13MB358294377356528B4D8B77C79A6E0@MN2PR13MB3582.namprd13.prod.outlook.com>
References: <MN2PR13MB35820D0A6A5E73CBB5D9DD129A6C0@MN2PR13MB3582.namprd13.prod.outlook.com> <CAPDqMeqANRZPxEswcp+=TdwgGQztgr3YS8bHH_wW4Ftfqj8YyQ@mail.gmail.com>
In-Reply-To: <CAPDqMeqANRZPxEswcp+=TdwgGQztgr3YS8bHH_wW4Ftfqj8YyQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=haoyu.song@futurewei.com;
x-originating-ip: [77.60.70.19]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 6462ec6a-d495-494c-a762-08d755a8799e
x-ms-traffictypediagnostic: MN2PR13MB3567:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <MN2PR13MB35675FC874FD4799DB175AFC9A6E0@MN2PR13MB3567.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 0196A226D1
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(366004)(376002)(136003)(396003)(39830400003)(346002)(189003)(199004)(13464003)(81156014)(11346002)(186003)(81166006)(6506007)(76176011)(7696005)(486006)(2906002)(5660300002)(53546011)(6246003)(102836004)(229853002)(476003)(66446008)(64756008)(66556008)(66476007)(26005)(4326008)(66066001)(6916009)(44832011)(8936002)(8676002)(446003)(76116006)(66946007)(7736002)(305945005)(55016002)(74316002)(6116002)(478600001)(33656002)(52536014)(256004)(54906003)(6306002)(86362001)(966005)(71200400001)(25786009)(71190400001)(316002)(45080400002)(99286004)(9686003)(6436002)(3846002)(14454004); DIR:OUT; SFP:1102; SCL:1; SRVR:MN2PR13MB3567; H:MN2PR13MB3582.namprd13.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: futurewei.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: mtK3Osv4rbeB8dKSqXYSS9nVtSCtE8Y2pQk6VomL2uJ89gMuUFOD1gH9n96ToUUfIdDa5gBTnyvuE70sqMRQM0RzNl/6WMTvOQ0NbsqoirVtcBgzp4MMriqPKmp63NdFeIjJgMGLV5i5vup79/+sJLJ1UddnBYg627zBwrzN3IqplCWVYeXzZHEx6Dh2hrizCdU6FhZ5qO73f7/8QRzsonP1NRMp7cVpneHRTf5X8MBhi2MpHkqjys+yvbWrRB3d9bF/oYUpgWAxX0fJOP/mQBpP0nTE4FeZ3Mj16AMSXkZqZ9j3fgtcOx3QTi+mZipSC54nNqvywgZst5tBpZHccSOn5l45piGoWIvUfsXWUocUexwtELNWmVBQaDUbe9GyBNZQ+MePI/JrZQZgI+mMujv4mbU5fBrLWiDjrCeZuaCd+O8BYOpuhFa71q865T0X
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 6462ec6a-d495-494c-a762-08d755a8799e
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Oct 2019 21:57:17.7123 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: MLT0wM/POa+XByHUb7FSLc6GevMQCdO59n0S0q1odkjzqaDEXF5YHqiVDprwtB6zAcmgyLP+0U3bMKTEkARvgg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR13MB3567
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/7BNdSRMKIj8wrL80fmudpzRoRI0>
Subject: Re: [ippm] Mail regarding draft-fz-6man-ipv6-alt-mark
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Oct 2019 21:57:25 -0000

inline

-----Original Message-----
From: Tom Herbert <tom@quantonium.net> 
Sent: Saturday, October 19, 2019 8:33 AM
To: Haoyu Song <haoyu.song@futurewei.com>
Cc: draft-fz-6man-ipv6-alt-mark@ietf.org; ipv6@ietf.org; IETF IPPM WG <ippm@ietf.org>
Subject: Re: [ippm] Mail regarding draft-fz-6man-ipv6-alt-mark

On Fri, Oct 18, 2019 at 1:30 AM Haoyu Song <haoyu.song@futurewei.com> wrote:
>
> I just read this draft and I think it’s an implementation of the draft [I-D.zhou-ippm-enhanced-alternate-marking], which discusses the method of encapsulating the enhanced alternate marking header in IPv6. I have several comments.
>
>
>
> It doesn’t cover the encapsulation on SRv6 yet and I think a solution for SRv6 would be more useful.

SRv6 _is_ a subset IPv6. It is one type of routing header. Like any other use case of IPv6, HBH and destination options are useable when
SRv6 header is present. Because SRv6 is a routing header destination options before the routing header are processed by each destination in the route list.

[HS] What I mean is to make it a part of SRH. Sorry I didn't make it clear. 

> More deployment consideration discussion should be given when it’s 
> encapsulated in HBH EH

In what regard?

[HS] I just think there might be some deployment issues for SRv6 EH

> The document mentioned two PBT modes discussed in [I-D.song-ippm-postcard-based-telemetry]. Since the PBT-I variation has been merged in another draft [I-D.ioamteam-ippm-ioam-direct-export], this draft may need to be updated accordingly.
>
>
>
> Thanks!
>
>
>
> Haoyu
>
> _______________________________________________
> ippm mailing list
> ippm@ietf.org
> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
> ietf.org%2Fmailman%2Flistinfo%2Fippm&amp;data=02%7C01%7Chaoyu.song%40f
> uturewei.com%7Cd8011b4323b24621feae08d754a9a4f3%7C0fee8ff2a3b240189c75
> 3a1d5591fedc%7C1%7C1%7C637070959917566910&amp;sdata=p6xgfJ1PWLLA8T%2BM
> 5%2FFu%2Fa5Hae9ulu82aTnkqHPQMc0%3D&amp;reserved=0

v2.23.0 | Report a Bug | By Email