Re: [netmod] ietf-yang-types:date-and-time canonical value

Hi, Hiya, On 24.04.23 14:20, Michal Vasko wrote: Hi, I would like to have a specific date-and-time canonical value clarified because I am not sure what exactly is expected. If a system is using NZST (+12:00, New Zealand Standard Time) and is printing the timestamp

Re: [netmod] Comments on draft-ma-netmod-immutable-flag-06

Hi, Kent Thank you for your valuable comments, please see inline. I've just re-read the draft and this thread and have comments. I support ensuring XC/Y remains transactional, such that a client can always move from valid config-A to valid config-B in a single update. I also support

[netmod] ietf-yang-types:date-and-time canonical value

Hi, I would like to have a specific date-and-time canonical value clarified because I am not sure what exactly is expected. If a system is using NZST (+12:00, New Zealand Standard Time) and is printing the timestamp 2023-02-23T10:00:00+12:00, should the output be 1.

Re: [netmod] ietf-yang-types:date-and-time canonical value

Hi Eliot, thanks for the answer. From what you wrote I assume that your explanation is based on RFC 3339 but I could not find this behavior specified there, only a note (second bullet) that the exact situation we are discussing is not

Re: [netmod] Comments on draft-ma-netmod-immutable-flag-06

Hi Qiufang, > I support ensuring XC/Y remains transactional, such that a client can always > move from valid config-A to valid config-B in a single update. I also > support requiring a "with-immutable" flag in client-requests in order for the > "immutable" annotations to be returned (like

Re: [netmod] ietf-yang-types:date-and-time canonical value

Mi Michael, On 24.04.23 15:40, Michal Vasko wrote: Hi Eliot, thanks for the answer. From what you wrote I assume that your explanation is based on RFC 3339 but I could not find this behavior specified there, only a note (second bullet)

Re: [netmod] ietf-yang-types:date-and-time canonical value

On Mon, Apr 24, 2023 at 7:48 AM Carsten Bormann wrote: > On 2023-04-24, at 14:20, Michal Vasko wrote: > > > > canonical > > Hi Michal, > > I don’t know what exactly “canonical” means here. > >From the date-and-time typedef: The canonical format for date-and-time values with a known time

Re: [netmod] J. Sterne comments on draft-ietf-netmod-system-config-00

Thanks Qiufang. Please see inline. I got down to J6 and will continue with feedback in a subsequent reply. Jason From: maqiufang (A) Sent: Monday, April 17, 2023 11:53 PM To: Jason Sterne (Nokia) Cc: netmod@ietf.org Subject: RE: [netmod] J. Sterne comments on draft-ietf-netmod-system-config-00

[netmod] IPR Poll on draft-ietf-netmod-yang-semver-09

Dear Kent, all, No, I'm not aware of any IPR that applies to this draft. Sorry for missing the email. Regards, Bo Wu On Jan 16, 2023, at 5:59 PM, Kent Watsen mailto:kent+i...@watsen.net>> wrote: [NOTE: A response is needed from all listed in this message's "To" line, the authors and

Re: [netmod] IPR Poll on draft-ietf-netmod-yang-semver-09

Hello chairs and WG, (as an author) We've updated both drafts to refactor Acknowledgements vs Contributors: https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-module-versioning/09/ https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-semver/11/ The IPR call for Module Versioning is

Re: [netmod] IPR Poll on draft-ietf-netmod-yang-semver-09

Bo and Jan (CC-ed), Please reply-all to this email with your response to the original IPR call here: https://mailarchive.ietf.org/arch/msg/netmod/xHDWFr5e2ykRBEseq-99PhRENGM/ Jason, thank you for highlighting this issue to the chairs. Kent // as chair > On Apr 24, 2023, at 5:48 PM, Jason

Re: [netmod] ietf-yang-types:date-and-time canonical value

On 2023-04-24, at 14:20, Michal Vasko wrote: > > canonical Hi Michal, I don’t know what exactly “canonical” means here. As a general rule, timestamps used by machines should not use timezones, so you should use 2023-02-22T22:00:00Z If there is a use for indicating the timezone offset a