Re: [ippm] Review on draft-ietf-ippm-ioam-data-06

Jai Kumar <jai.kumar@broadcom.com> Fri, 23 August 2019 22:27 UTC

Return-Path: <jai.kumar@broadcom.com>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F05DC12002F for <ippm@ietfa.amsl.com>; Fri, 23 Aug 2019 15:27:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=broadcom.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 RLCvb_c_0cWp for <ippm@ietfa.amsl.com>; Fri, 23 Aug 2019 15:27:47 -0700 (PDT)
Received: from mail-pg1-x536.google.com (mail-pg1-x536.google.com [IPv6:2607:f8b0:4864:20::536]) (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 9D35212000F for <ippm@ietf.org>; Fri, 23 Aug 2019 15:27:47 -0700 (PDT)
Received: by mail-pg1-x536.google.com with SMTP id u17so6517079pgi.6 for <ippm@ietf.org>; Fri, 23 Aug 2019 15:27:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=DAfuWTHsAeJzu8gwK6rb8eOjYCePFm8uoP9wFUzZWWw=; b=NkJYNV9tqyrlzm7w4/JlIK4+AdamYNPcCpkPECUosGiPt4bMWryyMU7fp19HOQbegz 0KN4esUwzHTtgK8FaeWyzg7JJbmxC0m/+lWY9rSJWcKiYkTV9FFfi+pOED5XM7aiyDIW r1W1h8NelW/898PgDDRoHbhK09m3FIDoa2lys=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=DAfuWTHsAeJzu8gwK6rb8eOjYCePFm8uoP9wFUzZWWw=; b=rUe4poHtSc5aNwiKify6Ay+dxJplaup8PQBnOmyVzXGXmxmGVuHhQGkEE0OUfBZ5ll GRkEfIkeRq4Ps9qYD6EenK19EER3XaoHSdugaVXUPytyJLa+pyU9Yh2p6kTD9hXYqSCn G2pTqm+nR1ILXP/li0UrkvomZC7L/AcV7UDcXnwqIPjvnfFWFh5qxs+rO6kDJ2pfgE/U Mq2y94OiTVUqMAdq1OBvyzMyLLtdOAQjYP2DIOPjwM/9mJTi3N+GO6pnQsvWA2sj1K6e k8jOwS9pyq+Gi45MUiCYfVcey6wEAue0OVkYl3d2LE6GxGoDV18jwidwu9w2R+k6r6Ex 99eQ==
X-Gm-Message-State: APjAAAUUptNeBPNlsTEH6pIVQRKnty3U67ZGe8PQg8AdOT5p75b+uJhn AowlKK/QEqSJ0DHuVro8GNsLvA==
X-Google-Smtp-Source: APXvYqxxysP3a3hNfaZb9skiDjGGPk7zSWbg5QKzQOzFmr5EXANVxNBRUEKDL20Fi4PaiWuJlBC4yQ==
X-Received: by 2002:aa7:818b:: with SMTP id g11mr7952910pfi.122.1566599266980; Fri, 23 Aug 2019 15:27:46 -0700 (PDT)
Received: from [10.199.211.222] ([12.37.163.218]) by smtp.gmail.com with ESMTPSA id e7sm3387383pfn.72.2019.08.23.15.27.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 23 Aug 2019 15:27:45 -0700 (PDT)
Content-Type: multipart/alternative; boundary=Apple-Mail-8D699C45-78F6-446E-99D8-4CE0F7F1134B
Mime-Version: 1.0 (1.0)
From: Jai Kumar <jai.kumar@broadcom.com>
X-Mailer: iPhone Mail (16C104)
In-Reply-To: <CA+-tSzxvTjEkjyKJsFtUDV8+PACoV+NO2odV0UbOQNUqo67LGw@mail.gmail.com>
Date: Fri, 23 Aug 2019 15:27:44 -0700
Cc: vijayr@arista.com, "draft-ietf-ippm-ioam-data@ietf.org" <draft-ietf-ippm-ioam-data@ietf.org>, IETF IPPM WG <ippm@ietf.org>, Hugh Holbrook <holbrook@arista.com>, "OU, Heidi" <heidi.ou@alibaba-inc.com>
Content-Transfer-Encoding: 7bit
Message-Id: <C7538809-1E20-47CE-9350-8EC9B7AA6D37@broadcom.com>
References: <B5A76AB5-AE39-4771-9472-38454CF52152@broadcom.com> <CAGn858RE4p8gez+b0=9PSsZQ=Y1uZANno5V7tqSo=cuqY7AJLA@mail.gmail.com> <BD32CF3D-C6F3-4CF6-A618-C41ED0C4D1CB@cisco.com> <CAGn858SLr4vix18=09gXgsN-VOspBL=qZ2-q6dWyF5b3ASgCYA@mail.gmail.com> <BYAPR11MB25845CFB28F096937486F8D7DAA50@BYAPR11MB2584.namprd11.prod.outlook.com> <CAGn858QOPgXb=-WgWhXETKgEw5v1soo=JsDB+LemOr7G6DKB1A@mail.gmail.com> <CA+-tSzxvTjEkjyKJsFtUDV8+PACoV+NO2odV0UbOQNUqo67LGw@mail.gmail.com>
To: Anoop Ghanwani <anoop@alumni.duke.edu>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/R3mFBfmDq7Hla5TLXTeGl_-0958>
Subject: Re: [ippm] Review on draft-ietf-ippm-ioam-data-06
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Aug 2019 22:27:52 -0000

Hi Frank,

While we are trying to close on GRE based details please provide your thoughts on trace type and reducing the size of trace header as well.

Thanks,
-Jai

> On Aug 23, 2019, at 3:02 PM, Anoop Ghanwani <anoop@alumni.duke.edu> wrote:
> 
> Hi Frank,
> 
> As with Vijay, I am also interested in understanding the use of GRE for in-sequencing OAM.  Do we end up needing an Ethertype for TCP/UDP?
> 
> Thanks,
> Anoop
> 
>> On Thu, Aug 22, 2019 at 10:06 AM Vijay Rangarajan <vijayr=40arista.com@dmarc.ietf.org> wrote:
>> Hi Frank:
>> Thanks, I knew I was missing something.
>> So basically what you are saying is - let's say we have a UDP packet, we are just going to stick in the GRE header and IOAM Header and Metadata in-between the original IP and UDP headers?
>> 
>> So, the next protocol in the IOAM Header should indicate the L4 protocol - i.e UDP/TCP? 
>> Looking at https://datatracker.ietf.org/doc/draft-weis-ippm-ioam-eth/, it actually defines the "Next protocol" in the IOAM header to be an ethertype value?
>> 
>> Thanks,
>> Vijay
>> 
>> 
>>> On Thu, Aug 22, 2019 at 6:22 PM Frank Brockners (fbrockne) <fbrockne@cisco.com> wrote:
>>> Hi Vijay,
>>> 
>>>  
>>> 
>>> note that you don’t necessarily need to “tunnel” – you can just use the GRE header to sequence-in IOAM.
>>> 
>>>  
>>> 
>>> Cheers, Frank
>>> 
>>>  
>>> 
>>> From: Vijay Rangarajan <vijayr@arista.com> 
>>> Sent: Donnerstag, 22. August 2019 05:31
>>> To: Carlos Pignataro (cpignata) <cpignata@cisco.com>
>>> Cc: Jai Kumar <jai.kumar@broadcom.com>om>; draft-ietf-ippm-ioam-data@ietf.org; IETF IPPM WG <ippm@ietf.org>rg>; Frank Brockners (fbrockne) <fbrockne@cisco.com>om>; Hugh Holbrook <holbrook@arista.com>om>; Anoop Ghanwani <Anoop.Ghanwani@dell.com>om>; OU, Heidi <heidi.ou@alibaba-inc...com>; Surendra Anubolu <surendra.anubolu@broadcom.com>om>; John Lemon <john.lemon@broadcom.com>
>>> Subject: Re: [ippm] Review on draft-ietf-ippm-ioam-data-06
>>> 
>>>  
>>> 
>>> Thanks Carlos, for pointing me to the draft.
>>> 
>>>  
>>> 
>>> Based on my understanding of the two drafts I have the following questions and concerns:
>>> 
>>> If I understand correctly, to deploy inband telemetry, we would need to construct GRE tunnels coinciding with the IOAM domain?
>>> GRE typically requires configuration to provision the tunnels. Provisioning and managing these tunnels and keeping these updated as the network grows/shrinks could be a significant overhead.
>>> In order to get the benefit of telemetry, we are imposing a change in forwarding protocol/topology and configuration - which, I feel is not desirable. For example, a customer might have basic L3 routing enabled and the expectation would be for inband telemetry to work seamlessly, without having to revamp the network with GRE tunnels and such. This could be a significant barrier to deployment.
>>> If sampling is used to select packets for performing IOAM encap, is the expectation that only sampled IOAM packets go through GRE encap? Or all data packets?
>>> Due to network nodes inserting the IOAM data, the inner L3/L4 headers keep getting pushed deeper. I would imagine this gets challenging for ASICs to access these fields for hashing/load balancing.
>>> Assuming only a subset of packets in a flow are subject to IOAM (based on sampling), how do we ensure these packets take the same network path as the rest of the packets in the flow?
>>> Thanks,
>>> 
>>> Vijay
>>> 
>>>  
>>> 
>>>  
>>> 
>>> On Wed, Aug 21, 2019 at 5:04 PM Carlos Pignataro (cpignata) <cpignata@cisco.com> wrote:
>>> 
>>> Hello, Vijay,
>>> 
>>>  
>>> 
>>> Please see https://datatracker.ietf.org/doc/draft-weis-ippm-ioam-eth/, and the document this replaces. 
>>> 
>>>  
>>> 
>>> Thanks!
>>> 
>>> Thumb typed by Carlos Pignataro.
>>> 
>>> Excuze typofraphicak errows
>>> 
>>> 
>>> 2019/08/21 6:35、Vijay Rangarajan <vijayr@arista.com>のメールt;のメール:
>>> 
>>> Hello all:
>>> 
>>> Apologise if this has been previously discussed.
>>> 
>>> In reading "draft-ietf-ippm-ioam-data-06", I don't see mention of GRE encap. The draft, in fact in Sec 3, says the following - "The in-situ OAM data field can be transported by a variety of transport protocols, including NSH, Segment Routing, Geneve, IPv6, or IPv4.  Specification details for these different transport protocols are outside the scope of this document."
>>> 
>>>  
>>> 
>>> Is there another document, or a description somewhere, that talks about how IOAM is proposed to be carried in GRE? what would be the GRE payload, the GRE protocol type etc?
>>> 
>>>  
>>> 
>>> Thanks,
>>> 
>>> Vijay
>>> 
>>>  
>>> 
>>>  
>>> 
>>> On Wed, Aug 21, 2019 at 7:52 AM Jai Kumar <jai.kumar@broadcom.com> wrote:
>>> 
>>> Hello Frank,
>>> 
>>>  
>>> 
>>> This is in context of our conversation at IETF105. My goal is to provide input and improve current IOAM data draft with the learnings we had with IFA deployment.
>>> 
>>> This feedback is based on various customer interactions and concerns raised by them wrt IOAM. Each feedback is a longer topic and I am starting this thread as a summary email. This is just highlighting the issues and not yet proposing any solution.
>>> 
>>>  
>>> 
>>>  
>>> 
>>> Feedback 1:
>>> 
>>> Section 4.2.1 Pre-allocated and Incremental Trace Options
>>> 
>>> Pre-allocated and incremental trace option is 8Bytes long. This can be easily reduced to 4Bytes.
>>> 
>>> There is a feedback that pre-allocated option is really not needed and either be removed or made optional.
>>> 
>>> Given that deployments are sensitive to the IOAM overhead (specially in 5G deployments), it’s a 50% fixed overhead savings on a per packet basis.
>>> 
>>>  
>>> 
>>>  
>>> 
>>> Feedback 2:
>>> 
>>> Section 4.1 IOAM Namespaces
>>> 
>>> Namespaces should be treated as templates (similar to IPFIX template record formats). This is more flexible way of enumerating data. 64K namespace id is a very large namespace and can be reduced to 64 IANA specified name spaces. Separate private name space can be allowed instead of interleaving of opaque data in the IANA allocated name space as suggested in the current draft “opaque state snapshot”.
>>> 
>>> https://tools.ietf.org/html/rfc7011#section-3.4
>>> 
>>>  
>>> 
>>> Feedback 3:
>>> 
>>> Section 4.2.1 Pre-allocated and Incremental Trace Options
>>> 
>>> IOAM-Trace-Type:  A 24-bit identifier which specifies which data
>>> 
>>>       types are used in this node data list.
>>> 
>>> This is the most contentious of all. In the current proposal, as new data fields are added, there is a corresponding trace type bit need in the header. This essentially means that all possible data fields need to be enumerated. Given that we there are 64K names spaces allowed, I don’t see how we can fit all possible data fields in this 24bit vector. I know there was a suggestion of keeping last bit as an extension bit but it is still scalable and/or easy to implement in hardware. Besides this the data fields are not annotated/encoded with the data type, something like in IPFIX https://tools.ietf.org/html/rfc7011#section-6.1
>>> 
>>>  
>>> 
>>> Feedback 4:
>>> 
>>> There is no version field in the data header and this will make interoperability challenging. Standard will evolve and headers bit definition and/or trace type will change and without version field HW will not be able to correctly handle the IOAM data headers.
>>> 
>>>  
>>> 
>>> Feedback 5:
>>> 
>>> Handling of TCP/UDP traffic using GRE encap is not acceptable. Here are some of the issues I can think of
>>> 
>>> GRE encaped IOAM packets will traverse a different network path then the original packet
>>> Not all packets can be GRE encaped to avoid the previous problem, due to wastage of network bandwidth (typically sampled traffic is used for IOAM). What about native GRE traffic, will it get further encaped in another GRE tunnel and so forth.
>>> IP header protocol will point to GRE IP proto and IOAM ethertype (pending allocation by IEEE) need to be read from the GRE header to detect an IOAM packet. This means parsing performance penalty for all regular GRE (non IOAM) traffic.
>>>  
>>> 
>>> Thanks,
>>> 
>>> -Jai
>>> 
>>>  
>>> 
>> _______________________________________________
>> ippm mailing list
>> ippm@ietf.org
>> https://www.ietf.org/mailman/listinfo/ippm
> _______________________________________________
> ippm mailing list
> ippm@ietf.org
> https://www.ietf.org/mailman/listinfo/ippm