IETF Logo Mail Archive

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

Joel Halpern <jmh@joelhalpern.com> Sat, 08 October 2022 01:17 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 3F9AEC1524D7; Fri, 7 Oct 2022 18:17:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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 Z51_Y3SSWlYV; Fri, 7 Oct 2022 18:17:43 -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)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 663AAC1524D4; Fri, 7 Oct 2022 18:17:43 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4MknNR1xLYz1pNGk; Fri, 7 Oct 2022 18:17:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1665191863; bh=RGbml+quXMZygceTnL57Ex9mFLe4Ta3xpK6AmwbnmpQ=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=HdVrcd26ldXGueG5lJ5uLG25jzFyMbxMeGxVZI23cxRszY3kByUCuEJus89cOn2lu r3nIN0hmhVtqmzOQwT6hMAirOSD6b4mbMY/V4MGrnn486dm99BOhxOIm06EYf2V5fm /dA6rIzC5pvggGRPUFAKaG7xfPXoaU2ForrJTGdQ=
X-Quarantine-ID: <VeVr2il8T3lc>
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) server-digest SHA256) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4MknNQ4d4lz1pMKr; Fri, 7 Oct 2022 18:17:42 -0700 (PDT)
Content-Type: multipart/alternative; boundary="------------o1s0qPm9UTFKkd2yY7b0HfI2"
Message-ID: <4d993f28-a371-116a-2c48-f2a47ee42e75@joelhalpern.com>
Date: Fri, 07 Oct 2022 21:17:41 -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> <bdd7bf12-f712-3fe5-2698-9272c16ddded@joelhalpern.com> <58E77509-A1A1-4CE8-9EE4-22BEEEA8B62E@gmail.com> <98a941e4-0fff-ced1-d4ca-4406368eac31@joelhalpern.com> <4DC495DF-AD6B-4D60-80C4-B836DD365A0C@gmail.com>
From: Joel Halpern <jmh@joelhalpern.com>
In-Reply-To: <4DC495DF-AD6B-4D60-80C4-B836DD365A0C@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/QUYYGXR3MZy9SwCJR165IG17G1g>
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: Sat, 08 Oct 2022 01:17:47 -0000

Thanks.  Good enough for me.

On 10/7/2022 9:16 PM, Suresh Krishnan wrote:
> Hi Joel,
>
>> On Oct 7, 2022, at 9:07 PM, Joel Halpern <jmh@joelhalpern.com> wrote:
>>
>> Almost, but not quite.  The first part, up to "egress points" is 
>> fine.  But the description of the reasons leaves out one case I think 
>> is important. Namely, preventing packets from outside the SR Domain 
>> (e.g. from an outside attacker) entering the SRv6 Domain.)
>>
>>
>
> Ah. Got it. This is covered in more detail in RFC8754 Section 5.1 but 
> it makes sense to at least point to it here. Take 2:
>
> NEW:
> In case the deployments do not use this allocated prefix additional 
> care needs to be exercised at network ingress and egress points so 
> that SRv6 packets do not leak out of SR domains and they do not 
> accidentally enter SR unaware domains. Similarly as stated in Section 
> 5.1 of RFC8754 packets entering an SR domain from the outside need to 
> be configured to filter out the selected prefix if it is different 
> from the prefix allocated here.
>
> Thoughts?
>
> Regards
> Suresh
>

v2.23.0 | Report a Bug | By Email