I'd actually tried the authors, but no reply yet (only a few days). I also
tried the RFC Editor thinking they might have e.g. XML from which extraction
might have been easier, but also no response yet. And I had found several
libraries, but not the RFC code. I can't see any suggestion that the
Hi,
On Jun 28, 2013, at 10:53, Dearlove, Christopher (UK)
chris.dearl...@baesystems.com
wrote:
But the broader point is that if it's worth the IETF publishing the code as
an RFC, it's worth making the code available straightforwardly.
some WGs are good at this. RFC5662 for example includes
I think we must agree to differ on whether the IETF should do this. If it takes
twenty minutes work for everyone who has to do it, either that stacks up, or no
one is actually interested, so is the RFC worth it?
As for maintaining the code, I'm just suggesting the same snapshot as the RFC
is
On Thu, 2013-06-27 at 12:44 +0100, Arturo Servin (probably did not
intend to) wrote:
What is the rationale of the requirement to attend psychically to
meetings?
I attend all meetings psychically so spriritual!
Sorry.. couldn't resist.
E.
As we have been working together as IETF community as well as univ.
community with us, I would share thiss loss of Evi with us and all the
students working with her at IETF.
Jun Murai
2013年6月28日金曜日 Brian E Carpenter brian.e.carpen...@gmail.com:
Evi used to be an IETF regular. There is rather
On 6/28/2013 4:53 AM, Dearlove, Christopher (UK) wrote:
I'd actually tried the authors, but no reply yet (only a few days).
For me, a thanks to Tony Hansen, who did the extraction for me. (That makes
me feel a little guilty, why should he do my work I could have done?) But the
point of
On Fri, Jun 28, 2013 at 4:11 PM, Tony Hansen t...@att.com wrote:
On 6/28/2013 4:53 AM, Dearlove, Christopher (UK) wrote:
I'd actually tried the authors, but no reply yet (only a few days).
For me, a thanks to Tony Hansen, who did the extraction for me. (That makes
me feel a little
Hi Faiz,
Thanks for bringing your idea to the IETF. The best way to propose your
idea is to write down the details in an Internet-draft. That helps make
sure that everyone understands how your system works. There are some tools
for writing drafts here:
http://tools.ietf.org/
Once you've
On Jun 28, 2013, at 1:57 AM, Eggert, Lars l...@netapp.com wrote:
some WGs are good at this. RFC5662 for example includes the shell commands to
extract the sources it contains.
Earlier example: RFC 4134.
It would certainly be nice if other WGs did this, too, but I'm not sure we
need to
I believe this is all part of improving the IETF Electronic Diversity
picture. Just like we have to deal with greater people personal
globalization diversity issues, there is also greater technology and
legal diversity issues to deal with. So many tools, so many languages,
so many OSes, so
Hi,
Please note that draft-eastlake-trill-rfc6327bis-00 was replaced by
draft-ietf-trill-rfc6327bis-00.
Thanks,
Donald
=
Donald E. Eastlake 3rd +1-508-333-2270 (cell)
155 Beaver Street, Milford, MA 01757 USA
d3e...@gmail.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
[I posted this question a little while ago to the WG chairs mailing list and
got no response.
Maybe my question is too trivial but I thought I should try it on the
ietf@ietf.org list as well to
get some feedback.]
Hi all,
when concerns about
On Jun 28, 2013, at 6:54 PM, Hannes Tschofenig hannes.tschofe...@gmx.net
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
[I posted this question a little while ago to the WG chairs mailing list and
got no response.
Maybe my question is too trivial but I thought I should try it on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
For SCTP we did a number of interoperability tests, which were
face to face meetings and the people who were developing stacks
we there. This events were always very helpful not only for improving
the stacks but also for improving the IETF
On Jun 28, 2013, at 7:14 PM, Hannes Tschofenig hannes.tschofe...@gmx.net
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
For SCTP we did a number of interoperability tests, which were
face to face meetings and the people who were developing stacks
we there. This events were always
--On Friday, June 28, 2013 10:11 -0400 Tony Hansen
t...@att.com wrote:
I also tried the RFC Editor thinking they might have e.g. XML
from which extraction might have been easier, but also no
response yet. And I had found several libraries, but not the
RFC code. ... But the broader point is
On Jun 28, 2013, at 12:10 PM, John C Klensin john-i...@jck.com wrote:
Folks, IANAL, but please be _very_ careful about the comment Joe
made about the potential difference between publishing a paper
or article that contains code and exporting the code itself or
making it generally available
On 2013-06-28, at 15:19, Paul Hoffman paul.hoff...@vpnc.org wrote:
The RFC Editor is publishing code in a text file that is formatted like an
RFC. The proposal is for the RFC Editor to publish *the exact same code* in a
file without the RFC wrapping.
If you really think you see a legal
Hi Hector,
On Fri, Jun 28, 2013 at 11:56 AM, Hector Santos hsan...@isdg.net wrote:
I believe this is all part of improving the IETF Electronic Diversity
picture. Just like we have to deal with greater people personal
globalization diversity issues, there is also greater technology and legal
Dearlove, Christopher (UK) wrote:
I'd actually tried the authors, but no reply yet (only a few days).
I also tried the RFC Editor thinking they might have e.g. XML
from which extraction might have been easier, but also no response yet.
Extracting code from text is pretty trivial.
Use
Martin Rex wrote:
Dearlove, Christopher (UK) wrote:
I'd actually tried the authors, but no reply yet (only a few days).
I also tried the RFC Editor thinking they might have e.g. XML
from which extraction might have been easier, but also no response yet.
Extracting code from text is
This message is reply to an author of a new draft under ietf discussion.
If this list is not the correct place to discuss such matter, then the
list's responsible Chair is required to give details of where to
discuss such new work.
+
Hi Moonesamy,
A new IETF working group has been proposed in the Security Area. The IESG
has not made any determination yet. The following draft charter was
submitted, and is provided for informational purposes only. Please send
your comments to the IESG mailing list (iesg at ietf.org) by 2013-07-08.
Security
The Managed Incident Lightweight Exchange (mile) working group in the
Security Area of the IETF is undergoing rechartering. The IESG has not
made any determination yet. The following draft charter was submitted,
and is provided for informational purposes only. Please send your
comments to the IESG
A new IETF working group has been formed in the Operations and Management
Area. For additional information please contact the Area Directors or the
WG Chair.
Large-Scale Measurement of Broadband Performance (lmap)
Current Status: Proposed WG
A new IETF working group has been proposed in the Security Area. The IESG
has not made any determination yet. The following draft charter was
submitted, and is provided for informational purposes only. Please send
your comments to the IESG mailing list (iesg at ietf.org) by 2013-07-08.
Security
A new IETF non-working group email list has been created.
List address: vm...@ietf.org
Archive: http://www.ietf.org/mail-archive/web/vmeet/current/maillist.html
To subscribe: https://www.ietf.org/mailman/listinfo/vmeet
Purpose: Explore, specify and develop improved services for remotely
A new Request for Comments is now available in online RFC libraries.
RFC 6956
Title: Forwarding and Control Element Separation
(ForCES) Logical Function Block (LFB) Library
Author: W. Wang, E. Haleplidis,
K.
A new Request for Comments is now available in online RFC libraries.
RFC 6971
Title: Depth-First Forwarding (DFF) in Unreliable
Networks
Author: U. Herberg, Ed.,
A. Cardenas,
T. Iwao,
29 matches
Mail list logo
