Re: [core] progressing ietf-core-yang-cbor and ietf-core-sid

Ivaylo Petrov <ivaylo@ackl.io> Wed, 08 January 2020 22:25 UTC

Return-Path: <ivaylo@ackl.io>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AF5112010C for <core@ietfa.amsl.com>; Wed, 8 Jan 2020 14:25:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=ackl-io.20150623.gappssmtp.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 OXy1PxNF2sWv for <core@ietfa.amsl.com>; Wed, 8 Jan 2020 14:24:58 -0800 (PST)
Received: from mail-wm1-x336.google.com (mail-wm1-x336.google.com [IPv6:2a00:1450:4864:20::336]) (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 D879E1200C7 for <core@ietf.org>; Wed, 8 Jan 2020 14:24:57 -0800 (PST)
Received: by mail-wm1-x336.google.com with SMTP id a5so688696wmb.0 for <core@ietf.org>; Wed, 08 Jan 2020 14:24:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ackl-io.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=kDem4OJiRJhtZjADmGZawO9ndUOjH1E8kWIGFsl5Y+A=; b=0zaPgAFJgMHgKQIDWK7YHcLBshFRx5DzzUXAG4PaJxS3+b/p0GwRVhud/FXJGh2CIr 3dBMRIcikaEVfG510ij+aQG3AWdzZpfADRTG6BnVMsObfeIwjmP2d+2r5PTMQ/WgJbNB Er6ylAuaXYJATbeRLMHv3vEPfSphoPDLYBqk13cq0VvgS5tLdnOjjV30aQN2XpTBwqKl 2uvZe4Jf5Zv/whzxa5KXWIivqht7IBQr0EahZlU3RFbS2x7YfyC2OfqrpUmg0VOLiYl7 QpBFfIXqP4oGoMJNFb1e9CRAf7wNYP9S2NVMhVNWX3exJPU/3avmB7hS9Z8cYs3lj4G1 3jQA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=kDem4OJiRJhtZjADmGZawO9ndUOjH1E8kWIGFsl5Y+A=; b=KaJtZ0pf13HFdds6VCxyMTTBKngbIabr/vP+oWXBJzQmp6h5TbGAL2/KhiQAb7prkc YF4STVL3LNeTvvkWJNgowUWDOJUrUJF/iOIugDu3DaUPiJCnoY041xEyO8myQpr2CdtX i6j3AYARfL8rsqvy554tkvwbBI/EgjtgYmzwA2jrbhpryiqnRHf4JdEakyeSI7cCB2Jk JSaARaiLlIzWaDhpJ6DKC9gNaH5lePO9xeEHPacT2RIBAip6VnEdlDMRrUKK5qOYrjJg Tx1F94j6RWOyiyk1yu9VNS2MIRtQzKDxO27fz4khKhIsbT4d6OacsfXSnn+m4BhW86Dy 8d9Q==
X-Gm-Message-State: APjAAAWT0sLydAbi/jcCvdI5k/DtMt2j6yFe5aP/7KQxYV626l6wDPlw VT4Vjv6G2fxhVzluWh05xLsbutaDMuWsO+6midO+SPbUOyk=
X-Google-Smtp-Source: APXvYqyUSg3fDSqCeb+9HXRHz1oMgcmviovVS+n/slapU/ibiOD0HC5Ei34ZQfTBZZ9Uzs1+jBpUDYWif+J2UMjrhkc=
X-Received: by 2002:a1c:9814:: with SMTP id a20mr881226wme.94.1578522296370; Wed, 08 Jan 2020 14:24:56 -0800 (PST)
MIME-Version: 1.0
References: <29380.1565102380@localhost> <BL0PR06MB50428065032ECC2AB3345F619AD70@BL0PR06MB5042.namprd06.prod.outlook.com> <7505.1565633977@localhost> <BL0PR06MB50424C618A704460E4A8F8D99AA90@BL0PR06MB5042.namprd06.prod.outlook.com> <18990.1577231446@localhost> <0bfb0f10f1a5001a588047a79d6db792@bbhmail.nl> <CAJFkdRwRMFx00KFXo-gJsqgAVmRfV=mKNwur1Th73uy_qj-WjA@mail.gmail.com> <0445EBA6-CB2E-4331-AE23-3E54D0923552@tzi.org>
In-Reply-To: <0445EBA6-CB2E-4331-AE23-3E54D0923552@tzi.org>
From: Ivaylo Petrov <ivaylo@ackl.io>
Date: Wed, 8 Jan 2020 23:24:30 +0100
Message-ID: <CAJFkdRz_kfQtD5L+4OHM=sKV4wsz8LLzG09MDUezobDD1aKVZg@mail.gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: peter van der Stok <consultancy@vanderstok.org>, core <core@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000bee551059ba85cd5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/cEMy4w2fm_2Xe8vxHJ4Iqhha0cg>
Subject: Re: [core] progressing ietf-core-yang-cbor and ietf-core-sid
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2020 22:25:01 -0000

Hello Carsten,

I was not aware that this is the blocking point and that is why I had put
much less priority to this modification. I should have read more carefully
the minutes, my bad. I have uploaded a new version now that addresses
this issue.

Best regards,
Ivaylo


On Wed, Jan 8, 2020 at 12:00 PM Carsten Bormann <cabo@tzi.org> wrote:

> Hi Ivaylo,
>
> The minutes indeed say:
>
> * draft-ietf-core-yang-cbor-11, draft-ietf-core-yang-library-00,
>   draft-ietf-core-comi-08, draft-ietf-core-sid-07: Now ready for WGLC,
>   to be sent to CoRE as well as netconf/netmod (with the discussion to
>   happen on CoRE).  (One comment on the numeric range of SIDs still to
>   be taken care of.)
>
> The parenthesis may have been a bit cryptic, but the intention was indeed
> to have I-D versions with all known issues (including the 63-bit one)
> addressed.  Is there a reason this will need more time?
>
> Grüße, Carsten
>
>
> > On 2020-01-08, at 11:23, Ivaylo Petrov <ivaylo@ackl.io> wrote:
> >
> > Hello,
> >
> > I am working on a new version of the SID draft that would address the
> comments related to 63bit SIDs and looking to clarify how are .sid files
> passed to IANA. Those are the only comments that I have received and I
> believe they are not blocking the WGLC. What I heard during the last IETF
> was that this draft is WGLC material, https://youtu.be/YIHoiHhz2Ys?t=1280
> and I was expecting the CoRE chairs to go ahead with this. If you believe
> there is some misunderstanding on my side and there are other issues that
> need to be resolved before the WGLC, please let me know.
> >
> > Best regards,
> > Ivaylo
> >
> > CONFIDENTIALITY NOTICE: This email may contain confidential and
> privileged material for the sole use of the intended recipient(s).
> > It is strictly forbidden to share any part of this message with any
> third party, without the written consent of the sender.
> > If you have received this message by mistake, please notify the sender
> immediately by email and delete the message and any file attached to it.
> Thank you!
> >
> >
> > On Mon, Dec 30, 2019 at 11:08 AM Peter van der Stok <stokcons@bbhmail.nl>
> wrote:
> >>
> >> I have not seen any progress on:
> >>   1) https://datatracker.ietf.org/doc/draft-ietf-core-yang-cbor/
> >>   2) https://datatracker.ietf.org/doc/draft-ietf-core-sid/
> >>
> >> At IETF105, it seemed that the documents were unstuck, and would
> progress
> >> to WGLC soon.  Is there something holding this up other than author
> time?
> >>
> >>
> >>
> >> I also want to express my concern about the VERY slow progress of these
> documents.
> >> It is quite possible and understandable that the authors are occupied
> with too many other tasks.
> >>
> >> An additional author may be the answer to unstick the progress.
> >>
> >> Greetings,
> >>
> >> Peter
> > _______________________________________________
> > core mailing list
> > core@ietf.org
> > https://www.ietf.org/mailman/listinfo/core
>
>