Seed source clarification

[NomCom Chair]

It was noted that the URL I posted for the megamillions lottery no longer
works.  The lottery is still there, and is still running, and I will still
be using the numbers that are drawn on August 29.
The URL I will use for these numbers is:
http://www.megamillions.com/numbers/pastdrawings.asp
as that will work if someone needs to recreate the results after they have
run another drawing.  

Thank you, 
and many thanks to Ted Hardie, who noticed and reported the URL problem,
Joel M. Halpern
[EMAIL PROTECTED]
[EMAIL PROTECTED]
___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

Protocol Action: 'Internet Message Format' to Draft Standard

[The IESG]

The IESG has approved the following document:

- 'Internet Message Format '
   draft-resnick-2822upd-06.txt as a Draft Standard

This document has been reviewed in the IETF but is not the product of an
IETF Working Group. 

The IESG contact person is Lisa Dusseault.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-resnick-2822upd-06.txt

Technical Summary

This document specifies the Internet Message Format (IMF), a syntax for
text messages that are sent between computer users, within the framework
of electronic mail messages.  This specification is a revision of
Request For Comments (RFC) 2822, which itself superseded Request For
Comments (RFC) 822, Standard for the Format of ARPA Internet Text
Messages, updating it to reflect current practice and incorporating
incremental changes that were specified in other RFCs.


Working Group Summary

No working group is currently extant on core email formats. Subsequently,
this document was reviewed on the ietf-822 mailing list, which had been
set up by DRUMS. Pointers to the discussions there were periodically sent
to other mailing lists populated with email people, such as ietf-smtp, the
EAI working group, the LEMONADE working group, and the IMAP-EXT working
group.


Document Quality

The current document represents implementation experience from the past 7
years in email since RFC 2822 was published. As an update intended to move
the internet message format to Draft Standard status, the key issues was
to remove features not implemented by vendors and to tighten down the
specification to represent what has been implemented.

Personnel

Tony Hansen is the Doc Shepherd.  Lisa Dusseault reviewed this for the
IESG.  A number of reviewers from the email community were involved,
including such notables as Ned Freed, John Klensin, and Dave Crocker.

___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

IETF72, IPv6 Panel Report

[Olaf Kolkman]

Dear Colleagues,

The IAB would like to thank all of you who attended or otherwise
participated at the IETF 72 Technical Plenary's panel on IPv6 adoption in
Dublin. We heard about IPv4 exhaustion contingency planning and about
real-world IPv6 adoption successes and barriers from:

- Mark Kosters (ARIN's perspective and policies about IPv4 address
  exhaustion)
- Alain Durand (Comcast's IPv6-enabled network infrastructure)
- Lorenzo Colitti (Google's IPv6-enabled content services)
- Shin Miyakawa (NTTcom's IPv6-enabled consumer services)
- Stuart Cheshire (Adoption of IPv6 in applications like Apple's Safari
  web browser)

Audio stream archive:
  http://limestone.uoregon.edu/ftp/pub/videolab/media/ietf72/
  Select ietf72-ch3-wed-plenary.mp3.
  The IPv6 panel starts at time 01:13:00 on the stream.

Presentation archive:
  https://datatracker.ietf.org/meeting/72/materials.html
  See heading Plenary Sessions, session PlenaryW.

The consistent message from the presentations was that most of the code
implementation work for IPv6 is done -- the protocols have been designed,
and implemented in all major operating systems and networking devices.
Most widely-used software (like networking gear, OS software, and web
browser clients) has already been updated to support IPv6, and most
application software written to use higher-level connect-by-name APIs.
Popular development languages like Java get IPv6 support for free without
any code changes at all. However, the participants were clear that
although the actual operational deployment of IPv6 is much easier
technically than they expected, it takes longer than expected; they urged
the rest of the community to begin their deployment work as soon as
possible.

One common theme was that, as with many technological advances, success
stories in IPv6 adoption are frequently the result of one or two motivated
individuals who take the initiative to make things happen in their
organization. If you yourself have worked on throwing the IPv6 switch
within your organization, or you know of someone with an interesting IPv6
adoption story, the IAB invites you to let us know about it, including
issues overcome, or hurdles still before you. Send your story to:

   [EMAIL PROTECTED]

The IAB will deliver a summary report on these stories at a future IETF
meeting.

On the universal deployment of IPv6[*],

-- For the IAB
   Olaf Kolkman



PS: Want to make a difference? A brainstorm of ideas follow:

  * Share the slides and a report of the plenary session with the
networking lead in your organization's IT department.
  * Personally request IPv6 service from your ISP and enable IPv6
for your home network.
  * Prepare your laptop for IPv6 and primarily use the IPv6 network
at IETF 73.
  * If you work on application code, make sure your application works
with IPv6, and if not, fix it. (Even if you don't test wide-area
IPv6, at the very least make sure your application works with
IPv6 link-local addresses, which are configured automatically
these days on Mac OS X and Windows.)
  * Start using IPv6 operationally within your organization.


[*] There is an old tradition to toast on the Universal Deployment of
IPv6 during the the IETF Scotch BOFs. With that in mind we plan to
provide the best story with a bottle of single malt.
___
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce