[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: draft-srisuresh-ospf-te-05.txt
------------- Begin Forwarded Message -------------
Date: Thu, 22 May 2003 10:14:52 -0700 (PDT)
From: Joyce Reynolds <jkrey@ISI.EDU>
Subject: Re: draft-srisuresh-ospf-te-05.txt
To: srisuresh@yahoo.com
Cc: rfc-editor@rfc-editor.org, iesg@ietf.org
Suresh,
The IESG has established that there is a clear conflict with your
document and current IETF working group activities (see message
below). The RFC Editor will take this as a six month delay. You may
resubmit your document to the RFC Editor six months from today. Please
include a copy of this email when you resubmit.
Joyce
(on behalf of RFC Editor)
------------- Begin Forwarded Message -------------
Date: Mon, 19 May 2003 16:49:21 -0400
To: RFC Editor <rfc-editor@rfc-editor.org>
From: The IESG <iesg-secretary@ietf.org>
Subject: Re: draft-srisuresh-ospf-te-05.txt
Cc: IESG <iesg@ietf.org>, srisuresh@yahoo.com
RFC Editor,
The IESG has considered draft-srisuresh-ospf-te and has consulted with the
chairs of the OSPF and CCAMP WGs to determine what effect publishing of
this draft would have on ongoing IETF activities. The subject of the draft
is within the charter of the OSPF WG that is completing its work on OSPF
traffic engineering extensions (draft-katz-yeung-ospf-traffic).
draft-srisuresh-ospf-te was discussed in and rejected by the OSPF WG. Given
the above, and the work items expected to be taken on by the CCAMP WG
(including inter-area traffic engineering), the IESG believes that
publishing draft-srisuresh-ospf-te as an RFC at this moment would interfere
with ongoing activities within these WGs. The IESG recommends that the RFC
Editor does not publish draft-srisuresh-ospf-te at this moment.
Thank you,
The IESG Secretary
------------- End Forwarded Message -------------
------------- End Forwarded Message -------------