headers
Simon Josefsson | 2 May 2007 09:43
Favicon
Gravatar

Re: Last Call: draft-ietf-rmt-bb-fec-raptor-object (Raptor Forward Error Correction Scheme for Object Delivery) to Proposed Standard

Hi,

The document appear to contain several pages of "random numbers" and
"systematic indices", page 32-47
<http://www.ietf.org/internet-drafts/draft-ietf-rmt-bb-fec-raptor-object-08.txt>:

,----
| 5.6.  Random Numbers
| 
|    The two tables V0 and V1 described in Section 5.4.4.1 are given
|    below.  Each entry is a 32-bit integer in decimal representation.
| 
| 5.6.1.  The table V0
| 
|    251291136, 3952231631, 3370958628, 4070167936, 123631495, 3351110283,
|    3218676425, 2011642291, 774603218, 2402805061, 1004366930,
|    1843948209, 428891132, 3746331984, 1591258008, 3067016507,
|    1433388735, 504005498, 2032657933, 3419319784, 2805686246,
|    3102436986, 3808671154, 2501582075, 3978944421, 246043949,
|    4016898363, 649743608, 1974987508, 2651273766, 2357956801, 689605112,
|    715807172, 2722736134, 191939188, 3535520147, 3277019569, 1470435941,
|    3763101702, 3232409631, 122701163, 3920852693, 782246947, 372121310,
|    2995604341, 2045698575, 2332962102, 4005368743, 218596347,
| ...
`----

I'm not familiar with this technology enough to be able to tell if these
tables can be generated easily through some algorithm, and/or whether
that algorithm is even described in the document.  Help?
(Continue reading)

Permalink | Reply | 0 comments |
headers
Alexander Mayrhofer | 2 May 2007 12:36
Picon
Favicon

RE: Last Call: draft-ietf-enum-xmpp (IANA Registration for Enumservice 'XMPP') to Proposed Standard

> In the Introduction, this I-D says:
> 
>     RFC 4622 [6] registers an Internationalized Resource Identifier
>     (IRI) [5] and Uniform Resource Identifier (URI) scheme for
>     identifying XMPP entities.
> 
> There is no such thing as an IRI scheme, so the author may want to 
> correct the text; here is suggested wording:
> 
>     RFC 4622 [6] registers a Uniform Resource Identifier 
> (URI) scheme for
>     identifying an XMPP entity as a URI or as an Internationalized
>     Resource Identifier (IRI) [5].

Peter,

Thanks for performing that review - I have changed the text in the
Introduction as you suggested:

   RFC 4622 [5] registers a Uniform Resource Identifier (URI) scheme for
   identifying an XMPP entity as a URI or as an Internationalized
   Resource Identifier (IRI) [4].  The Enumservice specified in this
   document allows the provisioning of such "xmpp" URIs (and the URI
   representations of "xmpp" IRIs) in ENUM.

> There are some errors in RFC 4622, which I have attempted to 
> correct in 
> draft-saintandre-rfc4622bis:
> 
> http://www.ietf.org/internet-drafts/draft-saintandre-rfc4622bis-00.txt
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ray Pelletier | 2 May 2007 19:09
Favicon

IAOC Communications Plan: Review Requested

All;

The IAOC recognizes its responsibility to oversee IASA on behalf of the 
IETF community in a transparent manner and to that end publishes this 
Draft Communications Plan for community review before its adoption.

The Plan can be found at 
http://www1.tools.ietf.org/group/iaoc/wiki/CommsPlan
It is in pdf and doc/xls formats and consists of two documents, a draft 
plan and a matrix.

This draft Communications Plan identifies the information to be 
communicated to the community, the desired frequency and the mode of 
those communications.

RFC 4071 provides general and specific guidance to the IAOC and IAD 
regarding their responsibility to ensure transparency in the operation 
of the IASA. This Plan implements the requirements of RFC 4071 and 
provides additional reports to the community to enhance its visibility 
into the operation of the IASA.

Section C defines Confidential Information.

Section D identifies the communications channels the IAOC will employ to 
publish the report.

Section E defines the reports.

The Communications Plan Matrix provides the details of what, when and 
where of the reports to the community, as well as specifying the RFC
(Continue reading)

Permalink | Reply | 11 comments |
headers
Simon Josefsson | 2 May 2007 20:06
Favicon
Gravatar

Re: IAOC Communications Plan: Review Requested

The plan says that the primary form of communication with the community
will be in the form of a public Wiki.  A "Wiki" is unfortunately not a
precise term.  I'm not sure it automatically imply that there are any
indexes, a log of who made what changes when, or a search function, etc.

I would suggest that it should be required that all pages are reachable
from a single 'Table of Contents' page, that the log of changes in all
files are available publicly, and that a list of recent changes is
available.  A search function would also be usable.  Setting up a
mailing list that receives notification of every change to the wiki is
another idea.

If these mechanisms are not in place someone could create a wiki page
'OnSomeThingObscure' and if that page was never linked from any other
page, I doubt that anybody will find it.  It seems incorrect to me to
call writing such a page "communicating with the community".

Thanks,
Simon

Ray Pelletier <rpelletier <at> isoc.org> writes:

> All;
>
> The IAOC recognizes its responsibility to oversee IASA on behalf of
> the IETF community in a transparent manner and to that end publishes
> this Draft Communications Plan for community review before its
> adoption.
>
> The Plan can be found at
(Continue reading)

Permalink | Reply | 4 comments |
headers
Frank Ellermann | 2 May 2007 20:20
Picon
Picon

Re: IAOC Communications Plan: Review Requested

Ray Pelletier wrote:

> The Plan can be found at
> http://www1.tools.ietf.org/group/iaoc/wiki/CommsPlan

This results in an emtpy page with my browser.  Trying
to fix it locally I've removed all lines from 221 to
430 right before <div id="content" etc., and all lines
from 7 to 218 with inline styles.

Something with the structure is broken, there are open
<table>, <tr>, <td>, <div>, <ol>, and <li> elements at
the end, see http://validator.w3.org for the details.

I've attached the content, isolated the content works.
After that I saw that the raw (plain text) wiki input
is also available by adding ?format=txt to the URL.

> Section D identifies the communications channels the
> IAOC will employ to publish the report.

For D.1 (IAOC wiki) somebody has to look into the wiki
software, it shouldn't render content as XHTML-garbage.

Frank

Communications Plan

Draft Plan

(Continue reading)

Permalink | Reply | 4 comments |
headers
Henrik Levkowetz | 2 May 2007 20:44

Re: IAOC Communications Plan: Review Requested

Hi Frank,

on 2007-05-02 20:20 Frank Ellermann said the following:
> Ray Pelletier wrote:
> 
>> The Plan can be found at
>> http://www1.tools.ietf.org/group/iaoc/wiki/CommsPlan
> 
...
> Something with the structure is broken, there are open
> <table>, <tr>, <td>, <div>, <ol>, and <li> elements at
> the end, see http://validator.w3.org for the details.

                 ... somebody has to look into the wiki
> software, it shouldn't render content as XHTML-garbage.

You're right, it shouldn't.  I'll look into it.

	Henrik

_______________________________________________
Ietf mailing list
Ietf <at> ietf.org
https://www1.ietf.org/mailman/listinfo/ietf
Permalink | Reply | 3 comments |
headers
Frank Ellermann | 2 May 2007 21:16
Picon
Picon

Re: IAOC Communications Plan: Review Requested

Simon Josefsson wrote:

> I'm not sure it automatically imply that there are any indexes,
> a log of who made what changes when, or a search function, etc.

Some wikis offer a revision history and a search function, e.g.
most openspf.org pages are based on a Wiki, which is a fork of
"Usemod".  That offers a news feed (RSS) for "recent changes".

The IAOC wiki is broken at the moment (at least from my POV),
but the IESG wiki using the same software has similar features,
check out <http://tools.ietf.org/group/iesg/trac/timeline>

At the end of this page you find the feed URL.

> it should be required that all pages are reachable from a
> single 'Table of Contents' page, that the log of changes in
> all files are available publicly, and that a list of recent
> changes is available.

<http://tools.ietf.org/group/iesg/trac/wiki/TitleIndex>
<http://tools.ietf.org/group/iesg/trac/wiki/RecentChanges>

It's all there (for the IESG wiki)

> A search function would also be usable.

Fom the index I saw that a page FolkloreDrinks should exist,
and when I input that in the search form at the top I arrive
on a page with that title.
(Continue reading)

Permalink | Reply | 3 comments |
headers
Ray Pelletier | 2 May 2007 22:38
Favicon

Meeting Calendar Update 2011 - 2013

All;

The IAOC is considering adoption of an IETF Meetings Calendar for the 
period 2011 - 2013 prior to IETF 69 in Chicago. Adoption of such a 
calendar will permit advance planning for the community, venue 
selections, hosts and sponsors.

The IETF tries to avoid clashing with the schedule of other 
organizations on the Clash List. [ 
http://www1.tools.ietf.org/group/iaoc/wiki/ClashList ] Clashes should be 
brought to our attention.

Other events can be located at and added to the Internet Society 
Calendar at http://www.isoc.org/isoc/conferences/events/index.php .

2008 - 2010 dates are provided below for historical reference.

2011 - 2013 dates have considered the known IEEE 802 schedule, one of 
the few organizations with schedules set that far into the future.

Comments should be sent to calendar at ietf.org

Thanks
Ray Pelletier
IAD

 .

2008    
1    IETF 71    Mar 9 - 14
(Continue reading)

Permalink | Reply | 0 comments |
headers
Simon Josefsson | 3 May 2007 09:51
Favicon
Gravatar

Re: IAOC Communications Plan: Review Requested

Frank Ellermann <nobody <at> xyzzy.claranet.de> writes:

> Simon Josefsson wrote:
>
>> I'm not sure it automatically imply that there are any indexes,
>> a log of who made what changes when, or a search function, etc.
>
> Some wikis offer a revision history and a search function, e.g.
> most openspf.org pages are based on a Wiki, which is a fork of
> "Usemod".  That offers a news feed (RSS) for "recent changes".
>
> The IAOC wiki is broken at the moment (at least from my POV),
> but the IESG wiki using the same software has similar features,
> check out <http://tools.ietf.org/group/iesg/trac/timeline>

Will the IAOC use the same wiki software?  I seems sub-optimal to
require the IAOC to use a particular wiki implementation.  It seems
better to list the requirements one should have on such an
implementation instead.  That gives the IAOC/tools team more freedom to
chose and/or develop its own software.

>> Setting up a mailing list that receives notification of
>> every change to the wiki is another idea.
>
> IMO redundant if there's a news feed.  You could watch it
> with a "google alert", and let the "alert" post to blogger
> readable as pure HTML (i.e. without feed reader or ugly
> Javascript approximations of a feed reader).  It's more
> straight forward if you simply bookmark "recent changes".
(Continue reading)

Permalink | Reply | 2 comments |
headers
Henrik Levkowetz | 3 May 2007 09:25

Re: IAOC Communications Plan: Review Requested

Hi Simon,

on 2007-05-03 09:51 Simon Josefsson said the following:
> Frank Ellermann <nobody <at> xyzzy.claranet.de> writes:
> 
>> Simon Josefsson wrote:
>>
>>> I'm not sure it automatically imply that there are any indexes,
>>> a log of who made what changes when, or a search function, etc.
>>
>> Some wikis offer a revision history and a search function, e.g.
>> most openspf.org pages are based on a Wiki, which is a fork of
>> "Usemod".  That offers a news feed (RSS) for "recent changes".
>>
>> The IAOC wiki is broken at the moment (at least from my POV),
>> but the IESG wiki using the same software has similar features,
>> check out <http://tools.ietf.org/group/iesg/trac/timeline>
> 
> Will the IAOC use the same wiki software?

Since it's up and running, why don't you go and have a look?

The links are here (and in the left-hand menu-bar of any
tools.ietf.org WG or wiki page):

  http://www3.tools.ietf.org/group/iesg/trac/
  http://www3.tools.ietf.org/group/iaoc/

There's also, to complete the set, these:
(Continue reading)

Permalink | Reply | 1 comment |

Gmane