[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [VCARDDAV] vcardrev nits

To: Javier Godoy <rjgodoy at fich.unl.edu.ar>
Subject: Re: [VCARDDAV] vcardrev nits
From: Julian Reschke <julian.reschke at gmx.de>
Date: Wed, 16 Sep 2009 11:52:32 +0200
Cc: vcarddav at ietf.org
Delivered-to: vcarddav at core3.amsl.com
In-reply-to: <6CFB403EC15B4D41AF136E1F1BA29B8E at Javier2>
List-archive: <http://www.ietf.org/mail-archive/web/vcarddav>
List-help: <mailto:vcarddav-request@ietf.org?subject=help>
List-id: IETF vcarddav wg mailing list <vcarddav.ietf.org>
List-post: <mailto:vcarddav@ietf.org>
List-subscribe: <https://www.ietf.org/mailman/listinfo/vcarddav>, <mailto:vcarddav-request@ietf.org?subject=subscribe>
List-unsubscribe: <https://www.ietf.org/mailman/listinfo/vcarddav>, <mailto:vcarddav-request@ietf.org?subject=unsubscribe>
References: <4AB00791.4040005 at stpeter.im> <4A6CDE38802D481BAF82CDF30E08B75E at Javier2> <4AB095A2.2090407 at gmx.de> <6CFB403EC15B4D41AF136E1F1BA29B8E at Javier2>
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4 Mnenhy/0.7.4.666

Javier Godoy wrote:

...
I think the question was whether RFC 4770 should be explicitlyreferenced in section 7.4.3. IMPP of vcardrev (which is based on RFC 4770).
BTW, the references to RFC 2425, RFC 2426 and RFC 4770 (all of them willbe obsoleted by vcardrev) are normative in draft version 08.
...


Sorry. Should have done more checking.

However, shouldn't the references to to-be-obsoleted RFCs be *informative*?

BR, Julian

References:
- [VCARDDAV] vcardrev nits
  - From: Peter Saint-Andre
- Re: [VCARDDAV] vcardrev nits
  - From: Javier Godoy
- Re: [VCARDDAV] vcardrev nits
  - From: Julian Reschke
- Re: [VCARDDAV] vcardrev nits
  - From: Javier Godoy

Prev by Date: Re: [VCARDDAV] vcardrev nits
Next by Date: Re: [VCARDDAV] vcardrev nits
Previous by thread: Re: [VCARDDAV] vcardrev nits
Next by thread: Re: [VCARDDAV] vcardrev nits
Index(es):
- Date
- Thread