IETF Logo Mail Archive

Re: [Idr] WG adoption for draft-kumari-deprecate-as-set-confed-set - 8/16 to 8/30/2019

Job Snijders <job@ntt.net> Fri, 16 August 2019 17:24 UTC

Return-Path: <job@instituut.net>
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 051BD12008D for <idr@ietfa.amsl.com>; Fri, 16 Aug 2019 10:24:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.65
X-Spam-Level:
X-Spam-Status: No, score=-1.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no
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 CVTCuGS00sCV for <idr@ietfa.amsl.com>; Fri, 16 Aug 2019 10:24:33 -0700 (PDT)
Received: from mail-ed1-f50.google.com (mail-ed1-f50.google.com [209.85.208.50]) (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 15587120041 for <idr@ietf.org>; Fri, 16 Aug 2019 10:24:33 -0700 (PDT)
Received: by mail-ed1-f50.google.com with SMTP id m44so5749727edd.9 for <idr@ietf.org>; Fri, 16 Aug 2019 10:24:32 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=d+GHRtgcws4OI16kyiARt8SqvJR+AOZdAZ2kjhnEpKM=; b=VcKkDGyMVOAi+gjBsrVjl+W38i03vNNyQKmA3tNPUvmlvUZ66nM/h40wp4MocLTEh4 kcD5qAKHPLIzRNfuOggNb58LLOQXyjxydG8MFxqUts2wy3PQfEnh2CEpt7o+LSQW0/Rn +vOXa1QqvsZDUiTpJlNm55KYbzIcGegV/ZUlQDy6kNClW3OxKr8xGePn15+ZxgywJOfw a/57sqSRMNTUa9J931ezBv4/f6uj3H7OUoAEIyerSxW8RCOplDLC/fc7s9d8mO9ucIYZ qGH6g20olB4c4yaQrRwmUHqQdafHaOfr8T9PW+2/vc3B1/HbXtxQ2ewnEh0VATDfH5fu 5hJg==
X-Gm-Message-State: APjAAAUyIiZuoJTwe+/wpek4Uqg1GYlB2BIowweSI9yC/3DjGG2/Ebxt JEHdZuCBEEe+wZarpUwvtm4vsQ==
X-Google-Smtp-Source: APXvYqwGNZnTvTc0yReI3jmiW44/BK/8WJqxXJQzV2aUSD5GOpL4GFotPukhn5jZ7oj6FhoxWMXx2A==
X-Received: by 2002:a50:d5ca:: with SMTP id g10mr12159981edj.276.1565976271385; Fri, 16 Aug 2019 10:24:31 -0700 (PDT)
Received: from localhost ([2001:67c:208c:10:6ca8:18f9:13ed:2be]) by smtp.gmail.com with ESMTPSA id gz5sm884828ejb.21.2019.08.16.10.24.30 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 16 Aug 2019 10:24:30 -0700 (PDT)
Date: Fri, 16 Aug 2019 19:24:30 +0200
From: Job Snijders <job@ntt.net>
To: john heasley <heas@shrubbery.net>
Cc: Randy Bush <randy@psg.com>, Interminable Discussion Room <idr@ietf.org>
Message-ID: <20190816172430.GB64486@hanna.meerval.net>
References: <012001d5543f$ab7015a0$025040e0$@ndzh.com> <20190816154827.GA26534@shrubbery.net> <m2k1bdyqwv.wl-randy@psg.com> <20190816172208.GC26534@shrubbery.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20190816172208.GC26534@shrubbery.net>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/Jz3igJDvEAPcAJuMI7F9jG504PI>
Subject: Re: [Idr] WG adoption for draft-kumari-deprecate-as-set-confed-set - 8/16 to 8/30/2019
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
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, 16 Aug 2019 17:24:35 -0000

On Fri, Aug 16, 2019 at 05:22:08PM +0000, john heasley wrote:
> Fri, Aug 16, 2019 at 10:13:36AM -0700, Randy Bush:
> > > imo, wg discussion of this should address how the complete removal
> > > will proceed, such that implementations can drop support entirely,
> > > which this draft does not address.
> > 
> > could you explain a bit more?  e.g. do you mean how a conforming
> > speaker, i.e. one which does not support sets, should act when
> > receiving a set?
> 
> yes; wouldnt one respond with an unknown/malformed attribute
> notification, unless some alternative were prescribed.

'treat as withdraw' would seem more appropriate

Kind regards,

Job

v2.23.0 | Report a Bug | By Email