Re: [spring] 6MAN WGLC: draft-ietf-6man-sids

Joel Halpern <jmh@joelhalpern.com> Fri, 07 October 2022 03:15 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CC27C14CE45; Thu, 6 Oct 2022 20:15:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.805
X-Spam-Level:
X-Spam-Status: No, score=-2.805 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, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1wnCCuB9LmR8; Thu, 6 Oct 2022 20:15:26 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 250C2C14CF1F; Thu, 6 Oct 2022 20:15:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4MkD2j5dNMz1pNGj; Thu, 6 Oct 2022 20:15:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1665112525; bh=gOk+ndvm2fEI1v8PFJmNXMpJLNOkrU5ESusPaJDTGDo=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=Q9cy2BsQ5xbOfXnFPpEiyJT+LA+y+XfTkhwt8akgNsVcCR6i4uuJ25qDvkDNgto0r hX3snjeNtqFDe7jq9RbhEkOiEigGPGMCYKgiRud+xoiMuejAQYXOFOc4AhtVerv7FZ nN6SE67fwE1XGZIkeMH1ww5KHsYzjriES/74tOTo=
X-Quarantine-ID: <sFZM3ss7tSYa>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.23.73] (unknown [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4MkD2j0Fygz1pKfw; Thu, 6 Oct 2022 20:15:24 -0700 (PDT)
Content-Type: multipart/alternative; boundary="------------Z3D4w0IXx9GTtjCTbBUhi20X"
Message-ID: <bdd7bf12-f712-3fe5-2698-9272c16ddded@joelhalpern.com>
Date: Thu, 06 Oct 2022 23:15:23 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.3.1
Content-Language: en-US
To: Suresh Krishnan <suresh.krishnan@gmail.com>
Cc: 6man <ipv6@ietf.org>, SPRING WG List <spring@ietf.org>
References: <CAFU7BARixwPZTrNQOuEw3WP-FqUsVwTj7btMTahcMbXm_NqWGw@mail.gmail.com> <CAB75xn4+N31=ggO03AAQJANv7RgHaC1eNGXRUQ9B20rLK+nJyg@mail.gmail.com> <E77D8982-11E9-45F9-81BF-3CA1E1F6B745@gmail.com> <CAB75xn4Zme4KOjPuY1_-4jCKTk1jshbq8X645zXhYQLiKB+N9g@mail.gmail.com> <54A38015-95AD-41F0-8E9D-76B3E62AA55B@gmail.com>
From: Joel Halpern <jmh@joelhalpern.com>
In-Reply-To: <54A38015-95AD-41F0-8E9D-76B3E62AA55B@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/q1x1cgORYi3RdSeKpKDNgNRyB70>
Subject: Re: [spring] 6MAN WGLC: draft-ietf-6man-sids
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Oct 2022 03:15:30 -0000

I wonder if we could / should add a sentence or two related to the 
address block noting that if an operator chooses to use other address 
blocks for the SRv6 SIDs then they need to be extra careful about 
configuring their edge filters to prevent leaks inwards or outwards?

Yours,

Joel

On 10/6/2022 10:34 PM, Suresh Krishnan wrote:
> Hi Dhruv,
>
>> On Oct 5, 2022, at 12:27 AM, Dhruv Dhody <dhruv.ietf@gmail.com> wrote:
>>
>> Hi Suresh,
>>
>> Thanks for taking the comments into consideration. Snip to just two 
>> points...
>>
>>
>>
>>>     - Do we need to add some text on what happens if the address
>>>     block assigned by IANA is not used in the received IPv6 packet?
>>
>> Dhruv: Any thoughts on this?
>
> This block is not mandatory to use. The packet will be processed as 
> any other IPv6 packet would. Is there something specific you are 
> worried about?
>
>>>     - This text "This would be useful in identifying and potentially
>>>     filtering packets at the edges of the SR Domains as described in
>>>     Section 4.1.". But section 4.1 of this I-D does not have any
>>>     text for this! Do you mean some other document?
>>
>>     This is in reference to the following text in 4.1
>>     " In this case, to allow the SR domain to fail closed, some form
>>     of filtering based on the LOC part of the SRv6 SID is required as
>>     relying purely on the presence of an SRH will not be sufficient.”
>>
>>     Please let me know if I can clarify this further.
>>
>>
>> Dhruv: I got confused because section 4.1 is meant to be only about 
>> C-SID. My suggestion would be to avoid the reference and just put the 
>> relevant sentence there for emphasis and clarity.
>
> Sounds good. Will do.
>
> Thanks
> Suresh