Re: [Idr] WG LC on draft-ietf-idr-large-community-03.txt (10/17/2016 to 10/31/2016)

Robert Raszuk <robert@raszuk.net> Fri, 21 October 2016 16:49 UTC

Return-Path: <rraszuk@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 3932D129436 for <idr@ietfa.amsl.com>; Fri, 21 Oct 2016 09:49:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level:
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 WwVT0cs7fWkL for <idr@ietfa.amsl.com>; Fri, 21 Oct 2016 09:49:53 -0700 (PDT)
Received: from mail-wm0-x241.google.com (mail-wm0-x241.google.com [IPv6:2a00:1450:400c:c09::241]) (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 22049129485 for <idr@ietf.org>; Fri, 21 Oct 2016 09:49:53 -0700 (PDT)
Received: by mail-wm0-x241.google.com with SMTP id d199so366120wmd.1 for <idr@ietf.org>; Fri, 21 Oct 2016 09:49:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=mBEqviNs0xRHIyF6zOAg/24UcBbv7OyVD3JWpA/vn34=; b=ZFlJZarZX8MXgGBGddSoJHomJ+f0WdkQXJPx8F37/+o+ja9TzAAtYUb9cxRPNbhL2+ PkP2gru/TJKhq++AQJErCRpmFrNse3URk1TGKHMt4vSEWn5MUrv2gAKHVLXBYtvamJ4D cgj77cjEPbwW2FHsMtZTxXlxmQnlw4QABiUy/HMeisJnjRvzI+/ifWBDZu4pug1Ghnh9 jsAtySeWvFWGSBfnoG2ScCUMPTSXNY35L74g48I1Hv0IsJGDg9ARePyT8OjcvSVB/VKF EHdpVcbgix1nO5sEXsyGDh2F5Se2vWNalfbOFBLhizCkgMjO3nL8z3XEwoqxY/3HNad9 Tdhw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=mBEqviNs0xRHIyF6zOAg/24UcBbv7OyVD3JWpA/vn34=; b=TpwnEIJe0gSSUEorlF5/u8Qoawsw9VaDtqz1Ekmn/GCEyeUpfbny/nZvB0R2WdI6dq UCbWJPaIpG/Kyq2IxdEpcGf5lD7/Y9ik1copqjrp/pn44kE/PEbdRTs+LaAQK7WwSlSI ce/vgpQz066DFhowt3istigihT0248yFh1kwCSKUNveCpz/JBswaJs1sWMSbqV8X2lP7 zMbbLcleoQp7iw7qdKGKg1zHYIk41+EWqgOdGIxt/aiydMEAE6+waf7Kv1DTNj4UFaJf fdHMzmlwDIhZkc5apbb11w5bHnDdI/ypXPHZL6tTg90OjLztWoct/mlo2u1S38344r0s Dv8A==
X-Gm-Message-State: ABUngvdgdhGNLvHeR6sPHUZCf/ZpDEWMofoWlFsbGXuTWaOFEJ+ekYAeEcIWkokphhf7Iu34NFHTPRSemAYSQw==
X-Received: by 10.195.13.107 with SMTP id ex11mr1446664wjd.99.1477068591527; Fri, 21 Oct 2016 09:49:51 -0700 (PDT)
MIME-Version: 1.0
Sender: rraszuk@gmail.com
Received: by 10.80.182.155 with HTTP; Fri, 21 Oct 2016 09:49:49 -0700 (PDT)
In-Reply-To: <20161021164241.GC32387@Vurt.local>
References: <20161018191521.GT95811@Vurt.local> <9EFC9BAA-F917-4C70-A139-1F69CAECF9C0@pfrc.org> <20161020215938.GE1074@Vurt.local> <adb00bcd7b8e45db857eae7019c646fc@XCH-ALN-014.cisco.com> <ae5da282-201c-f745-9f26-67ce73826bd5@i3d.net> <CA+b+ERkV2PBtzzx=uoygDzvTyJzunROCNX=0Y4phvGdn=oK5Xw@mail.gmail.com> <20161021154958.GR27221@gir.theapt.org> <CA+b+ERmrzCtFLP98D0YzRc-BJNbBWp3Ce6yKZr2cg1_QS0Oz5w@mail.gmail.com> <2ddbfbaf-7b99-53b9-365c-269fcc7746e7@i3d.net> <CA+b+ERn6dG+R8+UV-jaRXAV7eWQBygqEQp4VY4x1yKukpVKhTA@mail.gmail.com> <20161021164241.GC32387@Vurt.local>
From: Robert Raszuk <robert@raszuk.net>
Date: Fri, 21 Oct 2016 18:49:49 +0200
X-Google-Sender-Auth: 9XGLB1USStoG3eVOL7RnaTuYEoE
Message-ID: <CA+b+ERkAJDFPwmiNr7_UiaKfRQnt=8h9d9JM6B4oFgU_P1S1cQ@mail.gmail.com>
To: Job Snijders <job@instituut.net>
Content-Type: multipart/alternative; boundary=047d7bfcedbeb4fe6d053f62d4e8
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/SdVN1GgdJF1kY2YV064ac1HQJPU>
Cc: IETF IDR WG <idr@ietf.org>, Peter Hessler <phessler@theapt.org>
Subject: Re: [Idr] WG LC on draft-ietf-idr-large-community-03.txt (10/17/2016 to 10/31/2016)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 21 Oct 2016 16:49:55 -0000

Hey Job,

That's what I thought ... but if so I do not get why there are so many
discussions of any MUSTs/SHOULDs/MAYs operators are expected to follow on
in the fields LCs provides.

If they are opaque that means there is zero structure in place and everyone
is free to put whatever he/she likes in it .. even hex encoded Morse (
https://goo.gl/rHcGeV)

We either allow all opaque and free style or we structure fields such that
for example they may be used in simple parametrized BGP in/out policy
example I provided.

And the excuses type "oh we can not structure it as there is no way to
insert valid ASN" are wrong as there is a way as proven :)

Cheers,
R.



On Fri, Oct 21, 2016 at 6:42 PM, Job Snijders <job@instituut.net>; wrote:

> On Fri, Oct 21, 2016 at 06:29:46PM +0200, Robert Raszuk wrote:
> > The policy example was nothing to do with BGP table. If I am receiving
> > BGP_UPDATE it comes with AS_PATH and may contain LC. So if I want very
> > simple policy to filter trash of LCs I can set it to match first 4
> > octets to any ASN present in the same UPDATE MSG AS_PATH attribute. If
> > it there I do not drop LC.
>
> A clever trick, but not a good fit for Large BGP Communities. Large BGP
> Communities are opaque, by definition and design.
>
> We want routing policy in which networks can send 2914:X:Y to us, and we
> can send 2914:A:B to them - very much like RFC 1997 communities. The
> Global Administator field does not necessarily contain the ASN of the
> sending party.
>
> Kind regards,
>
> Job
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>