Re: [bess] draft-ietf-bess-evpn-overlay-10 PMSI with Ingress Replication

Jeff Tantsura <jefftant.ietf@gmail.com> Fri, 15 December 2017 18:33 UTC

Return-Path: <jefftant.ietf@gmail.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 030CA1270A7 for <bess@ietfa.amsl.com>; Fri, 15 Dec 2017 10:33:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 W6yUAYEmiTV0 for <bess@ietfa.amsl.com>; Fri, 15 Dec 2017 10:33:34 -0800 (PST)
Received: from mail-ot0-x230.google.com (mail-ot0-x230.google.com [IPv6:2607:f8b0:4003:c0f::230]) (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 2748912706D for <bess@ietf.org>; Fri, 15 Dec 2017 10:33:34 -0800 (PST)
Received: by mail-ot0-x230.google.com with SMTP id y10so8546546otg.10 for <bess@ietf.org>; Fri, 15 Dec 2017 10:33:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=user-agent:date:subject:from:to:message-id:thread-topic:references :in-reply-to:mime-version:content-transfer-encoding; bh=NRSrcDtrXTRoEjPl/7cUDpV4O4smC5ggA6tMceE3qkA=; b=QjNLXthxzwvxX2aYR7pSe4usi8wVsSINd53jDK9rbDgtMP0qjB7/CGKEf/D2t5zQ71 Vo4hNu3Cx40k7q0Ir4nPwmjZf8tCj3eAAxw8M1zCB7sCCzzxNdqspyJAVzsy/1FEoqjD h/hb+SR9yRGhoBVmmDL0x7pNOBeoHxMR6aoc881W4bKhMNNugYF0Dl0kugQ8ksiiYX/c oFuLMboIpMJny/lidR3vQBcN9B2t3VRw/UV6JevwB3lsOEadClydFWEfrAxSR7JMBMeo sMN2UcKlgIiMzfHHmM0uLNIxzjFbV1KYduuBNMkU/H5DhqpoR76K2XV64u5+Gu8ZDyKD 5bSA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:user-agent:date:subject:from:to:message-id :thread-topic:references:in-reply-to:mime-version :content-transfer-encoding; bh=NRSrcDtrXTRoEjPl/7cUDpV4O4smC5ggA6tMceE3qkA=; b=Ylm/4nMd3lw1cuyP/BVUwjDS+60DvHskrGJbRZjw2L0LphLPzsGfXY4EzvLYURYKad sy0NsV4+tovc9zFJjCZu6IdjNIewhXujKp+01SrVfv8p6IjGIKSL0e2uXtXBM0mX8i6H u9TqHP0jpz4eSTFbhNI1qNqlMqi1tlg/17uSMt7kn2eLr6ftSEsiR9W311G2ltjbL2TB 1V8Cy1lfF1n1YCSc+A004155UXhPjGajUxolzyHd1yZkUdWJursBqvRezeW3hkWId6D5 wwDI5rn25PZ8c5psN+1k5/7B9lKEbQ7mDISt3RjBNARs86Aqkv/acSyGm12ENEfLocRt eQOA==
X-Gm-Message-State: AKGB3mJ8sQtLEA1LpKnIib77WOMXM4tT0LhniPxeqAThVOSbDtOS7ipr 8iL2sZN19AJlu2JU2BaHJjc=
X-Google-Smtp-Source: ACJfBosph6PUckybJ1yezHDqu3p+9q48dhSuD6W2C8D4aYAeXb63xQ4IwxtF83qlWqD62vOO1nU7CA==
X-Received: by 10.157.12.74 with SMTP id 68mr7982693otr.368.1513362813442; Fri, 15 Dec 2017 10:33:33 -0800 (PST)
Received: from [100.65.101.83] ([206.16.17.196]) by smtp.gmail.com with ESMTPSA id n130sm3126649oia.12.2017.12.15.10.33.32 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 15 Dec 2017 10:33:32 -0800 (PST)
User-Agent: Microsoft-MacOutlook/f.29.0.171205
Date: Fri, 15 Dec 2017 10:33:32 -0800
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: Martin Vigoureux <martin.vigoureux@nokia.com>, <bess@ietf.org>
Message-ID: <8BD0ACBF-833B-4785-826D-A49092FC651A@gmail.com>
Thread-Topic: [bess] draft-ietf-bess-evpn-overlay-10 PMSI with Ingress Replication
References: <CAO367rVvmv4kyFbS8C=WEyZpXZZQUgLsFX1gscy49UNU2_pJvQ@mail.gmail.com> <1513258777.30252.11.camel@orange.com> <CAO367rWCvS2fOD43agch0Mpu1pOfoXYHkptJPfccJsPHc+vzZQ@mail.gmail.com> <AT5PR8401MB0353B2B69B6F8D292FFB268BF60A0@AT5PR8401MB0353.NAMPRD84.PROD.OUTLOOK.COM> <1513334544.6588.9.camel@orange.com> <MWHPR05MB355144EB0007DE112C09F34BC70B0@MWHPR05MB3551.namprd05.prod.outlook.com> <AT5PR8401MB035389AC482DEFA78909334FF60B0@AT5PR8401MB0353.NAMPRD84.PROD.OUTLOOK.COM> <1513356144.6588.38.camel@orange.com> <37A2C852-9730-4944-8205-88ACE9112990@cisco.com> <5c71355d-d55d-d74b-73dc-dc924a756ec9@nokia.com>
In-Reply-To: <5c71355d-d55d-d74b-73dc-dc924a756ec9@nokia.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/9wWHXHD3RjGefGYdSXq5IVrXtnQ>
Subject: Re: [bess] draft-ietf-bess-evpn-overlay-10 PMSI with Ingress Replication
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Dec 2017 18:33:37 -0000

+1 Martin.
By removing it you assume right interpretation, by wording it unambiguously you provide
the right interpretation.

Cheers,
Jeff

-----Original Message-----
From: BESS <bess-bounces@ietf.org> on behalf of Martin Vigoureux <martin.vigoureux@nokia.com>
Date: Friday, December 15, 2017 at 10:24
To: <bess@ietf.org>
Subject: Re: [bess] draft-ietf-bess-evpn-overlay-10 PMSI with Ingress Replication

    if the intent was to help people better understand the reasoning behind 
    the design, is it really best to remove it?
    Wouldn't a rephrasing be more appropriate?
    
    -m
    
    Le 2017-12-15 à 19:21, Ali Sajassi (sajassi) a écrit :
    > Hi Thomas,
    > 
    > On 12/15/17, 8:42 AM, "BESS on behalf of Thomas Morin" <bess-bounces@ietf.org on behalf of thomas.morin@orange.com> wrote:
    > 
    >      
    >      Here I would suggest to authors to consider purely removing this
    >      paragraph, not because it would be wrong or ambiguous (as said above, I
    >      don't think it is), but because as far as I can tell it has never meant
    >      to specify anything not already implied by RFC7432, but was here only
    >    to help understand.
    >    
    > OK, I will remove it in the next rev.
    >    
    > Cheers,
    > Ali
    >      
    >      Best,
    >      
    >      -Thomas
    >      
    >      
    >      
    >      
    >      -----Original Message-----
    >      > From: John E Drake [mailto:jdrake@juniper.net]
    >      > Sent: Friday, December 15, 2017 9:52 AM
    >      > To: EXT - thomas.morin@orange.com <thomas.morin@orange.com>; Fedyk,
    >      > Don <don.fedyk@hpe.com>; Marco Marzetti <marco@lamehost.it>
    >      > Cc: bess@ietf.org
    >      > Subject: RE: [bess] draft-ietf-bess-evpn-overlay-10 PMSI with Ingress
    >      > Replication
    >      >
    >      > Thomas,
    >      >
    >      > I completely agree w/ your email, below.
    >      >
    >      > Yours Irrespectively,
    >      >
    >      > John
    >      >
    >      >
    >      > > -----Original Message-----
    >      > > From: BESS [mailto:bess-bounces@ietf.org] On Behalf Of Thomas Morin
    >      > > Sent: Friday, December 15, 2017 5:42 AM
    >      > > To: Fedyk, Don <don.fedyk@hpe.com>; Marco Marzetti <marco@lamehost.
    >      > > it>
    >      > > Cc: bess@ietf.org
    >      > > Subject: Re: [bess] draft-ietf-bess-evpn-overlay-10 PMSI with
    >      > > Ingress
    >      > > Replication
    >      > >
    >      > > Hi Don,
    >      > >
    >      > > Fedyk, Don, 2017-12-14 20:33:
    >      > > > I think the gray area is that this draft talks about BUM traffic
    >      > > > and
    >      > > > ingress replication and then has a section on Multicast tunnels
    >      > > > which excludes ingress replication traffic from the tunnels.
    >      > >
    >      > > No, ingress replication is not excluded at all:
    >      > >
    >      > >    The following tunnel types as defined in [RFC6514] can be used
    >      > > in
    >      > >    the PMSI tunnel attribute for VXLAN/NVGRE:
    >      > >
    >      > >          + 3 - PIM-SSM Tree
    >      > >          + 4 - PIM-SM Tree
    >      > >          + 5 - BIDIR-PIM Tree
    >      > >          + 6 - Ingress Replication
    >      > >
    >      > > > If you are using point to point VXLAN/NVGRE  tunnels then
    >      > > > ingress
    >      > > > replication is default [...]
    >      > >
    >      > > This formulation surprises me: that some implementations behave as
    >      > > you
    >      > > describe is possibly true (this seems to be the case of the
    >      > > implementation that triggered this discussion), but I don't know
    >      > > about
    >      > > any text in the specs we are discussing that would imply such a
    >      > > 'default'.
    >      > >
    >      > > You might have implementations that in the absence of any local
    >      > > configuration for an EVPN instance on which type of tunnel to use
    >      > > for
    >      > > BUM, will default to ingress replication: this is fine, out of the
    >      > > scope of what is specified for interop, and not breaking other
    >      > > implementations (as long, of course, that what is chosen locally
    >      > > is
    >      > > then advertised as expected in a PMSI Tunnel Attribute).
    >      > >
    >      > >
    >      > > > but IMET is being used to identify the NVE IP.    I read RFC7432
    >      > > > and
    >      > > > RFC6514 in this area and thought that the PMSI attribute MUST be
    >      > > > set
    >      > > > when there is an Inclusive Multicast Ethernet tag IMET.
    >      > >
    >      > > Yes!  (the text of RFC7432 quoted by Ali reminds us that)
    >      > >
    >      > >
    >      > > > I can see two possible fixes:
    >      > > > -          Specify that the PMSI attribute MUST be set if there
    >      > > > is an
    >      > > > IMET route and specify correct attribute.
    >      > >
    >      > > Given the content of RFC7432 and the fact that this is a normative
    >      > > ref
    >      > > of draft-ietf-bess-evpn-overlay, I think that we don't need to
    >      > > repeat
    >      > > this MUST in draft-ietf-bess-evpn-overlay.  That is, unless we
    >      > > explicitly identify an ambiguous piece of text.
    >      > >
    >      > > > -          Allow that ingress replication is default when PMSI is
    >      > > > absent but accept PMSI that specifies ingress replication.
    >      > > >
    >      > >
    >      > > I don't think we should do that. It would overnight make non-
    >      > > compliant
    >      > > pre- standard implementation of draft-ietf-bess-evpn-overlay,
    >      > > without
    >      > > a rationale to do so except coping with an implementation that
    >      > > assumed a bit too much.
    >      > >
    >      > > Best,
    >      > >
    >      > > -Thomas
    >      > >
    >      > >
    >      > >
    >      > > > From: BESS [mailto:bess-bounces@ietf.org] On Behalf Of Marco
    >      > > > Marzetti
    >      > > > Sent: Thursday, December 14, 2017 9:21 AM
    >      > > > To: Thomas Morin <thomas.morin@orange.com>
    >      > > > Cc: bess@ietf.org
    >      > > > Subject: Re: [bess] draft-ietf-bess-evpn-overlay-10 PMSI with
    >      > > > Ingress Replication
    >      > > >
    >      > > > Hello,
    >      > > >
    >      > > > I have encountered an implementation that is not attaching any
    >      > > > PMSI
    >      > > > to the IMET.
    >      > > > The authors think they don't really need it because they only
    >      > > > support Ingress Replication.
    >      > > > Such behavior breaks interoperability with other implementations
    >      > > > that are dropping the NLRI if PMSI is not attached.
    >      > > >
    >      > > > So i looked at draft-ietf-bess-evpn-overlay-10 and noticed that
    >      > > > there's no clear indication of what the proper behavior is.
    >      > > > As said i assumed i had to look at RFC7432 and RFC6514 (and i
    >      > > > did
    >      > > > it), but i wasn't 100% sure and i preferred to ask.
    >      > > >
    >      > > > Onestly you already made my day by confirming what i thought.
    >      > > > My suggestion was to make things more clear, but i admit that it
    >      > > > could look redundant.
    >      > > >
    >      > > > Thanks
    >      > > >
    >      > > >
    >      > > >
    >      > > >
    >      > > >
    >      > > >
    >      > > >
    >      > > > On Thu, Dec 14, 2017 at 2:39 PM, Thomas Morin
    >      > >
    >      > > <thomas.morin@orange.co
    >      > > > m> wrote:
    >      > > > > Hi Marco,
    >      > > > >
    >      > > > > Marco Marzetti, 2017-12-14 12:25:
    >      > > > > > I am writing this email asking you to clarify what's the
    >      > > > >
    >      > > > > suggested
    >      > > > > > behavior when PMSI Tunnel Type is set to "Ingress
    >      > > > > > Replication"
    >      > > > >
    >      > > > > (type
    >      > > > > > 6) as draft-ietf-bess-evpn-overlay-10 only suggests what to
    >      > > > > > do
    >      > > > >
    >      > > > > with
    >      > > > > > multicast tunnel trees.
    >      > > > > >
    >      > > > > > I think the originating PE should conform with RFC6514 and
    >      > > > >
    >      > > > > RFC7432
    >      > > > > > (from which you've taken inspiration) and always (RFC2119
    >      > > > > > MUST)
    >      > > > > > attach PMSI Tunnel attribute with the Tunnel Type set to
    >      > > > > > Ingress
    >      > > > > > Replication and Tunnel Identifier set to a routable address
    >      > > > > > of
    >      > > > >
    >      > > > > the PE
    >      > > > > > itself (more specifically NVE's IP address).
    >      > > > > >
    >      > > > > > Is that correct?
    >      > > > > > In that case i suggest to add the following line at the end
    >      > > > > > of
    >      > > > > > Section 9.
    >      > > > > > """
    >      > > > > > For Ingress Replication the PE should follow what's stated in
    >      > > > >
    >      > > > > RFC6514
    >      > > > > > Section 5 .
    >      > > > > > """
    >      > > > >
    >      > > > > The text of section 9 lists "Ingress Replication" in the list
    >      > > > > of
    >      > > > > tunnel types that can be used. My understanding is that, in
    >      > > > > the
    >      > > > > absence of anything being specifically said for Ingress
    >      > > > > Replication, an implementation should follow what is said in
    >      > > > > RFC7432 and RFC6514.
    >      > > > > (What
    >      > > > > other specs could it follow to implement this supported type ?
    >      > > > > RFC7432
    >      > > > > and RFC6514 are more than an inspiration here, these are specs
    >      > > > > that the document refers to explicitly)
    >      > > > >
    >      > > > > So I'm not sure that it is useful or needed to add text.
    >      > > > >
    >      > > > > Can you perhaps expand on why the current text would possibly
    >      > > > > be
    >      > > > > ambiguous, misleading or incomplete...?
    >      > > > >
    >      > > > > -Thomas
    >      > > > >
    >      > > >
    >      > > >
    >      > > >
    >      > > > --
    >      > > > Marco
    >      > >
    >      > > _______________________________________________
    >      > > BESS mailing list
    >      > > BESS@ietf.org
    >      > > https://urldefense.proofpoint.com/v2/url?u=https-
    >      > > 3A__www.ietf.org_mailman_listinfo_bess&d=DwICAg&c=HAkYuh63rsuhr6Sc
    >      > > bfh0UjBXeMK-ndb3voDTXcWzoCI&r=CRB2tJiQePk0cT-h5LGhEWH-
    >      > > s_xXXup3HzvBSMRj5VE&m=tHiUTn9_QXrhs3cw-
    >      > > Dn9_qwR3VK2xWv72DcpoOfR_SI&s=VxylPoVhzXC58hBsqToxzhUK6-3kfy-
    >      > > ktUi7A9KZDcs&e=
    >      
    >      _______________________________________________
    >      BESS mailing list
    >      BESS@ietf.org
    >      https://www.ietf.org/mailman/listinfo/bess
    >      
    > 
    > _______________________________________________
    > BESS mailing list
    > BESS@ietf.org
    > https://www.ietf.org/mailman/listinfo/bess
    > 
    
    _______________________________________________
    BESS mailing list
    BESS@ietf.org
    https://www.ietf.org/mailman/listinfo/bess