Re: [i2rs] Suresh Krishnan's No Objection on draft-ietf-i2rs-rib-info-model-15: (with COMMENT)
Nitin Bahadur <nitin_bahadur@yahoo.com> Fri, 13 April 2018 06:01 UTC
Return-Path: <nitin_bahadur@yahoo.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2DF9126D45 for <i2rs@ietfa.amsl.com>; Thu, 12 Apr 2018 23:01:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.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 ohM5dfP7VRyO for <i2rs@ietfa.amsl.com>; Thu, 12 Apr 2018 23:01:57 -0700 (PDT)
Received: from sonic312-23.consmr.mail.gq1.yahoo.com (sonic312-23.consmr.mail.gq1.yahoo.com [98.137.69.204]) (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 26BA2126DFF for <i2rs@ietf.org>; Thu, 12 Apr 2018 23:01:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1523599315; bh=QCt0A3I0ddKe7wGPVOdOZBEoJswZGCO1ryJA7N5Ctx4=; h=Date:Subject:From:To:References:In-Reply-To:From:Subject; b=keY7WW3qF52QjGCIZZUNtehQ0iKXDjwXKT/D3OISHDXKIuXlp0NCQG56ikQIGaw6klAnPlLPnzm7uCZOR0QiYXydvxQjAeJSG1BDzL0QY0kgEDpN+ZynUkmDyK35Ym+d80FpX4/pFfdilJpA/GY4Xh9MZg2ZANJJvWR74c+m0t65490cp/edNHfBCd/ttbZ0F8N18X/MoExvXNuIPaMeBKH5TaB50kpLzdE/YtVnbfJPXCGc0Af7NxJFUWM0B1Uepi3t6adyamz8+4joPnAbbK1/y93zo8YR0AZ2qNZKtVoLPqEywjGuRC71UDmUjx+kKshusVpjYCfjvGh/X1eF9A==
X-YMail-OSG: eTGoD7MVM1mTnt2NgO58K1WPgwc2Jls.IOtw_A10KTMSnXuXRfvvM0MXpFQ8MIT Vcq.0Tmczn8c3dC2sw9JpNgQzktDZAZ3sVK_vWEPUBIm1RD5rEORCAR60CaayW3n504NoKABKd1i 59rWTxHlSAkw5SoYmaFGZ1RmwEMOX_X4c.y6TzEXLi.u6d_D0VmCfzHz.7VUxJAysXfzh46hpbsB tvEdTWLXZvhwQc65YD9LHgAklARDvZ6cSHNz98A15ErHvO7LRUKFLIndyS9k2JQCCX6nU4HmnDhI 0rMHtRN.LAPwdaUoYmCMARTQaHlyDcqFHQ40tCYzeccDaGS1dAkM0cB72SkJtJTHV6HLaBiEJ9Ok 3sSz0zhUexCpR9PVsHl4j_isrTjCyEDvDFWxX0AVEqmAXEzIGD6RbtXw6ltJdtjB20U.e0.FTNH7 gW96kFeugZgAjdFjMUJC4ldNe.JsfXpIxa.THa8GptKWjPwUlegnVS.GA_MfNxRdMnWs6ev_QRg3 7J2Hukqbimc8YSg--
Received: from sonic.gate.mail.ne1.yahoo.com by sonic312.consmr.mail.gq1.yahoo.com with HTTP; Fri, 13 Apr 2018 06:01:55 +0000
Received: from c-73-158-191-172.hsd1.ca.comcast.net (EHLO [192.168.0.106]) ([73.158.191.172]) by smtp432.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 0e982fd1cf02a906420b3fcea109ed8d; Fri, 13 Apr 2018 05:51:53 +0000 (UTC)
User-Agent: Microsoft-MacOutlook/10.9.0.180116
Date: Thu, 12 Apr 2018 22:51:50 -0700
From: Nitin Bahadur <nitin_bahadur@yahoo.com>
To: Susan Hares <shares@ndzh.com>, 'Suresh Krishnan' <suresh@kaloom.com>, 'The IESG' <iesg@ietf.org>
CC: i2rs@ietf.org, i2rs-chairs@ietf.org, draft-ietf-i2rs-rib-info-model@ietf.org
Message-ID: <1CF12BE1-AE55-43CF-95B4-66BC5B67E38F@yahoo.com>
Thread-Topic: [i2rs] Suresh Krishnan's No Objection on draft-ietf-i2rs-rib-info-model-15: (with COMMENT)
References: <152290489812.25948.2495908999143424774.idtracker@ietfa.amsl.com> <045701d3cce7$1c8bec00$55a3c400$@ndzh.com>
In-Reply-To: <045701d3cce7$1c8bec00$55a3c400$@ndzh.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/RoESEwe8tB7sKMycXIwpKDYZmqo>
Subject: Re: [i2rs] Suresh Krishnan's No Objection on draft-ietf-i2rs-rib-info-model-15: (with COMMENT)
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2rs/>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Apr 2018 06:01:59 -0000
Hi Suresh, Thanks for the review. Please see NB> below for comments. Did you mean 2001:DB8::1/128 for the host route? If not, this example is wrong since 2001:DB8::1/32 expands to 2001:DB8:0000:0000:0000:0000:0000:1/32 -> 2001:DB8::/32 as the route Sue: Yes - this is an error. NB> Nice catch. Fixing it in next rev. * Figure 4. Shouldn't the tunnel-encap and tunnel-decap also loop the packet back into nexthop processing just like the derived nexthops do? Suresh - I need to check the email list archives and get back to you on this point. My recollection was that there was a case where things people did not want to automatically loop this back. However, I cannot bring the discussion of 3.5 years ago to mind. I will take this as an action item as a reviewer to try to recreate the discussion. Thank you for mentioning this point. It is important to clarify in either case. NB> Sue is right that there were some cases where folks did not want the packet to be automatically sent back for lookup. They wanted an explicit specification on what to do with the packet. I believe the reasoning was there might be L2 processing that needs to be performed after the encap/decap and L2 processing was mainly out of scope of this draft. * Section 6 I would have expected the match type to have some indication about whether it requires an exact match or LPM (e.g. A MAC route uses an exact match but an IPv6 route uses LPM). Has the WG discussed this? The short answer is yes, extensive in early interims, list discussions and in session. Can you provide more depth to your questions. For the early discussions, I may need to query Alia Atlas and Jeff Haas (previous chairs) to get the institutional memory on this topic. (One of the reason I really want to have this document discussed with Alia Atlas as AD0. NB> Quoting from the grammar <ipv4-route> ::= <ip-route-type> (<destination-ipv4-address> | <source-ipv4-address> | (<destination-ipv4-address> <source-ipv4-address>)) <destination-ipv4-address> ::= <ipv4-prefix> <source-ipv4-address> ::= <ipv4-prefix> <ipv4-prefix> ::= <IPV4_ADDRESS> <IPV4_PREFIX_LENGTH> Thus IP addresses have a "prefix length" associated with them indicating a LPM (or exact-match if prefix length is 32). A MAC route is expected to have an exact match. LPM for MAC routes was out of scope. Thanks Nitin
- [i2rs] Suresh Krishnan's No Objection on draft-ie… Suresh Krishnan
- Re: [i2rs] Suresh Krishnan's No Objection on draf… Susan Hares
- Re: [i2rs] Suresh Krishnan's No Objection on draf… Susan Hares
- Re: [i2rs] Suresh Krishnan's No Objection on draf… Suresh Krishnan
- Re: [i2rs] Suresh Krishnan's No Objection on draf… Nitin Bahadur
- Re: [i2rs] Suresh Krishnan's No Objection on draf… Susan Hares