[Teas] Status update and plans for draft-ietf-teas-gmpls-signaling-smp

Jeong-dong Ryoo <ryoo@etri.re.kr> Wed, 22 July 2020 15:41 UTC

Return-Path: <ryoo@etri.re.kr>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF8A93A0AA1 for <teas@ietfa.amsl.com>; Wed, 22 Jul 2020 08:41:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.103
X-Spam-Level: *
X-Spam-Status: No, score=1.103 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_IMAGE_ONLY_16=1.092, HTML_MESSAGE=0.001, MISSING_MIMEOLE=1.899, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dooray.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 f6NVSctWKw0t for <teas@ietfa.amsl.com>; Wed, 22 Jul 2020 08:41:45 -0700 (PDT)
Received: from mscreen.etri.re.kr (mscreen.etri.re.kr [129.254.9.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 467603A0A19 for <teas@ietf.org>; Wed, 22 Jul 2020 08:41:42 -0700 (PDT)
Received: from unknown (HELO send001-relay.gov-dooray.com) (211.180.235.152) by 129.254.9.16 with ESMTP; 23 Jul 2020 00:41:33 +0900
X-Original-SENDERIP: 211.180.235.152
X-Original-MAILFROM: ryoo@etri.re.kr
X-Original-RCPTTO: teas@ietf.org
Received: from [10.162.225.109] (HELO send002.gov-dooray.com) ([10.162.225.109]) by send001-relay.gov-dooray.com with SMTP id 73be71185f185e34; Thu, 23 Jul 2020 00:41:40 +0900
DKIM-Signature: a=rsa-sha256; b=kPOauAJifNuvfkSn/LmZDOF+FiGpZKB3/W0Se8zv0BhMM7nEXflIPKtBd1iNnAhzWXScThh4eR CRQI4slBEziAw6vJYrMeK0CaVC8i5TZgs63kIzVeWSbhMuikvvvw+L49TKIgSznq7uYtaNikGzCA qwN8O40Yf2Y6pvSMn7LCOnVlzd9gp5GVbdDm46MyDOX/mHawGMf73swQTn6kfoXQj7EHn1iA7//r i5+NO0qIqx7wOvKlb5xozmW9hfX7ey3OZqvh3Tlz2aqgXzHiSvzkvbOmGtRRPK+BAtf2APPikSHg 7RUxdezrK2w7tCAr2UxD0If48M9vqlz4E5RhlfvQ==; c=relaxed/relaxed; s=selector; d=dooray.com; v=1; bh=7fyxCgfq9HZ9qOqb4n/Jt6nyAs+Jvgm6AoaOkQbutuA=; h=From:To:Subject:Message-ID;
From: Jeong-dong Ryoo <ryoo@etri.re.kr>
Cc: teas@ietf.org
Message-ID: <l8bk1aepo8e0.l8bk1aeqn23d.g1@dooray.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_214978_1665973807.1595432499076"
X-Dsn-Request: true
Importance: Normal
X-Priority: Normal
X-MSMail-Priority: Normal
To: teas-chairs@ietf.org
Date: Thu, 23 Jul 2020 00:41:39 +0900 (KST)
Sender: ryoo@etri.re.kr
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/HHNix3-2nzhursI5iD5kh9bcDfM>
Subject: [Teas] Status update and plans for draft-ietf-teas-gmpls-signaling-smp
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jul 2020 15:41:54 -0000

Dear TEAS WG Chairs and all,

The following is the status update and plans for draft-ietf-teas-gmpls-signaling-smp:
Current Status: &nbsp; - Version -03 uploaded in March 2020.      &nbsp; - Added text to describe how "Notify" messages are used to perform notifications for resource availability associated with preemptions, based on the discussion at IETF 105.&nbsp; -&nbsp;Two new sub-codes, "Shared resource &nbsp;unavailable" and "Shared resource available," are introduced under "Notify Error" code.

Open Issues:    &nbsp;&nbsp; - A new field to be defined for preemption priority&nbsp; &nbsp;- Clarify that APS configuration is out-of-scope of this document

Next Steps:&nbsp; - Publish a new revision that addresses the open issues

That's all, thank you.

Best regards,

Jeong-dong (on behalf of coauthors)