Fwd: I wonder what is being going on
shyam bandyopadhyay <shyamb66@gmail.com> Mon, 11 March 2019 16:13 UTC
Return-Path: <shyamb66@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1881612AF7E for <rtgwg@ietfa.amsl.com>; Mon, 11 Mar 2019 09:13:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.738
X-Spam-Level:
X-Spam-Status: No, score=-1.738 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_FREEMAIL_DOC_PDF=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 VbO0foQTw1bq for <rtgwg@ietfa.amsl.com>; Mon, 11 Mar 2019 09:13:34 -0700 (PDT)
Received: from mail-vs1-xe2c.google.com (mail-vs1-xe2c.google.com [IPv6:2607:f8b0:4864:20::e2c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A10821311CB for <rtgwg@ietf.org>; Mon, 11 Mar 2019 09:13:29 -0700 (PDT)
Received: by mail-vs1-xe2c.google.com with SMTP id m20so3055246vsq.8 for <rtgwg@ietf.org>; Mon, 11 Mar 2019 09:13:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zTTGH+pteunrQpYKC6IONE9NAJsMPwFXcMjXq6rqJ24=; b=FB91YwwKft6WcqFYWlloOzAuChEql4v/4tDAUdQ8z6N7UeR/Cevwwf4RbvZwl1BAq6 +f1zomRwh2sY1xnDDw4xIwlFxtedObJf5uSbSIU0Pd2TyV5j8QngUg5CV9VOl123n7tS 99Xl4xB2Q1dqqUjl4qt5MSfclDtWl5zL5RjmmY/VaOqoI+gxNsfopTX3zx1tHPGAA/QN qymqGaNyZEz7wt69KvbV5BlJklD/JqsRLgw8Bi0gr+9wJW27JJJkVqd3rv0oFSTWjZir uU+mx+Ysso93spQSdssun1mm7M4P6TMWlYH/pF4oNS3JBLIauXxc+r6qbd2oxe8ygZEg Izjg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=zTTGH+pteunrQpYKC6IONE9NAJsMPwFXcMjXq6rqJ24=; b=j4NpT/XNXpCmYzr/I2D8GLtHpHswvF0CJDWwxG5xPDKAvaIU//sjGrNTD5jVXKkcDK 5h+hO610gv35JIyj/JWYcRWa8kkbK/S/EivxKkbvyAmcZqalWFZ6Iw6lXZxia3Nxhb7K HErOFzPh+5d7RIzbh+9qHCyHsW4iLbnHhOFBiyF8Wbjs+agv601vOfUHgl+d8nUcISr3 ZYubLukktpzrVmJ4NpHs+rJN6qQl+VF1Ju/Yd8t/PqXPBlYkkPXO8KKxPou906jfN+eJ ILlJu2Qba2QB5Av6F/AjbYbgX6j3EnAuXdepNaGB3W+vCpGysjslyYBd64Qu+rRtV9sf CmBw==
X-Gm-Message-State: APjAAAWfDippFjOn64CVLMr89lFJFmBj0270BR7JWAUWiiXTrGOTZ7h7 SmBp9r0LozOiuX5sNGPm+tY6Xii3uHEr+XHU0GmGGT7iGJs=
X-Google-Smtp-Source: APXvYqzHlLLK/NDiMngPmQSDzcQFXb9kGZI3lk8ES6Idv+mWCfsjrOXsC1C0EmZasmC+z55f63/0TIwSZOnzi9n8uxY=
X-Received: by 2002:a67:8588:: with SMTP id h130mr16354385vsd.11.1552320807934; Mon, 11 Mar 2019 09:13:27 -0700 (PDT)
MIME-Version: 1.0
References: <CAPTMOt+jvTbrH1_YOmXJ0YQpLB5LdePekwkd2HyvLMLfGbnpZQ@mail.gmail.com> <04F9E6B4-2398-400E-8BB9-21935AE14845@cooperw.in>
In-Reply-To: <04F9E6B4-2398-400E-8BB9-21935AE14845@cooperw.in>
From: shyam bandyopadhyay <shyamb66@gmail.com>
Date: Mon, 11 Mar 2019 23:13:51 +0700
Message-ID: <CAPTMOtKcPnwv9bD4xbRB1h=HwddDe1RznwApL-kf_NV1b0NbRA@mail.gmail.com>
Subject: Fwd: I wonder what is being going on
To: rtgwg@ietf.org
Cc: Alissa Cooper <alissa@cooperw.in>
Content-Type: multipart/mixed; boundary="000000000000561fea0583d3da5e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/hzAoEqeCt_tC08_G6LWVDr4d47E>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Mar 2019 16:13:36 -0000
Dear Area Director, Routing Working Group, IETF I am writing to with the intention to resolve the conflict between draft-shyam-site-multi and RFC 8028, RFC 8043 and draft-ietf-rtgwg-pa-multihoming. I had raised the issue to IESG and IAB earlier. Recently IAB has released a report as a reply to my input. I am quoting IAB's response and attaching the file of IAB response as well. IAB report states: On point 2, the IAB understands from a review of the datatracker that the documents are still under review for publication by the ISE. The IAB does not direct the ISE to publish specific documents; the stream’s editorial independence is its key feature. If the ISE does publish the documents, the IAB believes it will join a longer conversation on the topic of source address based routing, and that this would not normally imply any change of status of RFC 8028 or other documents that form part of that conversation. Other relevant work includes RFC 1970, RFC 2461, RFC 4861, RFC 5533, RFC 7048, and any number of related working group discussions. This is just a statement with over simplification without getting into the details of solution for site multihoming. The term 'source address based routing' is nothing new, but how it is supposed to be used to solve what kind of problem is the matter of concern. Traditionally routing is based on destination address and there are multiple protocols like RIP, BGP, OSPF and each has got its own flavor and use. Documents like RFC 1970, RFC 2461, might have used the term 'source address based routing', but none of them specified how it is to be used to solve the problem of site multihoming. Otherwise, what is the use of writing another document like RFC 8028? Let me describe once again how draft-shyam-site-multi has tackled the issue of routing associated with site multihoming: It is neither completely 'source address based routing' nor completely 'destination address based routing', but it is the combination of both. 1. To communicate from one host to another within the same customer site, it is traditional 'destination address based routing'. 2. To communicate from a host of one customer site to a host of another customer site, it is neither completely 'source address based routing' nor completely 'destination address based routing'. To achieve this with only 'source address based routing' or only with 'destination address based routing', it requires the routing table of the entire world to be brought in, which is a very costly approach. To solve this issue it uses 'source address based routing' from the source host to the customer edge router of that customer site and from CE router of first customer site to the destination host using 'destination address based routing'. In short it is described as 'default routing based on source domain of the source address of the outgoing traffic'. This unique solution was first introduced in section 2.4.1 of draft-shyam-mshn-ipv6-07.txt (from which draft-shyam-site-multi was derived). RFC 8028 just elaborates this solution. RFC 8043 and draft-ietf-rtgwg-pa -multihoming are also based on the same solution. I would request IETF to show me a document where this solution was provided earlier. If any such document exists, I withdraw everything that I claim. Otherwise, I would request IETF to revoke RFC 8028, RFC 8043 and draft-ietf-rtgwg-pa-multihoming. They can be reproduced by making a reference to draft-shyam-site-multi showing what they are trying to achieve on top of whatever has already been stated in draft-shyam-site-multi. This is how contribution of the contributors of RFC 8028, RFC 8043 and draft-ietf-rtgwg-pa-multihoming will be properly evaluated. Thanks and regards, Shyam ---------- Forwarded message --------- From: Alissa Cooper <alissa@cooperw.in> Date: Fri, Mar 8, 2019 at 2:05 AM Subject: Re: I wonder what is being going on To: shyam bandyopadhyay <shyamb66@gmail.com> Cc: <Martin.vigoureux@nokia.com>, Adrian Farrel <rfc-ise@rfc-editor.org>, < n.leymann@telekom.de> Hi Shyam, Please direct your comments to rtgwg@ietf.org. Thanks, Alissa > On Feb 25, 2019, at 8:27 PM, shyam bandyopadhyay <shyamb66@gmail.com> wrote: > > Hi Alissa, > > I am writing to you as I am not fully > aware of the process of publication of a RFC. > > There was a last call review date on 02-19-2019 for > draft-ietf-rtgwg-enterprise-pa-multihoming. > > I have said many times earlier that the > basic principle based on which RFC 8028, RFC 8043 > and draft-ietf-rtgwg-enterprise-pa-multihoming > are written, i. e. "default routing based on > source address of outgoing packets" was first > introduced on draft-shyam-site-multi. > > I had written earlier to AD Mr. Martin Vigoureux that > draft-ietf-rtgwg-enterprise-pa-multihoming > should make a reference to draft-shyam-site-multi > with an illustration what it is being trying to > achieve on top of whatever has already been stated on > draft-shyam-site-multi. > > Output of the review from Mr. Nicolai Leymann > shows no major or minor issues found and the > draft can be published with some minor editing. > > I get a feel that Mr. Nicolai Leymann is not > aware of the existence of draft-shyam-site-multi. > > So, I would request the reviewer to go through > draft-shyam-site-multi and suggest necessary changes > required based on my input. > > By the way, IETF should consider publishing > draft-shyam-site-multi prior to publishing > documents that are dependent on draft-shyam-site-multi. > > Thanks and regards, > Shyam
- Fwd: I wonder what is being going on shyam bandyopadhyay
- RE: I wonder what is being going on Pascal Thubert (pthubert)
- Re: I wonder what is being going on shyam bandyopadhyay
- Re: I wonder what is being going on Fred Baker
- Re: I wonder what is being going on William Atwood
- Re: I wonder what is being going on Mark Smith
- Re: I wonder what is being going on Mark Smith
- RE: I wonder what is being going on Azinger, Marla