Re: [MBONED] mboned notes ietf 118 (fwd)
stefán atli jónasson <stefanajons@gmail.com> Thu, 09 November 2023 19:17 UTC
Return-Path: <stefanajons@gmail.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E6A1C18E527 for <mboned@ietfa.amsl.com>; Thu, 9 Nov 2023 11:17:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, 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 (2048-bit key) header.d=gmail.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 02-nY-L22F1K for <mboned@ietfa.amsl.com>; Thu, 9 Nov 2023 11:17:29 -0800 (PST)
Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (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 E5F24C187702 for <mboned@ietf.org>; Thu, 9 Nov 2023 11:17:28 -0800 (PST)
Received: by mail-ed1-x529.google.com with SMTP id 4fb4d7f45d1cf-53de8fc1ad8so1977435a12.0 for <mboned@ietf.org>; Thu, 09 Nov 2023 11:17:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1699557446; x=1700162246; darn=ietf.org; h=content-transfer-encoding:mime-version:message-id:references :in-reply-to:user-agent:subject:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=r1M5iC/dAi/zMeG4ThqOLxnc0ZsIUGjk95v6/b2qkgw=; b=TJUJ+OudsjTbdfnUDTyIiUgg9bTRKNZdXrx8vzxdrPnrsXdIySWY/MtsMHmkKGMEqP WQmBJP8SqFF9vJXUKaTlcci8zlyJjgpY3pSfgRyx1xL8BuJ/jR4BKuvkb5vJkFq438C1 G/SAqm5d7L16l6ys/U34DrcS7Uxew7vBRAEknVVRoom6mgNxOAzZIVjtgasBAbwtRamw 83E6yST0ksUAsjz/AvgnQquRWZ9WYQFAQVcctJuV634+GvCSnKVFbxF3c6OautFk93r5 X2BzRwfyLri5hpmKF9Nk6OW1nOeVxEq+21z8cC+lr9mu9ymt4klzs9AvmPkk8bgUsafJ EjLQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699557446; x=1700162246; h=content-transfer-encoding:mime-version:message-id:references :in-reply-to:user-agent:subject:to:from:date:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=r1M5iC/dAi/zMeG4ThqOLxnc0ZsIUGjk95v6/b2qkgw=; b=VByFJ77GhKn0bR2Hr86KksiyDfdI3sRKX0EKB2ND4E4C/WYJcmwDwh5S+DzmWc/Vmf nItGhZOz0KTPg0OeZ6AtMRFcT1t21/HBAGDpO5cIG+hCrl9BNUpxdLDYIJzvlK39H2x7 NSoJxbEzM3t3573+DrQQBIehVt8WobFF3QzmoacI929InLhM9qHQY4ovqDcDlU/Rm8MT FPrsAPF/aTvIS2/cy12yRqN5EINqyD6SKry0VNB/2MnDsAn+HcKclqUONtAGcIFjAHHY is8gMhLWxdoD/XEFlt3HhD10I5UpfVe8/sKjyweaxamoS6nwp/Lw6qupHcNEXOOhm3+/ 0hPQ==
X-Gm-Message-State: AOJu0Yxxy/aE9gd8tYHWhgdXjkTggsj9u5vUmbw5zF2E8MdOXVupTlmb ufc4NCsjX7xtqAkzdAD/VFMcMQLsbvi77w==
X-Google-Smtp-Source: AGHT+IFNwkjetQyL1RXRo6ubZ7jesVzfF58vupLQEovQpgqItUFyMtogpkAPyyukG09J8LFUuEWEYw==
X-Received: by 2002:a50:c31d:0:b0:544:fc51:cd9f with SMTP id a29-20020a50c31d000000b00544fc51cd9fmr4549465edb.42.1699557446152; Thu, 09 Nov 2023 11:17:26 -0800 (PST)
Received: from ?IPv6:::1? ([2a01:6f02:319:491:1:0:ed96:7b54]) by smtp.gmail.com with ESMTPSA id q20-20020a056402041400b0053e8bb112adsm173450edv.53.2023.11.09.11.17.25 for <mboned@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 09 Nov 2023 11:17:25 -0800 (PST)
Date: Thu, 09 Nov 2023 19:17:15 +0000
From: stefán atli jónasson <stefanajons@gmail.com>
To: mboned@ietf.org
User-Agent: Mail for Android
In-Reply-To: <c45a06a9-12f3-caf5-aef6-84fb10f94de3@juniper.net>
References: <f5424b8e-5873-f22a-3cf9-e1f5a8298b70@juniper.net> <c45a06a9-12f3-caf5-aef6-84fb10f94de3@juniper.net>
Message-ID: <4838F828-FA33-4F3B-921D-30F8F886FBFF@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----25BWYOGZSG6HY011KVM1C170JJEFO0"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/5pTlIF9M38V4xvf3p3MqkabPqKc>
Subject: Re: [MBONED] mboned notes ietf 118 (fwd)
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Nov 2023 19:17:33 -0000
I just need the mapp Þann 9. nóvember 2023 19:14:00 GMT+00:00, skrifaði Leonard Giuliano <lenny=40juniper.net@dmarc.ietf.org>: > >Also, forgot to thank Stig for taking these notes. Lots of discussion and >back-and-forth, so we greatly appreciate these notes under such >challenging conditions. > > >On Thu, 9 Nov 2023, Leonard Giuliano wrote: > >| >| MBONEDers- here are the notes from today's mtg. Please take a look and add >| any fixes you might see now that it's fresh on the mind. You can send edits >| to the chairs, or just edit directly at: >| >| https://notes.ietf.org/s/notes-ietf-118-mboned# >| >| ***** >| >| Notes from mboned >| >| Multicast telemetry doc passed wglc since 117 >| Looking for shepherd. >| -Max volunteered to shepherd >| >| YANG model draft. Sandy says received some comments from Tom and will update. >| Sandy says redundant ingress failover doc should be ready for wglc >| AMT yang model draft needs more review and comments. >| >| Updates on MTTB drafts from Max. Dorms may be ready for wglc. >| >| Multicast Extensions for QUIC >| Dino asking how it is working with keys. >| Asking if retransmit as uc or mc if many clients don't act. Basic idea is that >| draft doesn't specify how to retransmit. Saying how unicast might be better if >| multicast failures. >| Toerless asking if thought about NAT >| Not sure if I got that right. >| Someone (one of the authors?) saying that can kick client off multicast if too >| many failures. >| A comment that many options how to do acks, may not need to ack every packet. >| Mathias asking if this is just SSM. It seems that way. >| Someone (think an author) saying this is harder for ASM with many sources. >| >| Ice asking if routers do QUIC, I think. >| Someone clarifying that lost packets are not retransmitted, but rather data is >| retransmitted. >| >| Dino asking for more details on integrity. >| Integrity frames are sent over unicast. Contains checksums of packets. Used to >| verify multicast packets. >| >| Lucas Pardue Explaining about other approaches for integrity. >| >| Francois Michel >| Commenting on many to many, didn't get it, but presenter says out of scope for >| now. >| >| Juliusz >| Asking about what crypto to use. Presenter says he can't recommend a specific >| one. >| >| Lenny >| Cautions about adding complexity to address ASM. May make it harder to deploy. >| Interdomain ASM was deprecated for a reason, recommend keeping scope at >| SSM-only. >| >| Dino >| Asking if DH on multicast channels, rather than publishing shared key. >| Juliusz mentions that 2 layers, encryption and authentication. >| >| Toerless >| Make it slow enough for the slowest guy? >| Presenter says can be different channels with different rates. >| Rely on clients joining slower channels if rate is too high for them. >| Suggesting can keep it simple and just throw slowest guy out if needed. >| Presenter says draft not specifying whether 1 or multiple channels. Not >| specified. >| Toerless says a draft on multi channel behavior may be needed. >| >| Francois Michel >| Missed comment. >| >| Juliusz >| Asking if can do FEC for unreliable data. Says can work well. >| Presenter says easy to do. >| >| Gorry >| Says congestion control in QUIC is very terse. >| >| Hitoshi asking about use of different FEC for different clients I think. Seems >| not something they thought about. >| >| Dino asking about cost of signatures. Whether to do it over just a few bytes >| or not. Maybe it can be cheap. >| >| Lucas talking about how use cases are important. >| >| Gorry Says a separate draft on congestion control could be useful to get help >| from CC experts. Says vital to get it right. >| Greg asking if CC would be in QUIC itself or applications using it. >| Historically for multicast it's been in the application. >| Gorry not sure right now. >| Toerless, there is a CC WG. >| >| >| Scalability analysis comparison of multicast/BIER forwarding mechanisms >| (https://atlas.cs.uni-tuebingen.de/*menth/papers/Menth21-Sub-5.pdf) >| Michael Menth, 20 min >| >| Juliusz >| Made some comment on worst case, I missed it. >| >| Greg >| Does not agree what presenter said about bier being bad for small groups. It >| may not generally be true. >| It depends on whether receivers are in the same bitset. >| >| Dino >| Asking why multiple sets if few members. Greg is explaining. >| >| No more questions. >| >| TreeDN update by Lenny >| WGLC soon in mops wg >| input from MBONED and PIM would be welcome >| >| >| >| >| >| >| >| >| >| >| >| > >_______________________________________________ >MBONED mailing list >MBONED@ietf.org >https://www.ietf.org/mailman/listinfo/mboned
- [MBONED] mboned notes ietf 118 (fwd) Leonard Giuliano
- Re: [MBONED] mboned notes ietf 118 (fwd) Leonard Giuliano
- Re: [MBONED] mboned notes ietf 118 (fwd) stefán atli jónasson