Re: [GROW] Terry Manderson's Discuss on draft-ietf-grow-blackholing-02: (with DISCUSS and COMMENT)

David Farmer <farmer@umn.edu> Thu, 04 August 2016 15:39 UTC

Return-Path: <farmer@umn.edu>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 565F112B046 for <grow@ietfa.amsl.com>; Thu, 4 Aug 2016 08:39:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.586
X-Spam-Level:
X-Spam-Status: No, score=-5.586 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.287] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=umn.edu
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 J4-TjSWcV8Y7 for <grow@ietfa.amsl.com>; Thu, 4 Aug 2016 08:39:08 -0700 (PDT)
Received: from mta-p8.oit.umn.edu (mta-p8.oit.umn.edu [134.84.196.208]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3FC8312D5A4 for <grow@ietf.org>; Thu, 4 Aug 2016 08:39:05 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by mta-p8.oit.umn.edu (Postfix) with ESMTP id AE9579AD for <grow@ietf.org>; Thu, 4 Aug 2016 15:39:04 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p8.oit.umn.edu ([127.0.0.1]) by localhost (mta-p8.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id caT0WoC2pSTZ for <grow@ietf.org>; Thu, 4 Aug 2016 10:39:04 -0500 (CDT)
Received: from mail-ua0-f200.google.com (mail-ua0-f200.google.com [209.85.217.200]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p8.oit.umn.edu (Postfix) with ESMTPS id 5C515584 for <grow@ietf.org>; Thu, 4 Aug 2016 10:39:04 -0500 (CDT)
Received: by mail-ua0-f200.google.com with SMTP id r91so340202850uar.2 for <grow@ietf.org>; Thu, 04 Aug 2016 08:39:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=bVB3ZG5/mgrpLHP6HpliB/muDj1Y2Auq8F2oU2dbKqk=; b=CPCUM/VoMMww+u0jZWsuLHwoYunWZp7H2iH+PdZfW+JRdGMujP/D12gLqu4XVr9mrB I5/BOwpsU/37TowBqn7gPlYtpk7WnELp2g6RI3pkY2APpQ2bQ1O2Fzdfu1uJehIHdrSw j/SmBC/7B6BvCeX4qabjsHeSXtUBWQdr7LmtM=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=bVB3ZG5/mgrpLHP6HpliB/muDj1Y2Auq8F2oU2dbKqk=; b=XH1bLN0BKAdtoXh8nFRML8NuH0jMrDLye8965ph6Y1Y+mXaPVm/gSAtCu4wCzbeS/m Fj8j72hkOjsEi5S5x2JEjyC1Xt9+cvZ29ZSLAAUna/ThtdXzAoe8/3SrIbNUGkjZH1DB f2EhYfvlcqySAyUMVBocJA96QYSU26+tfE7jPevY1AWBDlFUVkrDEkAbTPevfpBMa5An FTQq+A9bhTZv8DMAOyFXRhRRjTQZSxmFSF8hSea5mVJEpRVpWbP6yoDWzp6i8w0H93Nx 4tzjad4LVtPT4Q667ortob07ESRS6NWu7C1Miv33eF3q/mPV8K6jzD4JBtXFqTEXqBAc gXrQ==
X-Gm-Message-State: AEkooutC+DsNMxjBcsBq8wfgHGZ1axRyCUUxZxaCW/qF7KOM6rQoTUt33dfiA+I+NYl2F9GuAmS1gVLuLmVT6RepXjtfwDyuPL36KqguxizqYPVt13YWMS3S8Hsb1Cn+gAl3fYH4Xa7FhFA+8Os=
X-Received: by 10.200.47.92 with SMTP id k28mr7217849qta.50.1470325143744; Thu, 04 Aug 2016 08:39:03 -0700 (PDT)
X-Received: by 10.200.47.92 with SMTP id k28mr7217823qta.50.1470325143540; Thu, 04 Aug 2016 08:39:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.237.33.78 with HTTP; Thu, 4 Aug 2016 08:39:03 -0700 (PDT)
In-Reply-To: <CAL9jLaYaL9SzhXyC3wirqMB-NT0wU+=CpEg6G=3e9LL_qxoXsw@mail.gmail.com>
References: <20160804011604.9572.65960.idtracker@ietfa.amsl.com> <CAL9jLaYiu+U=46wY1JuGx3-h9cD7J8NpWnuV15hGRy8LeVzeCQ@mail.gmail.com> <D3C8EB51.9801E%terry.manderson@icann.org> <CAL9jLaYaL9SzhXyC3wirqMB-NT0wU+=CpEg6G=3e9LL_qxoXsw@mail.gmail.com>
From: David Farmer <farmer@umn.edu>
Date: Thu, 04 Aug 2016 10:39:03 -0500
Message-ID: <CAN-Dau2E9rGDGS818jo97vy1PXEiOM6c7FfSimi=EsqqukjXCQ@mail.gmail.com>
To: Christopher Morrow <christopher.morrow@gmail.com>
Content-Type: multipart/alternative; boundary="001a11356d62e2ae0a053940bfe3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/MlkG3cnZXKQ4RcUrxnxtzR31cdY>
Cc: "grow-chairs@ietf.org" <grow-chairs@ietf.org>, "grow@ietf.org grow@ietf.org" <grow@ietf.org>, "draft-ietf-grow-blackholing@ietf.org" <draft-ietf-grow-blackholing@ietf.org>, The IESG <iesg@ietf.org>
Subject: Re: [GROW] Terry Manderson's Discuss on draft-ietf-grow-blackholing-02: (with DISCUSS and COMMENT)
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Aug 2016 15:39:09 -0000

On Thu, Aug 4, 2016 at 10:12 AM, Christopher Morrow <
christopher.morrow@gmail.com> wrote:

>
>
> On Wed, Aug 3, 2016 at 11:26 PM, Terry Manderson <
> terry.manderson@icann.org> wrote:
>
>>
>>
>> On 4/08/2016, 12:11 PM, "Christopher Morrow"
>> <christopher.morrow@gmail.com> wrote:
>>
>> ....

> >----------------------------------------------------------------------
>> >COMMENT:
>> >----------------------------------------------------------------------
>> >
>> >>From a comment point of view, this informational document is agnostic on
>> >any operational differences between 2-byte and 4-byte ASNs. Is that
>> >intentional? Are there any operational differences worth calling out in
>> >regard to using extended communities etc?
>> >
>>
>> Any feedback on the comment?
>>
>>
> nope, I think extended communities with 4byte-asn is a problem though :(
>
>
A Well-Known RFC1997 community, that this document is defining, is usable
with both 2-byte and 4-byte ASNs.  Therefore if anything, that is another
advantage to defining a Well-Known community over the use of ASN specific
communities described in [RFC3882 <https://tools.ietf.org/html/rfc3882>]
and [RFC5635 <https://tools.ietf.org/html/rfc5635>].

There are most definitely general operational issues with 4byte-ASNs and
extended and ASN specific RFC1997 communities, however those more general
issues are mostly out of scope of this document.

-- 
===============================================
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================