From nobody Wed Mar 3 08:19:04 2021 Return-Path: X-Original-To: spring@ietfa.amsl.com Delivered-To: spring@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6AE53A15CB; Wed, 3 Mar 2021 08:18:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.097 X-Spam-Level: X-Spam-Status: No, score=-2.097 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sh6aVc2kI-yV; Wed, 3 Mar 2021 08:18:53 -0800 (PST) Received: from mail-vs1-xe2c.google.com (mail-vs1-xe2c.google.com [IPv6:2607:f8b0:4864:20::e2c]) (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 08D203A15C5; Wed, 3 Mar 2021 08:18:53 -0800 (PST) Received: by mail-vs1-xe2c.google.com with SMTP id d25so5840212vsr.11; Wed, 03 Mar 2021 08:18:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=WsfYE1Cze9U88YmIYnAQzs6PDdSJHqCVb35B2JLQ60U=; b=XzRY040FpOX3Ck3gYXkl7R1KZjT9k6uHYBQwswg24Y3Ivqo+5Pqk63PvD71HxxcnzF BnigH3RTxeYLfx+DwM5PDjedsV2joxeAC/dREYNVfE//jZ8nULWjITghfTktCtKn7U+/ Q4OkuX4EvuC7QEe9J0kVa/B7cGHPwZSl9uNxMqAvXSm7IayAQ9KyDocbtrKD4caZ8Y09 GtUMJvaUaf+aanXclQIOnk/xVbotA1IJxXb4uvebvFgUm6wwPpO0UzpdDs1Ig7gucU6A wr3T5RBMZCcJwBt1u6kxgnOxtuqHuSpREhKEciycMBVKUbsTlEfKfpSG3EmPcD6GamK5 NNZA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=WsfYE1Cze9U88YmIYnAQzs6PDdSJHqCVb35B2JLQ60U=; b=oNoFNqeHVQP3zMgqQ3qg/yl6FM85hMDFS2Njrj5RjZYuXT9LVnrZ8UEUX1mk+40ytC rB46yzdOFhep67S4645CgL5meWlprd2YMnFQpdWzRZFjE3nnWhtT6dW1nIlSAf1+7Dhx qVv5ZDH25Q4Z2x1MkysUF5sRFy+d6fCB+vZSa8SXjvcisd3dSbL9/fad2ZdT/HHQLdQ2 AqVCJUNIEu2roJPskjUzJYUJRvJ169VhWbQs/2h51Zmj+8DaI9CLeDKhUO9Xev7LX43e R4UI7yivtiitYPq2hJJX5dmlWYVEN3rdGSMW7B8uinMop0AUavur2+DOaybc0y2G7hMJ QGmw== X-Gm-Message-State: AOAM531DQXOMWx8ZNtJS8yQpaumQNYG8Lufq00tHK9vio/cQoCTgOOar uApDzLV+ye81lmF/mBXmE/xHevahLswXVE/4WLJGQsRNxn4= X-Google-Smtp-Source: ABdhPJxmnVkh0koM3Mrr54psymmSeiLmpFRzGpcPbX3lai7n/16b3sFbeN8GM6B9iFillYB4WNO2bi6tWToGPDEQxL0= X-Received: by 2002:a05:6102:94b:: with SMTP id a11mr16226796vsi.53.1614788331137; Wed, 03 Mar 2021 08:18:51 -0800 (PST) MIME-Version: 1.0 From: "Andrew G. Malis" Date: Wed, 3 Mar 2021 11:18:33 -0500 Message-ID: To: pals@ietf.org, mpls , detnet WG , SPRING WG List Cc: "" Content-Type: multipart/alternative; boundary="000000000000dd6e2105bca43434" Archived-At: Subject: [spring] Special PALS/MPLS/DetNet/SPRING joint meeting on Friday of IETF week X-BeenThere: spring@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Mar 2021 16:18:55 -0000 --000000000000dd6e2105bca43434 Content-Type: text/plain; charset="UTF-8" Looking at the IETF 110 agenda, you may have noticed a PALS/MPLS/DetNet/SPRING joint session on Friday Session I (12:00-14:00 UTC) in Room 7. This meeting was organized as a result of three recent drafts that have raised some basic architectural issues in proposing new applications and uses at the bottom of the MPLS label stack. The MPLS WG owns the underlying architecture, while PALS and DetNet both already make use of BoS, and one of the drafts in question is proposing SR-MPLS iOAM that would also play in that space (thus SPRING is part of this meeting as well). We are not soliciting any further drafts or talks for this session. The agenda is already full, and can be found at https://datatracker.ietf.org/meeting/110/materials/agenda-110-pals-03 . The agenda lists the drafts in question, and includes URLs for them. We are also including ample time for open discussion following the presentations. You are all invited to this session, which we hope will be a productive contribution to continued discussion on the topic. Please let me know if you have any questions. I'll be the overall chair for the session, with able co-chairing from a chair of each of the invited WGs. Thanks, Andy --000000000000dd6e2105bca43434 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Looking at the IETF 110 agenda, you=C2=A0may have noticed = a PALS/MPLS/DetNet/SPRING joint session on Friday Session I (12:00-14:00 UT= C) in Room 7.

This meeting was organized as a result of = three recent drafts that have raised some basic architectural issues in pro= posing new applications and uses at the bottom of the MPLS label stack. The= MPLS WG owns the underlying architecture, while PALS and DetNet both alrea= dy make use of BoS, and one of the drafts in question is proposing SR-MPLS = iOAM that would also play in that space (thus SPRING is part of this meetin= g as well).

We are not soliciting any further draf= ts or talks for this session. The agenda is already full, and can be found = at=C2=A0https://datatracker.ietf.org/meeting/110/materials/agenda-11= 0-pals-03 . The agenda lists the drafts in question, and includes URLs = for them. We are also including ample time for open discussion following th= e presentations.

You are all invited to this sessi= on, which we hope will be a productive contribution to continued
discu= ssion on the topic.

Please let me know if you have any q= uestions. I'll be the overall chair for the session, with able co-chair= ing from a chair of each of the invited WGs.

Thank= s,
Andy

--000000000000dd6e2105bca43434--