-
From: Martin Bjorklund [mailto:m...@tail-f.com]
Sent: Thursday, January 11, 2018 2:47 PM
To: Bogaert, Bart (Nokia - BE/Antwerp) <bart.boga...@nokia.com>
Cc: netmod@ietf.org
Subject: Re: [netmod] AD review of draft-ietf-netmod-entity-06
Hi,
To summarize this, I think we have three o
to:netmod-boun...@ietf.org] On Behalf Of Robert
Wilton
Sent: Thursday, December 21, 2017 4:14 PM
To: Martin Bjorklund <m...@tail-f.com>; netmod@ietf.org
Subject: Re: [netmod] AD review of draft-ietf-netmod-entity-06
Hi Martin,
On 21/12/2017 11:37, Martin Bjorklund wrote:
Hi,
I need WG
datastore only (accurately) reports on what
>>>>> is detected.
>>>> If there is a mismatch and the server doesn't apply the configured
>>>> values, then obviously the configured 'mfg-name' etc are not copied to
>>>> .
>>>>
>>
onfigured serial number.
>
> But if this is the case, I wonder if it wouldn't be better to leave
> such additional config objects to vendors, and simply make these three
> nodes config false in ietf-hardware.
>
>
> /martin
>
> >
> > Regards, Bart
> >
>
nodes config false in ietf-hardware.
/martin
Regards, Bart
/martin
Best regards, Bart
-Original Message-
From: netmod [mailto:netmod-boun...@ietf.org] On Behalf Of Robert
Wilton
Sent: Thursday, December 21, 2017 4:14 PM
To: Martin Bjorklund <m...@tail-f.com>; netmod@ietf
y the configured
>>> values, then obviously the configured 'mfg-name' etc are not copied to
>>> .
>>>
>>> We do not see this as a special rule for this data but rather would
>>>> apply a general rule:
>>>> - if there is a ‘missing re
nal Message-
From: netmod [mailto:netmod-boun...@ietf.org] On Behalf Of Robert
Wilton
Sent: Thursday, December 21, 2017 4:14 PM
To: Martin Bjorklund <m...@tail-f.com>; netmod@ietf.org
Subject: Re: [netmod] AD review of draft-ietf-netmod-entity-06
Hi Martin,
On 21/12/2017 11:37, Martin Bjorkl
e modelled as separate leafs.
> We should have a config false leaf 'serial-num' that only contains the
> detected value (if found), and a config true leaf 'config-serial-num'
> or something, that contains the configured serial number.
>
> But if this is the case, I wonder if i
From: netmod [mailto:netmod-boun...@ietf.org] On Behalf Of Robert
Wilton
Sent: Thursday, December 21, 2017 4:14 PM
To: Martin Bjorklund <m...@tail-f.com>; netmod@ietf.org
Subject: Re: [netmod] AD review of draft-ietf-netmod-entity-06
Hi Martin,
On 21/12/2017 11:37, Martin Bjorklund wrote:
and simply make these three
nodes config false in ietf-hardware.
/martin
>
> Regards, Bart
>
> /martin
>
>
> >
> > Best regards, Bart
> >
> > -Original Message-
> > From: netmod [mailto:netmod-boun...@ietf.org] On Behalf Of Robert
> >
m...@tail-f.com>; netmod@ietf.org
> Subject: Re: [netmod] AD review of draft-ietf-netmod-entity-06
>
> Hi Martin,
>
>
> On 21/12/2017 11:37, Martin Bjorklund wrote:
> > Hi,
> >
> > I need WG input on this issue. The question is how to handle
> > 'ser
ards, Bart
>
> -Original Message-
> From: netmod [mailto:netmod-boun...@ietf.org] On Behalf Of Robert
> Wilton
> Sent: Thursday, December 21, 2017 4:14 PM
> To: Martin Bjorklund <m...@tail-f.com>; netmod@ietf.org
> Subject: Re: [netmod] AD review of draft-ietf-netmod-
rds, Bart
-Original Message-
From: netmod [mailto:netmod-boun...@ietf.org] On Behalf Of Robert Wilton
Sent: Thursday, December 21, 2017 4:14 PM
To: Martin Bjorklund <m...@tail-f.com>; netmod@ietf.org
Subject: Re: [netmod] AD review of draft-ietf-netmod-entity-06
Hi Martin,
On 2
Hi Martin,
On 21/12/2017 11:37, Martin Bjorklund wrote:
Hi,
I need WG input on this issue. The question is how to handle
'serial-num', 'mfg-name', and 'model-name'. I think they should all
be treated the same. Based on previous WG discussion (see e.g. the
mail thread
On 12/21/2017 1:03 PM, Juergen Schoenwaelder wrote:
On Thu, Dec 21, 2017 at 12:58:26PM +0100, Martin Bjorklund wrote:
Juergen Schoenwaelder wrote:
On Thu, Dec 21, 2017 at 12:37:46PM +0100, Martin Bjorklund wrote:
Hi,
I need WG input on this issue. The
On Thu, Dec 21, 2017 at 12:58:26PM +0100, Martin Bjorklund wrote:
> Juergen Schoenwaelder wrote:
> > On Thu, Dec 21, 2017 at 12:37:46PM +0100, Martin Bjorklund wrote:
> > > Hi,
> > >
> > > I need WG input on this issue. The question is how to handle
> > >
Juergen Schoenwaelder wrote:
> On Thu, Dec 21, 2017 at 12:37:46PM +0100, Martin Bjorklund wrote:
> > Hi,
> >
> > I need WG input on this issue. The question is how to handle
> > 'serial-num', 'mfg-name', and 'model-name'. I think they should all
> > be
On Thu, Dec 21, 2017 at 12:37:46PM +0100, Martin Bjorklund wrote:
> Hi,
>
> I need WG input on this issue. The question is how to handle
> 'serial-num', 'mfg-name', and 'model-name'. I think they should all
> be treated the same. Based on previous WG discussion (see e.g. the
> mail thread
Hi,
I need WG input on this issue. The question is how to handle
'serial-num', 'mfg-name', and 'model-name'. I think they should all
be treated the same. Based on previous WG discussion (see e.g. the
mail thread "draft-ietf-netmod-entity issue #13"), I think they should
all be configurable,
Dear all,
One more comment, which I forgot in my AD review.
The -state YANG module in the appendix should actually be "deprecated".
Regards, Benoit
Dear all,
Here is my AD review of draft-ietf-netmod-entity-06.
Note that if you post the new version soon (before the end of this
week
On 12/20/2017 4:00 PM, Martin Bjorklund wrote:
Benoit Claise wrote:
Hi Martin,
Thanks.
Only kept the relevant excerpts.
- Some objects are read-write in RFC6933:
entPhysicalSerialNum
entPhysicalAlias
entPhysicalAssetID
entPhysicalUris
For
Benoit Claise wrote:
> Hi Martin,
>
> Thanks.
> Only kept the relevant excerpts.
> >
> >> - Some objects are read-write in RFC6933:
> >>entPhysicalSerialNum
> >>entPhysicalAlias
> >>entPhysicalAssetID
> >>entPhysicalUris
> >>
> >> For example,
Hi Martin,
Thanks.
Only kept the relevant excerpts.
- Some objects are read-write in RFC6933:
entPhysicalSerialNum
entPhysicalAlias
entPhysicalAssetID
entPhysicalUris
For example, entPhysicalSerialNum being read-write always bothered me.
serial-num is now "config
Hi,
Benoit Claise <bcla...@cisco.com> wrote:
> Dear all,
>
> Here is my AD review of draft-ietf-netmod-entity-06.
> Note that if you post the new version soon (before the end of this
> week), I could start the IETF last call, and the draft could be on Jan
> 11th IESG
Dear all,
Here is my AD review of draft-ietf-netmod-entity-06.
Note that if you post the new version soon (before the end of this
week), I could start the IETF last call, and the draft could be on Jan
11th IESG telechat.
- I don't believe that the RFC 2119 keywords are right on the following
25 matches
Mail list logo