Re: Do we really need to add state into each packet ...

Uma Chunduri <umac.ietf@gmail.com> Thu, 14 May 2020 17:13 UTC

Return-Path: <umac.ietf@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52C4F3A0BFA for <ipv6@ietfa.amsl.com>; Thu, 14 May 2020 10:13:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, SPF_HELO_NONE=0.001, SPF_PASS=-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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gXWUYR6-xtnc for <ipv6@ietfa.amsl.com>; Thu, 14 May 2020 10:13:20 -0700 (PDT)
Received: from mail-vs1-xe29.google.com (mail-vs1-xe29.google.com [IPv6:2607:f8b0:4864:20::e29]) (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 A1EDA3A0C15 for <6man@ietf.org>; Thu, 14 May 2020 10:13:20 -0700 (PDT)
Received: by mail-vs1-xe29.google.com with SMTP id h9so2442007vsa.3 for <6man@ietf.org>; Thu, 14 May 2020 10:13:20 -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=Ks6REjLtfwO4kX19XdGuV5kiE8ZRkXZinDvO3ursBqo=; b=fKi30eD96FUJAe9aVYm4+y1iduK/YkxThH/RQ786Kbt14lCqx7xVAZ3Ix5cBrE02s5 tVSygsaKj96q2NxKJSE4QTVVMuVLXRb5kMZ045qf80wEdyC0hvGmOPM1GxAVnSf7ILQm T65gpdqt20Ia38Ygit1fvBdBt6b03UKcXn38yyPj16XU3t53Y7HTpVRvRIdZx2Jw2Q6Y YxLvyc0W9CGX6XXEosdz3M32uM/QLQAmn63/d5UVW8/FJ+NoMU+C960TmBfo4yfLIJk1 GWKssRD0lBHF+wAXXdX5723+zeAEGK9BIM0RvfH63JMnkv8uF1dTa/IELLUiioTtWTPA g+tg==
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=Ks6REjLtfwO4kX19XdGuV5kiE8ZRkXZinDvO3ursBqo=; b=hsM6rAlabxvS2kaBdVaEdWB7sekSMjAZqct91RUvRd9vUDQVdj7LeWOWrOWEookkDK JkYSwVFH6K2Fud2SoqbTLqlipHdJT92i1R4lvThCkRvbPm63RL/9MewWmNyqhyo1/riP xqEaanhleNABmJ4hS2OuWqTT5bRnmuQSWBLKBkLgR0tipsVI+baDquUPnSbHhfQqCc9p EuYjr/YbSIAig0tqHlUfCHxQama0BY6Top0DSVFEar1ntLDYp7Rxk3Tluxqv+gW5dK8/ tzXM0kUw0G7M7MkUnCvsK/hy8YlWrT3DFXfEgvuwgIsadqcst18SAx8u4lgu0bJc5bSo 8DLA==
X-Gm-Message-State: AOAM531u3UAWRwXwW9BfMB01a/u5Jbp1p2mMxQcBM5ZWhK3qTnAS9SGd 3Ra3vX3jEn1r9eGSlcuvUdjSlUQEwvszKh1DPQJIsaWD
X-Google-Smtp-Source: ABdhPJwQh+ZBaD072g6YY2U3pLtVjPwBvNyGyOva+0k1rWTvE4oo0jLQeS0F6e0ABMi5rPEId2grtRRwMMd42K3eof8=
X-Received: by 2002:a67:7709:: with SMTP id s9mr4916741vsc.61.1589476399473; Thu, 14 May 2020 10:13:19 -0700 (PDT)
MIME-Version: 1.0
References: <CAOj+MME4QkcWBXdN4MieFbFi0Fip+pNFdrbk5k7MDVJ9jt2RWA@mail.gmail.com> <e0615a0b-3e9d-1c5a-afe1-705e96f78231@gmail.com> <CAOj+MMFwxn_Bf9AWU0TOScC96uZe8uoNbcjU7=z7Bp07Tokdwg@mail.gmail.com> <CAF18ct6B9_kYSLZHx8UfaqDSZ6EMFKOeFqzaEF=KsQVpGvEV0A@mail.gmail.com> <CAOj+MMHbryct1yfGFtKvhjWr8S38Eg5p3MCM8eeHkUjx7wzDSA@mail.gmail.com>
In-Reply-To: <CAOj+MMHbryct1yfGFtKvhjWr8S38Eg5p3MCM8eeHkUjx7wzDSA@mail.gmail.com>
From: Uma Chunduri <umac.ietf@gmail.com>
Date: Thu, 14 May 2020 10:13:30 -0700
Message-ID: <CAF18ct7RGOfOgy1jeJkErha6akvAxUxfcDW-fkS_d+-1r0OkgA@mail.gmail.com>
Subject: Re: Do we really need to add state into each packet ...
To: Robert Raszuk <robert@raszuk.net>
Cc: 6man <6man@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002b67bc05a59ed026"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/jJ-NunUdVVCGEjlaJVYmJAgMAEM>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 May 2020 17:13:23 -0000

Hi Robert,

Thanks for the clarification.


Just one clarification to your response. IP-TE + NP proposal does not
> require BGP only network. Not at all. Network can run IGP as today, may or
> may not run any BGP based services.
>
Right.
I guess, I misunderstood earlier, as P nodes don't run BGP (generally). Per
draft,  if segment endpoint is a P node then it is required to run BGP.
You also indicated PCE (PCE-CC ?) usage as alternative approach (section 5).


All I am stating in the draft is that one option to signal the translation
> state is to leverage existing protocol extension "Advertising Segment
> Routing Policies in  BGP", but this is just an option - not a requirement
> of any sort to make the proposal work.
>


Sure.  Got it now.  Shall go through this more thoroughly.

Any ways, as the title of the thread, yes,  there are many ways to do this
(each with it's own strengths) with out including the state in each packet.

But there are cases where per packet information is useful too (NP and
additional non-path info..).
--
Uma C.




>>>