IETF Logo Mail Archive

Re: [YANG] keyref

"Randy Presuhn" <randy_presuhn@mindspring.com> Wed, 23 January 2008 05:13 UTC

Return-path: <yang-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHXvq-0001BG-O6; Wed, 23 Jan 2008 00:13:50 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JHXvq-0001BA-4a for yang-confirm+ok@megatron.ietf.org; Wed, 23 Jan 2008 00:13:50 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHXvp-0001Az-QP for yang@ietf.org; Wed, 23 Jan 2008 00:13:49 -0500
Received: from elasmtp-masked.atl.sa.earthlink.net ([209.86.89.68]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JHXvp-0007Jw-Ha for yang@ietf.org; Wed, 23 Jan 2008 00:13:49 -0500
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=WFDMVQ8+7MOZ9JVfecn5qsRC9VtxtOOwHo9GccHAz+U3R4lr/p4We5ViYXn66rTn; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [69.3.145.174] (helo=oemcomputer) by elasmtp-masked.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1JHXvf-0002iF-KA for yang@ietf.org; Wed, 23 Jan 2008 00:13:40 -0500
Message-ID: <000b01c85d7e$f2291420$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <yang@ietf.org>
References: <200801230358.m0N3wsub017849@idle.juniper.net> <4796C299.7010706@andybierman.com>
Subject: Re: [YANG] keyref
Date: Tue, 22 Jan 2008 21:15:13 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8885d2a9c731cc89117e7fe3d0679a24513576202cba5d0d210350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 69.3.145.174
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
X-BeenThere: yang@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: YANG modeling Language for NETCONF <yang.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/yang>, <mailto:yang-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/yang>
List-Post: <mailto:yang@ietf.org>
List-Help: <mailto:yang-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/yang>, <mailto:yang-request@ietf.org?subject=subscribe>
Errors-To: yang-bounces@ietf.org

Hi -

> From: "Andy Bierman" <ietf@andybierman.com>
> To: "Phil Shafer" <phil@juniper.net>
> Cc: <yang@ietf.org>
> Sent: Tuesday, January 22, 2008 8:29 PM
> Subject: Re: [YANG] keyref
...
> I expect the requirements team to write the initial draft.
> I don't know what the RFC will look like yet.
...

Don't hold your breath.  We're only putting together an I-D
with our view of potential requirements in order to facilitate
progress at a BOF.  I have no expectation that the work will
be all-encompassing, and encourage others to document
any requirements they see as important.  In any case, I
see no point in turning it into an RFC effort.  Doing so would
only delay progress on the real work even more.

Randy



_______________________________________________
YANG mailing list
YANG@ietf.org
https://www1.ietf.org/mailman/listinfo/yang

v2.8.7 | Report a Bug | By Email