Re: [spring] WGLC - draft-ietf-spring-srv6-network-programming (off-topic)

S Moonesamy <sm+ietf@elandsys.com> Sat, 29 February 2020 13:52 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5924A3A0AF8 for <ietf@ietfa.amsl.com>; Sat, 29 Feb 2020 05:52:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.697
X-Spam-Level:
X-Spam-Status: No, score=-1.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.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 oyMuvniymsK3 for <ietf@ietfa.amsl.com>; Sat, 29 Feb 2020 05:52:29 -0800 (PST)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 7A0913A0AE9 for <ietf@ietf.org>; Sat, 29 Feb 2020 05:52:19 -0800 (PST)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.116.118.2]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 01TDq3aX010883 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 29 Feb 2020 05:52:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1582984336; x=1583070736; i=@elandsys.com; bh=km+/GuZQ1WQsN/k2Q+Eks4VQWbGZPb0bPaOLojL0PK0=; h=Date:To:From:Subject:In-Reply-To:References; b=xFaM+5TehK/1z0ZSY5TCmK/EsQLIPQqCzd0QWMYw4l+Up4ao++TiHsTuiL7rGPykx Hps0yCThN/u1pmbMWgMgKQEzrCUsAl/mBeqchzVifwX9wngaKoV2PBE7WENGsYV7V4 In2FaPvQRV3G4V8heUwQM5dTi6bwXC5YxTgyvM2w=
Message-Id: <6.2.5.6.2.20200229052740.0bf7fc08@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 29 Feb 2020 05:48:51 -0800
To: Robert Raszuk <robert@raszuk.net>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: [spring] WGLC - draft-ietf-spring-srv6-network-programming (off-topic)
In-Reply-To: <CAOj+MMHYXydkzOc5WrkoGdfUmFq+zuNsxGy+qqkAHYNUFK0KuA@mail.g mail.com>
References: <17421_1575566127_5DE93B2F_17421_93_1_53C29892C857584299CBF5D05346208A48D1A3DA@OPEXCAUBM43.corporate.adroot.infra.ftgroup> <5518_1582908787_5E594573_5518_436_1_53C29892C857584299CBF5D05346208A48DD1BCA@OPEXCAUBM43.corporate.adroot.infra.ftgroup> <C8417F71-D61E-42AC-831E-B85269D5D4A5@steffann.nl> <9b677b7c-fe52-dbae-7f83-2b5be5194325@gont.com.ar> <6.2.5.6.2.20200228132634.1060a610@elandnews.com> <CAOj+MMHYXydkzOc5WrkoGdfUmFq+zuNsxGy+qqkAHYNUFK0KuA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZTjfPzGR8tO8dqbH4m52xa_deIQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Feb 2020 13:52:42 -0000

Dear Mr Raszuk,
At 02:36 PM 28-02-2020, Robert Raszuk wrote:
>His information about 6man AD not accepting the Errata: 5933 is 
>correct. Errata must be first accepted by an AD then processed 
>further. Since it was posted on 11th Dec 2019 it was still not 
>accepted at first stage. You are mixing AD acceptance / validation 
>with IESG decision. Those are completely different errata processing phases.

Once an erratum is reported [1], a report is automatically sent to 
the Working Group Chair(s), the author(s) and the Area 
Directors.  The relevant Area Director ensures that there is adequate 
review and the erratum is classified.  There isn't any IESG decision 
for the errata processing phases.

Regards,
S. Moonesamy

1. https://www.rfc-editor.org/errata/eid5646