Re: [Netconf] Notifications: Proposed Edits to ResolveDiscuss Issues

["Sharon Chisholm" <[e-mail]>]

Hi

If there is no objection to option 2 then I will make the change and
publish the updated draft.

Sharon 

-----Original Message-----
From: [e-mail] [mailto:[e-mail]] On
Behalf Of Chisholm, Sharon (CAR:ZZ00)
Sent: Monday, May 05, 2008 8:06 AM
To: David B Harrington; [e-mail]; Eliot Lear
Cc: [e-mail]
Subject: Re: [Netconf] Notifications: Proposed Edits to ResolveDiscuss
Issues

Hi

Just to close this off. It seems we are converging on not adding the ISO
reference but just the RFC. (Note the RFC references the ISO
specification and attempts to remove some ambiguities). Just to clarify
what people want to do

1) Keep both references
2) Just have a reference to RFC3339
3) Just have a reference to RFC3339 section 4.4 and appendix A
4) Just have a reference to RFC3339 section 4.4
5) Just have a reference to RFC339 appendix A

Sharon

-----Original Message-----
From: [e-mail] [mailto:[e-mail]] On
Behalf Of David B Harrington
Sent: Monday, April 28, 2008 1:28 PM
To: [e-mail]; 'Eliot Lear'
Cc: [e-mail]
Subject: Re: [Netconf] Notifications: Proposed Edits to ResolveDiscuss
Issues

I believe we should follow RFC3339 section 4.4

David Harrington
[e-mail]
[e-mail]
[e-mail]
 

> -----Original Message-----
> From: [e-mail]
> [mailto:[e-mail]] On Behalf Of Juergen Schoenwaelder
> Sent: Friday, April 25, 2008 7:44 AM
> To: Eliot Lear
> Cc: [e-mail]
> Subject: Re: [Netconf] Notifications: Proposed Edits to ResolveDiscuss

> Issues
> 
> On Fri, Apr 25, 2008 at 01:29:57PM +0200, Eliot Lear wrote:
> > Hi Sharon,
> > 
> > This comment is largely bureaucratic:
> > 
> > > Proposed Edits
> > > --------------
> > >
> > > A. In section 2.1.1, for both instances and in section
> 2.2.1 Replace
> > >      This parameter is of type dateTime.
> > > With
> > >      This parameter is of type dateTime and compliant to
> [RFC3339] and
> > > [ISO.8601.1988].
> > >   
> > 
> > RFC 3339 specifically uses a subset of ISO.8601.1988.  As this 
> > discussion illustrates it is possible to construct times that are 
> > compliant with the latter and non-compliant with the
> former.  I believe
> > that ISO.8601.1988 is a superset of RFC 3339.  If you wish
> compliance
> > with "both", my recommendation would be to specify only
> ISO.8601.1988.  
> > This would meet Juergen's requirement of being able to specify an 
> > unqualified timezone.
> > 
> > ALTERNATIVELY, you could require times to be in
> ISO.8601.1988 format, as
> > specified in Appendix A of RFC 3339. 
> > 
> > Pointing at two standards covering the precise same
> specification is
> > just asking for a poke in the eye.
> 
> Good bureaucratic comment. Reading section 4.4 or RFC 3339, I should 
> probably shut up and be fine with requiring a timezone to be known
by
> a conforming device and then we can perhaps go with the RFC 3339 
> subset.
> 
> /js
> 
> -- 
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: [phone]         Campus Ring 1, 28759 Bremen, Germany
> Fax:   [phone]         <http://www.jacobs-university.de/>
> _______________________________________________
> Netconf mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/netconf
> 

_______________________________________________
Netconf mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/netconf
_______________________________________________
Netconf mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/netconf
_______________________________________________
Netconf mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/netconf