Re: [v6ops] IPmix relevance to the v6ops Charter
Khaled Omar <eng.khaled.omar@outlook.com> Sat, 17 November 2018 22:35 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 84A97128CFD for <v6ops@ietfa.amsl.com>; Sat, 17 Nov 2018 14:35:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 ZVGaWqHNaTLz for <v6ops@ietfa.amsl.com>; Sat, 17 Nov 2018 14:35:31 -0800 (PST)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-oln040092066017.outbound.protection.outlook.com [40.92.66.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4BF77128C65 for <v6ops@ietf.org>; Sat, 17 Nov 2018 14:35:31 -0800 (PST)
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=51B+RXD1HoCFIzzQs6sghg0CdyzY5yWIUHYmNGwoevs=; b=C8iKRAJgx50b2t4lhH4dtaVhuyOO/hi5W54z3cXk239P3YIt4yJJDqOCQOrYjVf8fx92SND1N9/y29BfpXFJNCcPjSGk5CaUgnV/ngiHVGSPzydLTUeNq2I8iZSEn7NJEKHgbVH+H5D08+Q/HgA1vShqAFG+ULJQFeQiyqBWNeJinAG6QxiaUtc9uGRdosiMv+VXCovedvpom8h/2R+waksRZ3jCEv6lPynRTAlrJqCWThdVOE4V7qmE7bIrO5DYDadTiiPi8wV8XIOXwLKvCsgKtdoIq3TgR2aqf2U0cElg/15amfuCFvpewTd24D2JDBpQe96eZVGqsKMgfMurSg==
Received: from HE1EUR01FT005.eop-EUR01.prod.protection.outlook.com (10.152.0.57) by HE1EUR01HT243.eop-EUR01.prod.protection.outlook.com (10.152.1.213) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1339.10; Sat, 17 Nov 2018 22:35:28 +0000
Received: from HE1PR0402MB2937.eurprd04.prod.outlook.com (10.152.0.56) by HE1EUR01FT005.mail.protection.outlook.com (10.152.1.229) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1339.10 via Frontend Transport; Sat, 17 Nov 2018 22:35:28 +0000
Received: from HE1PR0402MB2937.eurprd04.prod.outlook.com ([fe80::952e:86d2:1940:cb70]) by HE1PR0402MB2937.eurprd04.prod.outlook.com ([fe80::952e:86d2:1940:cb70%10]) with mapi id 15.20.1294.048; Sat, 17 Nov 2018 22:35:28 +0000
From: Khaled Omar <eng.khaled.omar@outlook.com>
To: Warren Kumari <warren@kumari.net>, JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
CC: IPv6 Operations <v6ops@ietf.org>
Thread-Topic: [v6ops] IPmix relevance to the v6ops Charter
Thread-Index: AQHUfFWOeCMFu9SuJkeF/wqPFpb2f6VPumOSgAAHq4CAAAWEMIAAh8wAgADcKACAABpkgIAAJk8AgAMbDmqAAAixgIAAAwoi
Date: Sat, 17 Nov 2018 22:35:28 +0000
Message-ID: <HE1PR0402MB293738B65A5D4EE2C974B9D4AEDE0@HE1PR0402MB2937.eurprd04.prod.outlook.com>
References: <HE1PR0402MB29377F0DD1854F1786FC67ACAEC20@HE1PR0402MB2937.eurprd04.prod.outlook.com> <78c52356-7d3e-21cc-ca3e-5e237fb4d55d@kit.edu> <HE1PR0402MB293774D01A1C350A21ADC884AEC30@HE1PR0402MB2937.eurprd04.prod.outlook.com> <35BBA13C-99A4-4C6F-AA86-36CEAD0E7C57@steffann.nl> <6BB2FA5C-64A8-4856-955D-6BA21DC23C2F@gmail.com> <HE1PR0402MB29370A892824851E7A2C81B7AEC30@HE1PR0402MB2937.eurprd04.prod.outlook.com> <0AECA19F-8C28-4FC7-9135-0E9F3692C01D@gmail.com> <HE1PR0402MB2937ECE8E079D605580037B1AEC30@HE1PR0402MB2937.eurprd04.prod.outlook.com> <31880F17-1335-4DDD-9767-B41DE4369B19@gmail.com> <CAHw9_iL5uWg8uB=ySOg0R6J3BCLfKjm0Mxp-rTBsEj02yCbkig@mail.gmail.com> <HE1PR0402MB293734B5D777768DC58C3378AEDC0@HE1PR0402MB2937.eurprd04.prod.outlook.com> <CAHw9_i+2H=O6niE-LdGkpQh_QmX+SthRqJ5Xes9K9n5v7=k5zg@mail.gmail.com> <HE1PR0402MB29374C3B82BBF20A20613041AEDE0@HE1PR0402MB2937.eurprd04.prod.outlook.com>, <973B856E-1919-47C1-BA5B-311AB5B05E55@consulintel.es>
In-Reply-To: <973B856E-1919-47C1-BA5B-311AB5B05E55@consulintel.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-incomingtopheadermarker: OriginalChecksum:856FD42BEC490A49E302951C9E54E10EA93DF0F70777F68CEFC0EF4DE054B322; UpperCasedChecksum:4DB0CE243357842864B320591A49A79F56EF1131586DA29022C2C46AE3EC75F7; SizeAsReceived:8118; Count:47
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [ePe/bceoX587tkwmkfYnFUsIMizr1bJS]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; HE1EUR01HT243; 6:XXpDQiCOO41AyyxolO6eIZ+fiuIGXtxnl6AW0f9+ULi0FTHfVZE0in1ZMpgmA+21sZ3E6dGiOnWD3u4WvXdS8p45d+X8W6rpvGU0BiwbHy3HRTfEFChaTre/sarB1AHFj72P5XZt1C+SMJSSwMqc4ozJwoGxU8bC8CmheVprbEYZ87YS/B0RLH5YBoLTsdQkSR3X7/E2SYSV7bRlZbaaN2rEFpLmC4ueSXhR78bbGkCdlErx99jqnzEYITfgZcUWMpEUX9EEm+w5rWjrnZ9ehxHO247sI7fJJk2xMPevt8WF7oE40BTIn3vPvg73EG/aG9CLNQ9cJmQEdASCdSHWXspYqVgwq71COaEWSxNjSMIiVSclw7RFHEaiXmLeiCaikuISpzmNoNEQFi0PZ9mdbDtMsNymuo2NxP8UQhJ8UPhdyUwsLp0kXeSsGB6Hk+bOkF5ENI1xzhY9lqeTEi+MAQ==; 5:JKt9YvAH3G3ZIV2mzoX5hIXBmcp3fxg8ye91PW8RTAih6kJP1bIkJ9IrcgZHD/4Zx89i/MHBYhHcdVLDHm8wC3D0bf8Wd/X5/rTxUwtcp2Zo8o9HHSx6Fk97hUA1FOswAMgHAoqbdWzvvTCFLhzRuXfY2oRaRApCi3N6iWb+68w=; 7:0ZFgK+9wsJSsxVll1GcGrd98Mn7SMiEUUfTNj6ovIIuZMrDHaPuDrjm8icGeLB318IwJlHgERHOhyUgVWYjkZyeL7H/aCAo1KkmzCf3b0y8LUnihrf/T8nI7uF9cjdNt95veUhfYr6jvsBgXGufknw==
x-incomingheadercount: 47
x-eopattributedmessage: 0
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390098)(7020095)(201702061078)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322404)(1603101475)(1601125500)(1701031045); SRVR:HE1EUR01HT243;
x-ms-traffictypediagnostic: HE1EUR01HT243:
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(4566010)(82015058); SRVR:HE1EUR01HT243; BCL:0; PCL:0; RULEID:; SRVR:HE1EUR01HT243;
x-microsoft-antispam-message-info: FqaZrY/VqXyUk0llRBxddZThnlqyBTG+24Ph9DR1AX7K8USLUeOz1QWwfiGerdqO
Content-Type: multipart/alternative; boundary="_000_HE1PR0402MB293738B65A5D4EE2C974B9D4AEDE0HE1PR0402MB2937_"
MIME-Version: 1.0
X-OriginatorOrg: outlook.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: dd759f05-a917-4aa0-a2f5-4cc35c50e0c8
X-MS-Exchange-CrossTenant-Network-Message-Id: fcd41842-8ca4-4cc6-916c-08d64cdcf96c
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: dd759f05-a917-4aa0-a2f5-4cc35c50e0c8
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Nov 2018 22:35:28.0161 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1EUR01HT243
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/mdJzm0ubtmJ7jAyn8-VaIikllaY>
Subject: Re: [v6ops] IPmix relevance to the v6ops Charter
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: Sat, 17 Nov 2018 22:35:36 -0000
Jordi, We are not discussing on the IETF main mailing list, I think the IETf gives me the right to submit a draft and discuss it freely with the relevant WGs and with the appropriate people, this few e-mails can be ignored by those who are not interested for now, but don't keep always stop the discussion like that, there are many people who are willing to represent themselves and share thoughts. Khaled ________________________________ From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Sent: Sunday, November 18, 2018 12:24:35 AM To: Khaled Omar; Warren Kumari Cc: IPv6 Operations Subject: Re: [v6ops] IPmix relevance to the v6ops Charter You can create your own discussion group outside IETF, but please stop creating unnecessary noise in the lists, which only discourage people to keep participating in other more relevant works. I will love the chairs to ban you for a long time if you insist going on. You need to learn how IETF works, we like it or not (I’m not saying is perfect, and indeed we can do it much better), but in this specific case, you are wasting people time instead of reading all the information that is there to tell you how to contribute. Many people tried to help you in the right direction, including myself when I was sergeant-at-arms, and you keep ignoring everything, or maybe not interested in understanding it. Regards, Jordi De: v6ops <v6ops-bounces@ietf.org> en nombre de Khaled Omar <eng.khaled.omar@outlook.com> Fecha: sábado, 17 de noviembre de 2018, 22:54 Para: Warren Kumari <warren@kumari.net> CC: IPv6 Operations <v6ops@ietf.org> Asunto: Re: [v6ops] IPmix relevance to the v6ops Charter I'm not repeating myself, maybe the core idea is the same but there are many changes that works towards solving this problem, I have one more word to say, where can we discuss this topic if v6ops and 6man have barriers regarding this discussion? Best Regards Khaled Omar ________________________________ From: Warren Kumari <warren@kumari.net> Sent: Friday, November 16, 2018 12:27:52 AM To: Khaled Omar Cc: Fred Baker; IPv6 Operations Subject: Re: [v6ops] IPmix relevance to the v6ops Charter On Thu, Nov 15, 2018 at 3:12 PM Khaled Omar <eng.khaled.omar@outlook.com<mailto:eng.khaled.omar@outlook.com>> wrote: Hi Warren, The protocol is under development, but does this means that allowing IPv-4 only hosts to communicate to IPv6-only hosts and vice versa has no relevance to any of these WGs? We already have multiple transition technologies -- the working groups have not demonstrated interest in your proposal. Bob Hinden told you that IPmix is off-topic in the IPv6 Maintenance Working Group. Fred has said the same for the V6OPS charter, and I agree with him. I understand that you believe that you have a great idea / solution, but there isn't any support for this in any of the IETF WGs. I'm sorry - I know that this must be frustrating for you, but simply repeating yourself isn't going to change that. W Khaled From: Warren Kumari [mailto:warren@kumari.net<mailto:warren@kumari.net>] Sent: Thursday, November 15, 2018 8:36 PM To: Fred Baker <fredbaker.ietf@gmail.com<mailto:fredbaker.ietf@gmail.com>> Cc: Khaled Omar <eng.khaled.omar@outlook.com<mailto:eng.khaled.omar@outlook.com>>; IPv6 Operations <v6ops@ietf.org<mailto:v6ops@ietf.org>> Subject: Re: [v6ops] IPmix relevance to the v6ops Charter On Thu, Nov 15, 2018 at 12:28 AM Fred Baker <fredbaker.ietf@gmail.com<mailto:fredbaker.ietf@gmail.com>> wrote: > On Nov 14, 2018, at 1:34 PM, Khaled Omar <eng.khaled.omar@outlook.com<mailto:eng.khaled.omar@outlook.com>> wrote: > > This is part of the v6ops charter, so my comment is to work in the host to achieve the last part. Two comments: 1) I wish you luck. Changing the host has been the hardest part, in the sense that the common Socket layer is partially implemented in the applications, so deploying IPv6 has meant a minor change to every application. 2) Hosts are not the topic of v6ops; networks are. Bob Hinden told you that IPmix is off-topic in the IPv6 Maintenance Working Group (6man, ipv6@ietf.org<mailto:ipv6@ietf.org>) and asked you to take your topic elsewhere. The same is true for IPv6 Operations (v6ops@ietf.org<mailto:v6ops@ietf.org>). I'm trying to be gentle with you, as you clearly don't know your way around. But this topic doesn't belong on this list. This is very true -- it is more like 6MAN that V6OPS, but it certainly doesn't fit in the V6OPS charter. The fact that V6OPS, 6MAN *and* the IETF Discuss list have all said that this is off-topic indicates that the IETF doesn't want to work on this.. W -------------------------------------------------------------------------------- The fact that there is a highway to hell and a stairway to heaven is an interesting comment on projected traffic volume... _______________________________________________ v6ops mailing list v6ops@ietf.org<mailto:v6ops@ietf.org> https://www.ietf.org/mailman/listinfo/v6ops -- I don't think the execution is relevant when it was obviously a bad idea in the first place. This is like putting rabid weasels in your pants, and later expressing regret at having chosen those particular rabid weasels and that pair of pants. ---maf -- I don't think the execution is relevant when it was obviously a bad idea in the first place. This is like putting rabid weasels in your pants, and later expressing regret at having chosen those particular rabid weasels and that pair of pants. ---maf _______________________________________________ v6ops mailing list v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.
- [v6ops] IPmix I-D version 01. Khaled Omar
- Re: [v6ops] IPmix I-D version 01. Bless, Roland (TM)
- Re: [v6ops] IPmix I-D version 01. Khaled Omar
- Re: [v6ops] IPmix I-D version 01. Sander Steffann
- Re: [v6ops] IPmix I-D version 01. Gert Doering
- Re: [v6ops] IPmix I-D version 01. Khaled Omar
- Re: [v6ops] IPmix I-D version 01. Sander Steffann
- Re: [v6ops] IPmix I-D version 01. Khaled Omar
- Re: [v6ops] IPmix I-D version 01. Gert Doering
- Re: [v6ops] IPmix I-D version 01. Khaled Omar
- Re: [v6ops] IPmix I-D version 01. Bob Hinden
- Re: [v6ops] IPmix I-D version 01. Khaled Omar
- Re: [v6ops] IPmix I-D version 01. Bob Hinden
- [v6ops] IPmix relevance to the v6ops Charter Fred Baker
- Re: [v6ops] IPmix I-D version 01. Khaled Omar
- Re: [v6ops] IPmix relevance to the v6ops Charter Khaled Omar
- Re: [v6ops] IPmix relevance to the v6ops Charter Fred Baker
- Re: [v6ops] IPmix relevance to the v6ops Charter Khaled Omar
- Re: [v6ops] IPmix relevance to the v6ops Charter Fred Baker
- Re: [v6ops] IPmix relevance to the v6ops Charter Warren Kumari
- Re: [v6ops] IPmix relevance to the v6ops Charter Khaled Omar
- Re: [v6ops] IPmix relevance to the v6ops Charter Warren Kumari
- Re: [v6ops] IPmix relevance to the v6ops Charter Khaled Omar
- Re: [v6ops] IPmix relevance to the v6ops Charter JORDI PALET MARTINEZ
- Re: [v6ops] IPmix relevance to the v6ops Charter Khaled Omar
- Re: [v6ops] IPmix relevance to the v6ops Charter JORDI PALET MARTINEZ
- Re: [v6ops] IPmix relevance to the v6ops Charter Khaled Omar
- Re: [v6ops] IPmix relevance to the v6ops Charter JORDI PALET MARTINEZ
- Re: [v6ops] IPmix relevance to the v6ops Charter Khaled Omar