IETF Logo Mail Archive

Re: [v6ops] IPv10 Discussion in v6ops

Khaled Omar <eng.khaled.omar@outlook.com> Mon, 14 September 2020 12:56 UTC

Return-Path: <eng.khaled.omar@outlook.com>
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 439DB3A08C7 for <v6ops@ietfa.amsl.com>; Mon, 14 Sep 2020 05:56:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=outlook.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 6JRby-__I8lL for <v6ops@ietfa.amsl.com>; Mon, 14 Sep 2020 05:56:00 -0700 (PDT)
Received: from EUR06-DB8-obe.outbound.protection.outlook.com (mail-db8eur06olkn2048.outbound.protection.outlook.com [40.92.51.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B28B63A0813 for <v6ops@ietf.org>; Mon, 14 Sep 2020 05:55:59 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=UQuu59LIuDnXAvX3Oxb0zaJlOvwwt3oJhsgpPX/Cs2U+WOaSm0HGnLiHn575Ta5Z9UghxFW3HFU2laElckaytfdk7qqcIukYzy2UvPAromSN0fxFIivZp4Gk/3gjUJXPYedZ40ybInttM3bYsX4eRdV0NplnGJfMl2J7mBm6j0pHEm+XGAjTY+9zvNYBD/URZ66rrc+Uir1oUk8ZaFKq6A7w95yxoQgyBVlVtrVnBSNXVZReHzzvzgbCFQWtbYuI3RZkf1pSwoVZkA7wc2lpgxaMeF/2EfVE5yZEq/0JYDgngAPub/nrCic3F3HxdnrR2J99IbfT6G/Uxbmi3gXvDA==
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=to6DjD8zaMuwnkLucHGwo3sDf00l8Ov1CfbLk7hgMys=; b=f4TldAy47QZyUnwxfgobUxGw+VHRWJ4g7/rMB4RgVvi47w9miyKeebtyRxaKAHSY4JUXl012Rwek4D4WxXgyLvE+OvBM4Y2w5Nnir4Jz2XCSyI3lrpVAbWrC22Zbmlp1BiAJyQ7tdHmeM4hpoydkt4UCB3Zz96UMpOo1pS+rMe3Fxsl5cLKG6QEfBH1P+FFV1o7LbEqtDN70gyKsRhlZdD3PGsidl9RXSdQeq5ivJqb+PI8SHs2gCY2aFXG0evOIKTFkiw6wbDdq2t93bHrfDuqBl8VkaoI9lWn7iO0sByyJJsEpGS+DbTw6eh0XtQBsI5+6Fm9i/R+s6pmup3G+xw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=to6DjD8zaMuwnkLucHGwo3sDf00l8Ov1CfbLk7hgMys=; b=HzxkPngQ7KIgBgV7eiwBA85HT6ykomZYKldkL0WPqzGT2pNXm//03zB1LKnZaBWgaO7q0l87W5PVsC99c9Ktq1qb+VbLudiWlYgTJ1gN0HN1fIA18yqAiKaunOrNWzVC4wBgtf4uT4Q0ac4pXpk6BqLWmkgLD6y+A2DEqJhV8KAucXRLCfjaIGKy7SQ3PuVrNzCVdjKP7/dgOHPfYQuZg4Jn+70pOdyWZbl2yqXombVJ+mU37FH6wi6QIVl9yrVWvrNnXIjV49vp22CR15t1aG1Yt7DCSnhxN25Bex1f3UXNUWz1NcQqLPfXzb2kxB0D4DDlRFyCgK5h2rHzl2FZeA==
Received: from VI1EUR06FT019.eop-eur06.prod.protection.outlook.com (2a01:111:e400:fc37::4f) by VI1EUR06HT227.eop-eur06.prod.protection.outlook.com (2a01:111:e400:fc37::441) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3370.16; Mon, 14 Sep 2020 12:55:57 +0000
Received: from VI1P194MB0285.EURP194.PROD.OUTLOOK.COM (2a01:111:e400:fc37::47) by VI1EUR06FT019.mail.protection.outlook.com (2a01:111:e400:fc37::417) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3370.16 via Frontend Transport; Mon, 14 Sep 2020 12:55:57 +0000
Received: from VI1P194MB0285.EURP194.PROD.OUTLOOK.COM ([fe80::89f6:7540:e834:ffb8]) by VI1P194MB0285.EURP194.PROD.OUTLOOK.COM ([fe80::89f6:7540:e834:ffb8%5]) with mapi id 15.20.3370.019; Mon, 14 Sep 2020 12:55:57 +0000
From: Khaled Omar <eng.khaled.omar@outlook.com>
To: Fred Baker <fredbaker.ietf@gmail.com>
CC: "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: IPv10 Discussion in v6ops
Thread-Index: AQHWiT43LYhHc7LQV0ie1xfS7y0F1aloGfGQ
Date: Mon, 14 Sep 2020 12:55:56 +0000
Message-ID: <VI1P194MB028561F81F5118ABC14967DFAE230@VI1P194MB0285.EURP194.PROD.OUTLOOK.COM>
References: <159985752195.15551.2657932726923781035@ietfa.amsl.com> <VI1P194MB0285E344B7B3E9697E6ED608AE240@VI1P194MB0285.EURP194.PROD.OUTLOOK.COM> <3FA82C44-0005-45BA-AB09-FAE63C8CD626@gmail.com>
In-Reply-To: <3FA82C44-0005-45BA-AB09-FAE63C8CD626@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-incomingtopheadermarker: OriginalChecksum:D015802D9E74A35CCADA1E8F2BFC6C26F0ACDD398D6464968664032F87B1E29C; UpperCasedChecksum:DBB60E73BBA337748CBDA16BBC1C3CE48F2273C40BEF24353AC16B5BD1E6497E; SizeAsReceived:2819; Count:43
x-tmn: [DZrY+Mf84vd+5AkhY8Z4Y4l9vjguysTr]
x-ms-publictraffictype: Email
x-incomingheadercount: 43
x-eopattributedmessage: 0
x-ms-office365-filtering-correlation-id: e78d52e6-812f-45f2-bba0-08d858ad85d6
x-ms-traffictypediagnostic: VI1EUR06HT227:
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: kvBMXptlnSS4hoa3SANhsqcvbbJxZD2YUqPynw9ophqs3/Guadaa4hutpnfPajONCcbWFJuMgbp2EQyIFs5/1u/AV+NuXsEWckXi4w8jXhWjBLUTYKrXXSI6AIG+k+4yMd3mvBbuDkCagj5Q7swQEfd/4ii7JJ9AEabx1NaFxJgAw1No2xacr2Czbp0ZEauRapS6PSxCpj2OdZSDKSTjDga5fvEYB0YbfNSVHrM0D/0=
x-ms-exchange-antispam-messagedata: YOehnGE10rDsGfbLw73TlNbE80Gno4Y49LT0rK45eE6dEewa8XFLltDECQmAlR3PUd6m83787XEBOiBMlIu8MImwPRqLuqhkE8m7ei8WbxEuuCrX9u0w0jx66M/EUoG4xLzcHscqTRQpCI60CP1nrQ==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-AuthSource: VI1EUR06FT019.eop-eur06.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: e78d52e6-812f-45f2-bba0-08d858ad85d6
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Sep 2020 12:55:57.0084 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1EUR06HT227
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/hUDCSR7HWhDwhLx1eUixGSOeCwg>
Subject: Re: [v6ops] IPv10 Discussion in v6ops
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 14 Sep 2020 12:56:01 -0000

Hi,

>> we generally don't consider drafts for the agenda that have not been updated since the last IETF meeting.

The IPv10 I-D is now on it best form, if you will compare the differences between a version and the other one, you will find slight minor difference, the major idea still the same.

Khaled Omar

-----Original Message-----
From: Fred Baker <fredbaker.ietf@gmail.com> 
Sent: Saturday, September 12, 2020 9:52 PM
To: Khaled Omar <eng.khaled.omar@outlook.com>
Cc: v6ops@ietf.org
Subject: IPv10 Discussion in v6ops

As is usual with requests for draft discussion in v6ops, we (the chairs) are looking for active supportive discussion of the draft on the v6ops list. I would suggest that you get the operators you are discussing the technology with to discuss their deployment on the list. Also, given that the -00 was posted in 2016, the -11 in 2018, and it has not been updated since, I would strongly suggest that you update the draft with current experience and post a revision - we generally don't consider drafts for the agenda that have not been updated since the last IETF meeting.

Section 4 ("IPv10 Packet Header Format") clearly discusses a protocol. According to the v6ops charter (https://datatracker.ietf.org/wg/v6ops/charter/), at most "the v6ops Working Group may provide input to those areas/groups, as needed, and cooperate with those areas/groups in reviewing solutions to IPv6 operational and deployment problems." What working group are you discussing this protocol in?

> On Sep 11, 2020, at 1:56 PM, Khaled Omar <eng.khaled.omar@outlook.com> wrote:
> 
> Hi V6OPS WG,
> 
> Is it possible to reserve a slot for the IPv10 I-D to be presented completely during the v6ops wg meeting session?
> 
> https://tools.ietf.org/html/draft-omar-ipv10-06
> 
> Best Regards,
> 
> Khaled Omar

v2.23.0 | Report a Bug | By Email