On Thu, Feb 28, 2019 at 03:50:02AM +, Kent Watsen wrote:
> If you are interested in presenting to the WG, please send your presentation
> requests to the "netmod-chairs" alias (CC-ed) with the following information,
> for each presentation request, if more than one:
>
> - name of the draf
Dear WG,
The preliminary IETF 104 Agenda has been posted [1]. NETMOD is currently
scheduled to meet twice, 2 hours Tuesday morning and again for two hours on
Friday morning.
If you are interested in presenting to the WG, please send your presentation
requests to the "netmod-chairs" alias (CC-e
FYI.
> Begin forwarded message:
>
> From: internet-dra...@ietf.org
> Subject: I-D Action: draft-chopps-netmod-geo-location-00.txt
> Date: February 26, 2019 at 3:59:23 PM EST
> To:
> Reply-To: internet-dra...@ietf.org
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> d
Hello,
reading RFC7952 sections 5.2.2-5.2.4, it would seem that metadata object
(5.2.2) can occur at any position in a JSON object, as well as metadata
attachments to leaf/leaf-list/anyxml (5.2.3, 5.2.4) can occur any
distance (before or after) from the data element they attach to.
The examples l
Hi Randy,
> Are you saying that legacy boxes sitting in dark closets
> would somehow be updated to provide this indication?
Assuming YANG-next resolves the issue, and there is sufficient motivation then,
yes, sys-admins would need to blow the dust off their servers (and clients) and
update the
Hi -
On 2/27/2019 10:17 AM, Kent Watsen wrote:
...
If so, then there should be a way for the server to indicate which
discretionary choices it made. I'd suggest that "obsolete" defaults to
"not-implemented" and thus only servers that want to continue support
for the node need to indicate any
> On Feb 27, 2019, at 11:48 AM, Juergen Schoenwaelder
> wrote:
>
> On Wed, Feb 27, 2019 at 04:09:17PM +, Kent Watsen wrote:
>>
>>
>>> On Feb 27, 2019, at 6:16 AM, Balázs Lengyel
>>> wrote:
>>>
>>> feature oldFeature {
>>> status obsolete;
>>> }
>>> leaf myTimer {
>>> if-feature oldF
Sent from my iPhone
> On Feb 27, 2019, at 08:30, Kent Watsen wrote:
>
> I'm hoping to optimize for this common case scenario.
>
> I do not agree that having having two folding approaches is an issue. I
> would like to see this
> BCP have the broadest appeal possible.
It comes up due to t
On Wed, Feb 27, 2019 at 8:48 AM Juergen Schoenwaelder <
j.schoenwael...@jacobs-university.de> wrote:
> On Wed, Feb 27, 2019 at 04:09:17PM +, Kent Watsen wrote:
> >
> >
> > > On Feb 27, 2019, at 6:16 AM, Balázs Lengyel <
> balazs.leng...@ericsson.com> wrote:
> > >
> > > feature oldFeature {
> >
On Wed, Feb 27, 2019 at 04:09:17PM +, Kent Watsen wrote:
>
>
> > On Feb 27, 2019, at 6:16 AM, Balázs Lengyel
> > wrote:
> >
> > feature oldFeature {
> > status obsolete;
> > }
> > leaf myTimer {
> > if-feature oldFeature ;
> > mandatory true;
> > config true;
> > status current;
Note: I just released this this email.
Peter sent it on the 22nd, but it was trapped by Mailman:
Post by non-member to a members-only list
Kent // co-chair
> On Feb 21, 2019, at 1:06 PM, Peter Loborg wrote:
>
>
> Your example is fine – but the gammar is ch14 specifies somethin
Your example is fine – but the gammar is ch14 specifies something different:
enum-stmt = enum-keyword sep string optsep
(";" /
"{" stmtsep
;; these stmts can appear in any order
All,
There seems to be some confusion. My original message said:
Whereby this second form only supports the folded line continuing on
column 1 (no indents).
To be clear, if indents are desired, I strongly support using the
double-backslash approach and
do not recommend any other appr
> On Feb 27, 2019, at 6:16 AM, Balázs Lengyel
> wrote:
>
> feature oldFeature {
> status obsolete;
> }
> leaf myTimer {
> if-feature oldFeature ;
> mandatory true;
> config true;
> status current;
> type string;
> }
> So should I configure myTimer or not? I assume yes, correct?
Th
On Wed, Feb 27, 2019 at 11:16:55AM +, Balázs Lengyel wrote:
> feature oldFeature {
>status obsolete;
> }
>
> leaf myTimer {
>if-feature oldFeature ;
>mandatory true;
>config true;
>status current;
>type string;
> }
>
>So should I configure myTimer or not? I ass
feature oldFeature {
status obsolete;
}
leaf myTimer {
if-feature oldFeature ;
mandatory true;
config true;
status current;
type string;
}
So should I configure myTimer or not? I assume yes, correct?
regards Balazs
On 2019. 02. 27. 11:33,
On Wed, Feb 27, 2019 at 10:19:55AM +, Balázs Lengyel wrote:
>Hello,
>
>The feature statement may have a status substatement. But what does it
>mean if a feature is deprecated or obsolete? Some ideas:
>
> * All if-feature statements using it should be removed. But what to do
>
Hi,
I have posted a baseline I-D for an update of the common YANG
datatypes (RFC 6991). There are no content changes yet, this version
reflects the content of RFC 6991. The idea is that this -00 version
serves as a convenient baseline for the diff tools we have.
/js
On Wed, Feb 27, 2019 at 02:17
Hello,
The feature statement may have a status substatement. But what
does it mean if a feature is deprecated or obsolete? Some ideas:
All if-feature statements using it should be removed. But what
to do with "if-feature oldFeature AND otherFeature" ;
Hi Adrian,
I mostly agree with your last sentence.
I think that if you always preserve whitespace then a single slash is fine.
I.e. the single slash just breaks the line, and I think that this matches how
editors, programming languages, etc normally behave.
What I’m not keen on is using a sin
Complete agreement, Joel.
What follows may look better in proportional fonts.
With a single slash we can wrap as follows
12345679012345
Goes to…
1234567\
9012345
…and unwrapping is easy.
However, if I want to manually wrap the line with indentation
T
21 matches
Mail list logo
