Re: [sipcore] Milestones changed for sipcore WG

Brian Rosen <br@brianrosen.net> Thu, 02 June 2022 14:15 UTC

Return-Path: <br@brianrosen.net>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D259C15AAF5 for <sipcore@ietfa.amsl.com>; Thu, 2 Jun 2022 07:15:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.898
X-Spam-Level:
X-Spam-Status: No, score=-6.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=brianrosen-net.20210112.gappssmtp.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 vxQuR5kBgAPC for <sipcore@ietfa.amsl.com>; Thu, 2 Jun 2022 07:15:28 -0700 (PDT)
Received: from mail-io1-xd36.google.com (mail-io1-xd36.google.com [IPv6:2607:f8b0:4864:20::d36]) (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 6EB4FC15AAF4 for <sipcore@ietf.org>; Thu, 2 Jun 2022 07:15:28 -0700 (PDT)
Received: by mail-io1-xd36.google.com with SMTP id i9so4915264ioa.6 for <sipcore@ietf.org>; Thu, 02 Jun 2022 07:15:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen-net.20210112.gappssmtp.com; s=20210112; h=from:content-transfer-encoding:mime-version:subject:date:references :to:in-reply-to:message-id; bh=M0++gSmjaOB+kTGGEjw0mHWw5DYE0h74kI/7I6oq3Gk=; b=7gcYrdQYExQSOuMksb5IpvV1Iv5RZuL6JT7muV4PCRvrlSih9X1qQqTIWE5T45kwho h/Jgz85mOpmuaMczON0AWBYFIxmAJ48cvgSsE/fww7G4ChiWWDO3SPoHtH4GWBX9XcSE Yc3D2hVH0IWCKBFy18Zw4eptCMR/Zs5L4QrOBdd/9wvzpGDI/UGEUZqDLM0bXQ9p3CSW In+35KWQiLmrUaHRyDggu6O8Dl6BYMnSe1/K+WEgimxPQsCi8F2EevsL0Cr12mwlaX84 hi+MXgUUQVAEymLUzZxxxbGTuMv92SQY6VwdU+Foj1vXGhjz+1OIlnwzjn0+N/qr3e44 lOQA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=M0++gSmjaOB+kTGGEjw0mHWw5DYE0h74kI/7I6oq3Gk=; b=ZtvQYOjIj6S9WWkTeo9Wqj8Qck0GdJLJJYOrbviHiK+aXJhlbBu/Z7orOrkaAIP8+Q Q1hgE1sJryUUPkXxbeymDFz3XUj7750VgNsYekevtAHvkPsLcsdPy9QfDeAJloje2gui CLfo94L2bKlcuDShGvvXd8DE+xReU3gezoRRABqlH+fFrIjQNvQJcs9rkZuxgQWD9E2G lgmm4P0qCZ/lhZAuEqqkCYIUC/M51ujpGlm15OOTewjrbWlFxDqHuVlIfTWdEhsY1kjR Ix5908TVMNbSWqwP+kgK8r9djNtVBaLKl+zh4grDZHpxRO+AKpYZZyAgjAfSvivIni+M Wo6g==
X-Gm-Message-State: AOAM533MlUIhHAFKxyVwPeil+LXNVawrldDCS0QDnx40kbbeNHbrgvQP RK5rMS8+Jsb39UNVSNY7TQ4papPezmq/Qv+5
X-Google-Smtp-Source: ABdhPJxanYtfRzGSNH+6kTh0xjW55JBi4Q1wx1RookEyFMtFs2VmzkfUZzwgY3UADiYR4bsgbb/cgA==
X-Received: by 2002:a05:6602:1510:b0:664:c918:e025 with SMTP id g16-20020a056602151000b00664c918e025mr2623579iow.19.1654179327585; Thu, 02 Jun 2022 07:15:27 -0700 (PDT)
Received: from smtpclient.apple (dynamic-acs-24-154-121-237.zoominternet.net. [24.154.121.237]) by smtp.gmail.com with ESMTPSA id k25-20020a02ccd9000000b00331598832besm1171632jaq.25.2022.06.02.07.15.26 for <sipcore@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 02 Jun 2022 07:15:27 -0700 (PDT)
From: Brian Rosen <br@brianrosen.net>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.31\))
Date: Thu, 02 Jun 2022 10:15:24 -0400
References: <165417913635.24135.12333953994619989579@ietfa.amsl.com>
To: sipcore@ietf.org
In-Reply-To: <165417913635.24135.12333953994619989579@ietfa.amsl.com>
Message-Id: <53812A62-BB0E-4DF7-B734-67F5285B879B@brianrosen.net>
X-Mailer: Apple Mail (2.3696.100.31)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/myPlODrGtuOFccRBe55528LXY0A>
Subject: Re: [sipcore] Milestones changed for sipcore WG
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jun 2022 14:15:29 -0000

Milestone approved: Robert please submit a sipcore -00.

Brian


> On Jun 2, 2022, at 10:12 AM, IETF Secretariat <ietf-secretariat-reply@ietf.org> wrote:
> 
> Changed milestone "Request publication of a SIP response code for unwanted
> communications ", set description to "Request publication of a SIP response
> code for unwanted communications".
> 
> Changed milestone "Allow Multiple Reasons values per protocol", set state to
> active from review, accepting new milestone, set description to "Multiple
> Reasons values per protocol (PS) to the IESG".
> 
> URL: https://datatracker.ietf.org/wg/sipcore/about/
> 
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore