[netconf] Re: Call for IETF 120 NETCONF Slot Requests
Per Andersson <per.ietf@ionio.se> Sun, 30 June 2024 16:13 UTC
Return-Path: <perkietf@gmail.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACB78C14F5F7; Sun, 30 Jun 2024 09:13:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.653
X-Spam-Level:
X-Spam-Status: No, score=-1.653 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
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 L4fZ1XZYNxm8; Sun, 30 Jun 2024 09:12:59 -0700 (PDT)
Received: from mail-pf1-f179.google.com (mail-pf1-f179.google.com [209.85.210.179]) (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 CAAE8C14F5F5; Sun, 30 Jun 2024 09:12:54 -0700 (PDT)
Received: by mail-pf1-f179.google.com with SMTP id d2e1a72fcca58-7066c799382so1833680b3a.3; Sun, 30 Jun 2024 09:12:54 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1719763974; x=1720368774; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=YGjbq8uNZqUmdHyczccPk7MfE4zLE4wSNNCC74qYkRg=; b=n0GXe3+h76iCeQcM/7bnlPe8qZ5K9t/sg65gd1J/B578ROFIV2+hpk7NmEpW91LnFL cJMGOk471WkLqIDyrRQ2H0SjL5wjxNvCRdpW3dZY/GG2Rk3RRcmEHfIdXVQFTJpIkMUE y4Idksf5IM+rMSnCTknpzJ3sm9GwJbbcmCBO0XO4Z6XqNMvBXrud0LR7QiVuUVN4m/dA STTzNPQJgjoziFSTfcUKKEGt0wWB+NIuwZMY831HW3wbvRcNiE/vdLM1yogKkvS+jo3q w9wtkJgItT5OzXQtfptlhTgcsoHzb2QYgaQ3nLNP4MyqVUT2CFiEM5frcoJjiZzXzqS7 93oQ==
X-Forwarded-Encrypted: i=1; AJvYcCWVASoWQuR5EVHm+D6JoAGP2cfHAPZqW0dju/JnnLEKKhmgAPSYEVi37L+ZEUjqpzKSybo3B+ZzBaUEzfc7ijdPNFoeUFIAa/J175b6K5oEgXf8VQByk+f1Ew==
X-Gm-Message-State: AOJu0Yw1fx9VmmoKYhH063xpqjO7a83o/ZATV78dFpnF5qRT3fVRfkRe W6bde/1XGeUsavYaqfmnVDHjLQKK21d+C+EoYkRPCSZ/jhmBBYa7uQZyIM37
X-Google-Smtp-Source: AGHT+IHs00SDZ3e8qLgwtQHIkAnF/bFrJtqPuTO4F23O7R0hLZHK5aL9cY2BjRT8FdveGVBEp22vcg==
X-Received: by 2002:a05:6a00:814:b0:706:5d85:61a5 with SMTP id d2e1a72fcca58-70aaad3b2camr5780276b3a.8.1719763974006; Sun, 30 Jun 2024 09:12:54 -0700 (PDT)
Received: from mail-pf1-f179.google.com (mail-pf1-f179.google.com. [209.85.210.179]) by smtp.gmail.com with ESMTPSA id d2e1a72fcca58-708020579e2sm4850328b3a.42.2024.06.30.09.12.53 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 30 Jun 2024 09:12:53 -0700 (PDT)
Received: by mail-pf1-f179.google.com with SMTP id d2e1a72fcca58-70abb539f41so311758b3a.2; Sun, 30 Jun 2024 09:12:53 -0700 (PDT)
X-Forwarded-Encrypted: i=1; AJvYcCWImFBeLXN3j2f7yPDyU0aVzMy81XIc17TUi37QMrXf1+okhCctouXv1zQL+tkrM3wf+tKezE5X25vYEyfYrtKIMnc9foj2LL/b6ZyuqCY4eOUVgvzDCOSmeg==
X-Received: by 2002:a05:6a20:431b:b0:1be:e1e1:d5de with SMTP id adf61e73a8af0-1bef613f48bmr5571528637.30.1719763973515; Sun, 30 Jun 2024 09:12:53 -0700 (PDT)
MIME-Version: 1.0
References: <0100019055249c75-7ba07162-6d07-479b-b370-c3cfe64d5bc7-000000@email.amazonses.com> <63699b4a05ec4c2395e250ce7f7cff0f@swisscom.com>
In-Reply-To: <63699b4a05ec4c2395e250ce7f7cff0f@swisscom.com>
From: Per Andersson <per.ietf@ionio.se>
Date: Sun, 30 Jun 2024 16:12:42 +0000
X-Gmail-Original-Message-ID: <CACvbXWH2egSxXFhfnrnp7TcigMomNdw6Si_8FL3kXvrG+_0GoQ@mail.gmail.com>
Message-ID: <CACvbXWH2egSxXFhfnrnp7TcigMomNdw6Si_8FL3kXvrG+_0GoQ@mail.gmail.com>
To: Thomas.Graf@swisscom.com
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: DXHVYYGTDPV43PVGU77FBO5EYUNQ6BQS
X-Message-ID-Hash: DXHVYYGTDPV43PVGU77FBO5EYUNQ6BQS
X-MailFrom: perkietf@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-netconf.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: netconf@ietf.org, netconf-chairs@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [netconf] Re: Call for IETF 120 NETCONF Slot Requests
List-Id: NETCONF WG list <netconf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/Cy5FNVJvrEaUr_34qFp1lKhcS5I>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Owner: <mailto:netconf-owner@ietf.org>
List-Post: <mailto:netconf@ietf.org>
List-Subscribe: <mailto:netconf-join@ietf.org>
List-Unsubscribe: <mailto:netconf-leave@ietf.org>
Hi I have noted your eight (8) slot requests for IETF 120. -- Per On Sun, Jun 30, 2024 at 10:22 AM <Thomas.Graf@swisscom.com> wrote: > > Dear Kent and Per, > > > > Thanks a lot. > > > > I like to request for myself and Alex Huang-Feng > > > > 15 minutes to > > > > Introduce > > > > An Architecture for YANG-Push to Message Broker Integration > > https://datatracker.ietf.org/doc/html/draft-ietf-nmop-yang-message-broker-integration > > > > and update on > > > > YANG model for NETCONF Event Notifications > > https://datatracker.ietf.org/doc/html/draft-ahuang-netconf-notif-yang-05 > > > > Support of Versioning in YANG Notifications Subscription > > https://datatracker.ietf.org/doc/html/draft-ietf-netconf-yang-notifications-versioning-05 > > > > Support of Hostname and Sequencing in YANG Notifications > > https://datatracker.ietf.org/doc/html/draft-tgraf-netconf-notif-sequencing-06 > > > > Support of Network Observation Timestamping in YANG Notifications > > https://datatracker.ietf.org/doc/html/draft-tgraf-netconf-yang-push-observation-time-02 > > > > > > and 15 minutes to update on > > > > UDP-based Transport for Configured Subscriptions > > https://datatracker.ietf.org/doc/html/draft-ietf-netconf-udp-notif-13 > > > > YANG Groupings for UDP Clients and UDP Servers > > https://datatracker.ietf.org/doc/html/draft-ietf-netconf-udp-client-server-03 > > > > Subscription to Distributed Notifications > > https://datatracker.ietf.org/doc/html/draft-ietf-netconf-distributed-notif-09 > > > > For draft-ietf-netconf-udp-notif-13, draft-ietf-netconf-udp-client-server-03 and draft-ietf-netconf-distributed-notif-09 we would like to request working group last call at IETF 120. > > > > We are both looking forward to meet in person in Vancouver. > > > > Best wishes > > Thomas > > > > From: Kent Watsen <kent+ietf@watsen.net> > Sent: Wednesday, June 26, 2024 5:23 PM > To: netconf@ietf.org > Cc: netconf-chairs@ietf.org > Subject: [netconf] Call for IETF 120 NETCONF Slot Requests > > > > Be aware: This is an external email. > > > > NETCONF WG, > > The final agenda for IETF 120 has been posted > - https://datatracker.ietf.org/meeting/120/agenda > > The NETCONF session information is scheduled to be held: > > Thursday, July 25, 2024 > > Morning Session 1 > > 09:30 - 11:30 PST > > 11:30 - 13:30 EST > > 16:30 - 18:30 UTC/GMT > > 00:30 - 02:30 CST (next day) > > Room: Georgia A > > ICS: https://datatracker.ietf.org/meeting/120/session/33055.ics > > > > This will be an in-person meeting with remote participation access. > > All authors of working group documents are expected to provide a > > status update to the WG. Status includes, at a minimum, recent > > changes, open issues, and plan to complete documents. Status > > can be provided via either: > > A) A report during the IETF session (preferred) > B) or an e-mail to WG list, sent no later than the Internet-Draft > > submission cut-off > > > > Please send slot requests to netconf-chairs@ietf.org (CC-ed) before > > the end of the day Monday July 8 (any TZ, but earlier is appreciated). > Please include draft names(s), presenter, desired slot length. Also, > please let us know if you think the topic would be better covered in a > Virtual Interim to be held at a future date. > > Thank you! > > Per and Kent > > Important dates (https://datatracker.ietf.org/meeting/important-dates) > 2024-07-08 Monday Internet-Draft submission cut-off by UTC 23:59. > 2024-07-10 Wednesday Draft Working Group agendas due by UTC 23:59. > 2024-07-15 Monday Revised Working Group agendas due by UTC 23:59.
- [netconf] Call for IETF 120 NETCONF Slot Requests Kent Watsen
- [netconf] Re: Call for IETF 120 NETCONF Slot Requ… Thomas.Graf
- [netconf] Re: Call for IETF 120 NETCONF Slot Requ… Per Andersson
- [netconf] Re: Call for IETF 120 NETCONF Slot Requ… Per Andersson
- [netconf] Re: Call for IETF 120 NETCONF Slot Requ… Thomas.Graf
- [netconf] Re: Call for IETF 120 NETCONF Slot Requ… Per Andersson
- [netconf] Re: Call for IETF 120 NETCONF Slot Requ… Zhuoyao Lin
- [netconf] Re: Call for IETF 120 NETCONF Slot Requ… Per Andersson
- [netconf] Re: Call for IETF 120 NETCONF Slot Requ… Jean Quilbeuf
- [netconf] Re: Call for IETF 120 NETCONF Slot Requ… Per Andersson
- [netconf] Re: Call for IETF 120 NETCONF Slot Requ… Thomas.Graf