Re: [Dime] Diameter API draft.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Dime] Diameter API draft.
Hmmm.
Publishing something as historic is not particularly helpful and only
wasting the time of the RFC Editor.
________________________________
From: dime-bounces at ietf.org [mailto:dime-bounces at ietf.org] On Behalf
Of Glen Zorn
Sent: 12 October, 2009 16:37
To: 'Romascanu, Dan (Dan)'; vfajardo at research.telcordia.com;
dime at ietf.org
Subject: Re: [Dime] Diameter API draft.
What does the WG want to do with the I-D? Declare it 'Dead'? Publish
it as Historic RFC with a note reflecting that this was OBE (Overcome By
Events)?
Personally, I like the latter idea.
Dan
________________________________
From: dime-bounces at ietf.org
[mailto:dime-bounces at ietf.org] On Behalf Of Victor Fajardo
Sent: Tuesday, October 06, 2009 4:29 PM
To: vfajardo at research.telcordia.com; dime at ietf.org
Subject: Re: [Dime] Diameter API draft.
Hi,
It's been over a month and we have not had any feedback
regarding the Diameter API doc. At this point, I think it's safe to say that
no one is interested in continuing this work and so we will effectively
remove this doc from the charter.
Regards,
Victor
From: dime-bounces at ietf.org [mailto:dime-bounces at ietf.org]
On Behalf Of Victor Fajardo
Sent: Monday, August 24, 2009 8:25 AM
To: dime at ietf.org
Subject: [Dime] Diameter API draft.
Hi Folks,
During the last IETF, we were trying to gauge if there is
leftover interest in continuing work with the Diameter AP
(http://tools.ietf.org/html/draft-ietf-dime-diameter-api-08)I. This email is
a follow up to solicit a final vote/hum for this draft. If you see value in
this draft and wish to see the work continue, make sure you respond to this
email as well as address the questions "why and who" would use this API. If
you don't see any value in this work pls state so as well. We'll give this
hum some time to circulate through peoples mailboxes (a month or so) after
which we can decide the fate of the draft.
Regards,
victor
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.