From job@fastly.com Tue Oct 3 16:54:56 2023 Return-Path: X-Original-To: sidrops@ietfa.amsl.com Delivered-To: sidrops@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DB32C151095 for ; Tue, 3 Oct 2023 16:54:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.105 X-Spam-Level: X-Spam-Status: No, score=-2.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastly.com Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id luDRkyiJj8bX for ; Tue, 3 Oct 2023 16:54:51 -0700 (PDT) Received: from mail-ej1-x631.google.com (mail-ej1-x631.google.com [IPv6:2a00:1450:4864:20::631]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF760C15107F for ; Tue, 3 Oct 2023 16:54:51 -0700 (PDT) Received: by mail-ej1-x631.google.com with SMTP id a640c23a62f3a-9adb9fa7200so78136366b.0 for ; Tue, 03 Oct 2023 16:54:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastly.com; s=google; t=1696377290; x=1696982090; darn=ietf.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=mx1Z+AFXakxNJUet/9loJWvO4jSwz9Kto0SIMh/7dvM=; b=YGtGwTXqmtTd/fJdfvaVCK0rW0UQBOBILdJuC/Hc7RZJB/YruFSwsWu9I3dEJqv0KZ Q4dX8AtpwWV7TiZpXRsgmnz4etSeoNZY8Bw3wfqCZJYiM8vKAKs/WmjK5ykAOmbpyxNB jv+RG8R/aGg0h8wG/MCpUJi0kdW1edhucmJ9Y= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696377290; x=1696982090; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=mx1Z+AFXakxNJUet/9loJWvO4jSwz9Kto0SIMh/7dvM=; b=VCt1VQoXB5V4pqCFiacgygmJ1jXLwLqHQa2UPvahkR5//s8i1JwXPQPVSB/uLjAXLF /Si9njjOmCu0NFjqw0ZjjQjNIq/wmW/TB21d8dmqPfbG50Gs5RXbAEpHp8CwIG+gV6Jj ly9lDpNPeM5qFbJAyXnvJW7KvcnEYlqQ5aIUD9Dws9CtDePfVU3m/KEJbf/KSrAkEOJ9 eF6Uxduy+JDEHlFN6e22gA4BbwHPHGorqQVQ44WuyZFh9vYCQXJFdebhX7ek4nOgvtJi 0JH+z9zurrmNt+RoUXTwL9taIYpqBwpIBm4ZLeAqao7d0s1ctG94FG3tauCB55wokIqw 1djg== X-Gm-Message-State: AOJu0Ywqb0tUCQAuTb0TnrrNHhLiSGYJpZaHInscmXVbxmJeFIc0clVF aAm/k5gzlozOQ1DXOGbrpFnQLVd4x4nPH+zHTD/DNw== X-Google-Smtp-Source: AGHT+IEMPja8lT+Bh5nevlJt3yydp59tdzbJZ3AlWgzWYyogl5VrleQS2vvgKdsY84tFuupQ3VbDMg== X-Received: by 2002:a17:907:75f5:b0:9b2:b755:5b94 with SMTP id jz21-20020a17090775f500b009b2b7555b94mr530210ejc.38.1696377289915; Tue, 03 Oct 2023 16:54:49 -0700 (PDT) Received: from snel ([2a10:3781:276:3:16f6:d8ff:fe47:2eb7]) by smtp.gmail.com with ESMTPSA id jo3-20020a170906f6c300b0099df2ddfc37sm1783533ejb.165.2023.10.03.16.54.49 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 03 Oct 2023 16:54:49 -0700 (PDT) Date: Wed, 4 Oct 2023 01:54:47 +0200 From: Job Snijders To: Warren Kumari Cc: Claudio Jeker , SIDR Operations WG Message-ID: References: <169536573828.13264.7436469383111995258@ietfa.amsl.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: Re: [Sidrops] I-D Action: draft-ietf-sidrops-8210bis-11.txt X-BeenThere: sidrops@ietf.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: A list for the SIDR Operations WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Oct 2023 23:54:56 -0000 Dear Warren, On Tue, Oct 03, 2023 at 02:59:04AM +0300, Warren Kumari wrote: > > I disagree with this proposed proceeding. > > > > 1) If I recall correctly, two RTR indepenednt implementers suggested the > > flags field to be zeroized. Yet, the authors of > > draft-ietf-sidrops-8210bis went another direction. (??!!) > > Ah, I had understood that this option had been agreed to by the WG. If > this is not in fact the case, then I suspect it will need to go back > through the WG to have consensus called (hopefully only on this > point). Two independent implementers suggested: 'forcing all 16 flag bits to zeri is probably the best course' https://mailarchive.ietf.org/arch/msg/sidrops/H7dB6GQ5Flly-Dtim5N_7dAeU34/ 'It is probably enough to remove / force-to-zero the AFI flags field in the ASPA PDU.' https://mailarchive.ietf.org/arch/msg/sidrops/MZhj8HZXj0Tu3rKtCyahF8eFxAA/ I think it is appropriate for this document to come back to the working group, and before moving forward again, that there is a actual demonstration of implementations by virtue of reports about those implementation efforts. I'll do my part in trying to provide running code. In the previous WGLC for 8210bis zero implementation reports were shared with this working group. :-( At this point in time it is not clear to me what relationship exists - if any - between RTR implementation projects adding support for ASPA, and the authors of the 8210bis document, but it's not hard to imagine that a disconnect between the two sides of the coin would make efforts in this context harder than needed, as we are seeing feedback being ignored. To overcome such a potential disconnect, I think it would be reasonable to ask Claudio Jeker and Martin Hoffman to edit the rfc8210bis document before putting it up for WGLC again. Kind regards, Job