[Idr] Issue with encoding of SRv6 Behavior in draft-ietf-idr-segment-routing-te-policy
Ketan Talaulikar <ketant.ietf@gmail.com> Tue, 06 June 2023 08:59 UTC
Return-Path: <ketant.ietf@gmail.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAB1AC13AE34 for <idr@ietfa.amsl.com>; Tue, 6 Jun 2023 01:59:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 (2048-bit key) header.d=gmail.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 ZAOmrwvgi8u0 for <idr@ietfa.amsl.com>; Tue, 6 Jun 2023 01:59:15 -0700 (PDT)
Received: from mail-ej1-x62a.google.com (mail-ej1-x62a.google.com [IPv6:2a00:1450:4864:20::62a]) (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 ietfa.amsl.com (Postfix) with ESMTPS id 2EA8DC151092 for <idr@ietf.org>; Tue, 6 Jun 2023 01:59:15 -0700 (PDT)
Received: by mail-ej1-x62a.google.com with SMTP id a640c23a62f3a-977d4a1cf0eso334216866b.1 for <idr@ietf.org>; Tue, 06 Jun 2023 01:59:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1686041952; x=1688633952; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=b2xbAIVxxhi184+e5ip6olMs8cYwIGFt5sP6INVXEl0=; b=ECFQsz7+4XT/i7ZWitnnkFAQz4ndYEJZBotzrdxNwRGHubeAJ/HZKh5Ja4lPbYucQZ VgeaAskwdTonIOr/2WjvskYgGBTEoGjTY4+dCm5yEPVYNX8RosA3bQYmSuQTKJD/SPIn z8SAU/AkOPF/0KmG2+rMX0COdlnMsV3SQeUOvfwqA/8nDj4B650axcuvIViqHMgPURcm VpVlDIaZwNiWccP4dW/M3f+qkHPMW1wns0WL6Ai81XdVgZEuYUElhFHDY+P1RH+MnrjK Y76gR6v8HEJppJYt8zyvjeWVzUhfrNJQjdSTQ1Ms7Uzsu07FbXJ2hpvl25m2LhhjZ+tB 1BDA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686041952; x=1688633952; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=b2xbAIVxxhi184+e5ip6olMs8cYwIGFt5sP6INVXEl0=; b=MYme2BB5ISCcvVtitcNqplR7vU2beSJ4pZKE7axeAVtAQyedSTAKbirOYvc8xKcCRR 5BJovZGOLiEdrfJeEjcx1ZT+6I8oo1qBQYGFLHhLGJahWmQI6nM2hqOIfLoPUIsPGR/h DQVsvo7BQ0DadWVbtrRu298e6irl/+t8Zq61K/AWRVRIy/lrB+5rA8RKUFEk5nkv2lFH FZhB5NaAzZKMxRIYH4Ka+b8Rl40qPqawPPJaGcPr+yWrAiFllP5uEbWoJZrhbC4UFnRc 4dGsYDzs9npoOnsxYoCWfnOb5owJFtAH1jmQqryQu5xsVTfA/8LkkbZ5t4XMA18y0CHm wR0A==
X-Gm-Message-State: AC+VfDwALuM4sTCuihqEDd0JS7Qn71FXugvGgRX0xuKuZnHmTfaAUIo8 vteCjolA2dpM8z1d9Uyo40Yl9uRzkofSsJd0PFOvhP01OX8=
X-Google-Smtp-Source: ACHHUZ6ZEZaLINXN/k6CERCBIzMU3Rl10TY8OGBgBO7YAkiXy9DeVEQo5JUZSjqP41cWAAHs8b4mAsYFKuOfWXbrdXM=
X-Received: by 2002:a17:907:6d98:b0:960:c5fe:a36a with SMTP id sb24-20020a1709076d9800b00960c5fea36amr1660946ejc.61.1686041952330; Tue, 06 Jun 2023 01:59:12 -0700 (PDT)
MIME-Version: 1.0
From: Ketan Talaulikar <ketant.ietf@gmail.com>
Date: Tue, 06 Jun 2023 14:29:00 +0530
Message-ID: <CAH6gdPzC=wHYT+UDuFYN4Qj8+7FSrqJidUS-C3rr1Sr9C-RvAA@mail.gmail.com>
To: "idr@ietf. org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a53ac805fd723b8e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/XRxZBtaKKvNQGKjC5uI0oiIZQ2U>
Subject: [Idr] Issue with encoding of SRv6 Behavior in draft-ietf-idr-segment-routing-te-policy
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Jun 2023 08:59:18 -0000
Hello All, I was informed by a WG member of an error in the draft related to the encoding of the opaque (or "don't care") SRv6 Endpoint Behavior in the draft in https://datatracker.ietf.org/doc/html/draft-ietf-idr-segment-routing-te-policy-20#section-2.4.4.2.13 The text says: When set with the value 0, the choice of SRv6 Endpoint Behavior is left to the headend. However, the value 0 is reserved and hence not valid for use. The value 0xFFFF (opaque) is the one that has been allocated for such usage. Refer https://www.iana.org/assignments/segment-routing/segment-routing.xhtml#srv6-endpoint-behaviors I would propose to fix this issue in the document. Please let me know if there are any concerns or comments in this regard. Thanks, Ketan
- [Idr] Issue with encoding of SRv6 Behavior in dra… Ketan Talaulikar
- Re: [Idr] Issue with encoding of SRv6 Behavior in… Ketan Talaulikar