<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Eric,<br>
<br>
personally speaking, that's what also got me to feel uneasy about
this proposal.<br>
Kindest regards,<br>
<br>
Olivier<br>
<br>
<div class="moz-cite-prefix">On 17/07/2014 16:59, Eric Burger wrote:<br>
</div>
<blockquote
cite="mid:48CCE9E0-A539-4780-BE77-67EF6DE5F07A@standardstrack.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
That there are three communities of interest: names (brands),
numbers (RIRs), and protocols (IETF).
<div><br>
<div>
<div>On Jul 17, 2014, at 10:46 AM, Seun Ojedeji <<a
moz-do-not-send="true"
href="mailto:seun.ojedeji@gmail.com">seun.ojedeji@gmail.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div style="font-family: Helvetica; font-size: 12px;
font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal;
orphans: auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: auto;
word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<div dir="ltr">Hello Eric,<br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Jul 17, 2014 at 2:59
PM, Eric Burger<span class="Apple-converted-space"> </span><span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:eburger@cs.georgetown.edu"
target="_blank">eburger@cs.georgetown.edu</a>></span><span
class="Apple-converted-space"> </span>wrote:<br>
<blockquote class="gmail_quote" style="margin: 0px
0px 0px 0.8ex; border-left-width: 1px;
border-left-color: rgb(204, 204, 204);
border-left-style: solid; padding-left: 1ex;">
<div style="word-wrap: break-word;">As far as
Milton is concerned, users do not count. :-(</div>
</blockquote>
<div><br>
</div>
<div>Following remotely as well, may i know what
part of Milton's comment implied your conclusion
above.<br>
<br>
</div>
<div>Cheers!<span class="Apple-converted-space"> </span><br>
</div>
<blockquote class="gmail_quote" style="margin: 0px
0px 0px 0.8ex; border-left-width: 1px;
border-left-color: rgb(204, 204, 204);
border-left-style: solid; padding-left: 1ex;
position: static; z-index: auto;">
<div style="word-wrap: break-word;"><br>
<div>
<div>
<div class="h5">
<div>On Jul 17, 2014, at 6:31 AM, Narelle
Clark <<a moz-do-not-send="true"
href="mailto:narelle@isoc-au.org.au"
target="_blank">narelle@isoc-au.org.au</a>>
wrote:</div>
<br>
</div>
</div>
<blockquote type="cite">
<div>
<div class="h5">
<div dir="ltr">
<div><br>
</div>
Milton Mueller Charter Proposal<br>
<br>
<p>Draft charter for the IANA
Stewardship Transition Coordination
Group</p>
<div> <br>
</div>
<p>V 2.1 (July 16, 2014)</p>
<div> <br>
</div>
<p>The IANA transition coordination
group (ICG) has one deliverable, a
proposal to the U.S. Commerce
Department National
Telecommunications and Information
Administration (NTIA) regarding the
transition of NTIA’s stewardship of
the IANA functions to the Internet
community.</p>
<div> <br>
</div>
<p>The group’s mission is to
coordinate the development of a
proposal among the communities
affected by the IANA functions. The
IANA parameters fall into three
categories: domain names, number
resources, and other protocol
parameters. While there is some
overlap among these categories, each
poses distinct organizational,
operational and technical issues,
and each tends to have distinct
communities of interest and
expertise. For those reasons it is
best to have work on the three
categories of IANA parameters
proceed autonomously in parallel and
be based in the respective
communities of interest.</p>
<div> <br>
</div>
<p>The coordination group has four
main tasks:</p>
<div> <br>
</div>
<p style="margin-left: 0.75in;"><span>(i)<span
style="font-style: normal;
font-variant: normal;
font-weight: normal; font-size:
7pt; line-height: normal;
font-family: 'Times New Roman';"> <span
class="Apple-converted-space"> </span></span></span>Act
as liaison to the three communities
of interest (names, numbers,
protocols)</p>
<p style="margin-left: 0.75in;"><span>(ii)<span
style="font-style: normal;
font-variant: normal;
font-weight: normal; font-size:
7pt; line-height: normal;
font-family: 'Times New Roman';"> <span
class="Apple-converted-space"> </span></span></span>Assess
the outputs of the three communities
of interest for workability,
compatibility and consensus</p>
<p style="margin-left: 0.75in;"><span>(iii)<span
style="font-style: normal;
font-variant: normal;
font-weight: normal; font-size:
7pt; line-height: normal;
font-family: 'Times New Roman';"> <span
class="Apple-converted-space"> </span></span></span>Assemble
a complete proposal for the
transition</p>
<p style="margin-left: 0.75in;"><span>(iv)<span
style="font-style: normal;
font-variant: normal;
font-weight: normal; font-size:
7pt; line-height: normal;
font-family: 'Times New Roman';"> <span
class="Apple-converted-space"> </span></span></span>Information
sharing and public communication</p>
<div> <br>
</div>
<p>Describing each in more detail:</p>
<div> <br>
</div>
<p style="margin-left: 0.75in;"><span>(i)<span
style="font-style: normal;
font-variant: normal;
font-weight: normal; font-size:
7pt; line-height: normal;
font-family: 'Times New Roman';"> <span
class="Apple-converted-space"> </span></span></span>Liaison</p>
<p>Members of the ICG will ensure that
the communities from which they are
drawn are working on their part of
the transition plans. This involves
informing them of requirements and
schedules, tracking progress, and
highlighting the results or
remaining issues. The role of a
coordination group member during
this phase is to provide status
updates about the progress of his or
her community in developing their
component, and to coordinate which
community will develop a transition
proposal for each area of overlap
(e.g., special-use registry)</p>
<div> <br>
</div>
<p style="margin-left: 0.75in;"><span>(ii)<span
style="font-style: normal;
font-variant: normal;
font-weight: normal; font-size:
7pt; line-height: normal;
font-family: 'Times New Roman';"> <span
class="Apple-converted-space"> </span></span></span>Assessment</p>
<p>When the group receives output from
the independent groups it will
discuss and assess their
workability, assess their
compatibility and interoperability
with the proposals of the other
groups, and verify their levels of
support in the respective
communities. The ICG might at some
point detect problems with the
component proposals. At that point
the role of the ICG is to
communicate that back to the
relevant communities so that they
(the relevant communities) can
address the issues. In assessing
consensus, the coordination group
will rely to some extent on its
members to reflect to the rest of
the group the support levels within
the member's own community, but the
group is also authorized to engage
in independent assessments, such as
public notice and comment periods.</p>
<div> <br>
</div>
<p style="margin-left: 0.75in;"><span>(iii)<span
style="font-style: normal;
font-variant: normal;
font-weight: normal; font-size:
7pt; line-height: normal;
font-family: 'Times New Roman';"> <span
class="Apple-converted-space"> </span></span></span>Assembling
and submitting a complete proposal</p>
<p>The assembly effort involves taking
the proposals for the different
components and verifying that they
fulfil the intended scope, meet the
intended criteria, that there are no
missing parts, and that the whole
fits together. The ICG will then
develop a draft final proposal that
achieves consensus within the ICG
itself. The ICG will then put this
proposal up for public comment
involving a reasonable period of
time for reviewing the draft
proposal, analyzing and preparing
supportive or critical comments. The
ICG will then review these comments
and determine whether modifications
are required. If not, and the
coordination group agrees, the
proposal will be submitted to NTIA.
If changes are required to fix
problems or achieve broader support,
the ICG is authorized to make minor
amendments in consultation with the
affected communities of interest.
If, in the ICG’s opinion, broad
public support for the proposal as
articulated by the NTIA is not
present, the parts of the proposal
that are not supported return to the
liaison phase.</p>
<div> <br>
</div>
<p style="margin-left: 0.75in;"><span>(iv)<span
style="font-style: normal;
font-variant: normal;
font-weight: normal; font-size:
7pt; line-height: normal;
font-family: 'Times New Roman';"> <span
class="Apple-converted-space"> </span></span></span>Information
sharing</p>
<p>The ICG should serve as a central
clearinghouse for public information
about the IANA stewardship
transition process. Its secretariat
should maintain an independent
website, under its own domain, where
status updates, meetings and notices
are announced, proposals are stored,
the ICG members are listed, etc.</p>
<div> <br>
</div>
<br>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Thu, Jul
17, 2014 at 8:27 PM, Narelle Clark<span
class="Apple-converted-space"> </span><span
dir="ltr"><<a
moz-do-not-send="true"
href="mailto:narelle@isoc-au.org.au"
target="_blank">narelle@isoc-au.org.au</a>></span><span
class="Apple-converted-space"> </span>wrote:<br>
<blockquote class="gmail_quote"
style="margin: 0px 0px 0px 0.8ex;
border-left-width: 1px;
border-left-color: rgb(204, 204,
204); border-left-style: solid;
padding-left: 1ex;">
<div dir="ltr">
<div><br>
</div>
Charter discussion happening
now. Two proposals so far. IETF
and Milton Mueller<br>
<br>
IETF Proposal:<br>
<p>The coordination group has
one deliverable, a proposal to
the NTIA regarding the
transition of NTIA’s
stewardship of IANA functions
to<span> <span
class="Apple-converted-space"> </span></span>the
multi-stakeholder community.</p>
<p>The coordination group
performs, as its name implies,
coordination, among the
communities that are affected
by IANA functions. The IANA
parameters fall into three
categories: domain names,
number resources, and other
protocol parameters. While
there is some overlap among
these categories, they have
their own communities of
interest; it is easiest to
have these communities proceed
on the work in parallel.</p>
<p>The coordination group has
three main tasks:</p>
<p>(i) Ensuring that the
relevant communities are
working on their part of the
transition<span> <span
class="Apple-converted-space"> </span></span>plans</p>
<p><span> </span>This involves
informing, tracking progress,
and highlighting the results
or remaining<span> <span
class="Apple-converted-space"> </span></span>issues.</p>
<p><span> </span>The role of a
coordination group member
during this phase is just</p>
<p><span> <span
class="Apple-converted-space"> </span></span>-
providing status updates about
the progress of his or her
community in<span> </span>developing
their component,</p>
<p><span> <span
class="Apple-converted-space"> </span></span>-
coordinating which community
will develop a transition
proposal for each area<span> </span>of
overlap (e.g., special-use
registry)</p>
<p><span> <span
class="Apple-converted-space"> </span></span>-
reflecting to the rest of the
coordination group the
consensus within the<span> </span>member's
own community.</p>
<p>(ii) Assemble a complete
proposal for the transition.</p>
<p><span> </span>This can begin
when the reports from the
coordination group members
from each<span> <span
class="Apple-converted-space"> </span></span>of
the three communities come
back with an answer of, "Yes,
there is consensus<span> </span>within
my community in support of the
complete proposal."</p>
<p><span> </span>The assembly
effort involves taking the
proposals for the different
components<span> <span
class="Apple-converted-space"> </span></span>and
verifying that they fulfil the
intended full scope, meet the
intended criteria,<span> <span
class="Apple-converted-space"> </span></span>that there are no missing
parts, and that the whole fits
together.</p>
<p><span> </span>The CG might at
some point detect problems
with the component proposals.</p>
<p><span> </span>At that point
the role of the CG is to
communicate that back to the
relevant<span> <span
class="Apple-converted-space"> </span></span>communities
so that they (the relevant
communities) can address the
issues.</p>
<p><span> </span>This step
concludes when the
coordination group achieves
rough consensus that<span> <span
class="Apple-converted-space"> </span></span>all conditions have been
met.</p>
<p>(iii) Information sharing and
communication.</p>
<p><span> </span>This should be
performed continuously
throughout the process.<br>
</p>
</div>
<div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On
Thu, Jul 17, 2014 at 6:29
PM, Narelle Clark<span
class="Apple-converted-space"> </span><span
dir="ltr"><<a
moz-do-not-send="true"
href="mailto:narelle@isoc-au.org.au"
target="_blank">narelle@isoc-au.org.au</a>></span><span
class="Apple-converted-space"> </span>wrote:<br>
<blockquote
class="gmail_quote"
style="margin: 0px 0px 0px
0.8ex; border-left-width:
1px; border-left-color:
rgb(204, 204, 204);
border-left-style: solid;
padding-left: 1ex;">
<div dir="ltr"><br>
All<br>
The first face-to-face
meeting of the IANA
coordination group is
taking<br>
place<span
class="Apple-converted-space"> </span><span>July
17-18</span><span
class="Apple-converted-space"> </span>in
London, UK. Information
about the remote
participation<br>
is available here:<span
class="Apple-converted-space"> </span><a moz-do-not-send="true"
href="https://www.icann.org/news/announcement-2014-07-16-en"
target="_blank">https://www.icann.org/news/announcement-2014-07-16-en</a><br>
<br>
The draft agenda is
below. All times are
local (UTC+1). The names
of the<br>
coordination group
members are listed here:<br>
<a
moz-do-not-send="true"
href="https://www.icann.org/resources/pages/coordination-group-2014-06-17-en"
target="_blank">https://www.icann.org/resources/pages/coordination-group-2014-06-17-en</a><br>
<br>
<br>
== Day 1 ==<br>
<br>
<span>9:00 - 9:15</span><br>
Introduction and
level-setting. (Alissa)<br>
Live streaming,
administrivia, and
logistics.<br>
Brief explanation of why
we are gathered to meet.<br>
Agenda bash.<br>
<br>
<span>9:15 - 10:45</span><br>
Introductions. (Alissa)<br>
It would be useful to
hear from each rep
about:<br>
- What group appointed
them<br>
- What that group does
and who participates in
it<br>
- How that group does
its work and what its
decision processes are<br>
- Whether they are
"representing" their
groups or participating
as<br>
individuals in the CG<br>
- How they view their
group's work in relation
to the coordination
group's<br>
work<br>
<br>
<span>10:45 - 11:00</span><br>
Break.<br>
<br>
<span>11:00 - 12:30</span><br>
Charter of the CG.
(Jari)<br>
It would be good to
obtain a shared
understanding in the
whole group of<br>
the role and<br>
charter of the CG.
Charter proposals
circulated in advance of
July 17<br>
would help here --<br>
on the IETF/IAB side we
may be able to work one
up based on the IAB's<br>
<span>April 29</span><span
class="Apple-converted-space"> </span>comments.<br>
<br>
<span>12:30 - 13:30</span><br>
Lunch.<br>
Continued discussion of
charter.<br>
<br>
<span>13:30 - 15:00</span><br>
Transition scope and
expectations about work
in the communities.
(Paul)<br>
It would be good to
clarify the CG's
understanding of the
scope of the<br>
work of the<br>
transition, what the
community processes need
to produce, and
where/how<br>
areas of overlap<br>
will be handled. We will
want to communicate this
publicly if we get<br>
agreement on it.<br>
<br>
<span>15:00 - 16:15</span><br>
Coordination group
participation. (Lynn)<br>
Having hopefully
developed some shared
understanding of the
charter of the<br>
CG and the work<br>
expected in the
communities, it would be
good to verify that the<br>
composition of the CG is<br>
suitable for its tasks
and to resolve any
outstanding questions
concerning<br>
group<br>
representation in the
CG.<br>
<br>
<span>16:15 - 16:30</span><br>
Break.<br>
<br>
<span>16:30 - 17:30</span><br>
Self-organization.
(Joseph)<br>
Initial discussion about
how the CG wants to
organize itself, e.g.,
do we<br>
want a chair<br>
and/or vice-chair, do we
need to form sub-groups
for any particular
tasks,<br>
how will we<br>
select people for these
things. I think it would
be good to talk about<br>
this on the first<br>
day and try to come to
some conclusions, and
then make the decisions
on<br>
the second day. If<br>
people know they would
like to serve in a
particular role, they
could make<br>
that known to<br>
the group.<br>
<br>
<span>17:30 - 18:00</span><br>
Parking lot for items we
want to come back to
before day 2 or in case
we<br>
run over time.<br>
<br>
<br>
== Day 2 ==<br>
<br>
<span>9:00 - 9:45</span><br>
Parking lot for leftover
charter/community
work/CG participation<br>
discussion items from<br>
yesterday.<br>
<br>
<span>9:45 - 10:15</span><br>
Internal and external
communications needs.
(Martin)<br>
Whether the CG needs
public and/or private
mailing lists for its
own work,<br>
whether we<br>
should stand up our own
web site, where that
site should be hosted,
what<br>
we would use the<br>
web site for, what we
think about ICANN's
web-based platform and
whether<br>
it should<br>
continue to exist and/or
be replaced by other
list(s).<br>
<br>
<span>10:15 - 10:30</span><br>
Break.<br>
<br>
<span>10:30 - 11:45</span><br>
Secretariat tasks and
selection. (Daniel)<br>
ICANN will be selecting
an independent
secretariat for the CG.
To make<br>
this selection,<br>
they will need an RFP.
So the CG needs to agree
on what the
secretariat's<br>
responsibilities<br>
will be, and possibly
needs to come up with
that RFP (or work on it<br>
together with ICANN).<br>
Again having a draft RFP
going into the meeting
might be a useful thing.<br>
<br>
<span>11:45 - 12:45</span><br>
Lunch.<br>
Self-organization,
continued. (Joseph)<br>
If we're ready by this
point, we could solicit
candidates for
chair/vice<br>
chair/whatever<br>
other positions we think
we need and hear from
them each briefly about<br>
what they would<br>
bring to the role(s).<br>
<br>
<span>12:45 - 13:30</span><br>
Complete
self-organization.<br>
<br>
<span>13:30 - 14:15</span><br>
Timeline. (Russ H.)<br>
It would be good to get
some agreement about the
drop-dead date for the<br>
final proposal to<br>
be submitted to NTIA
(assuming they need some
lead time to review it
and<br>
socialize it<br>
within the USG before
the contract actually
expires). We can then
work<br>
backwards from<br>
there and set goals for
when it would be good to
have the community<br>
discussions come to a<br>
close. As with the
charter, it would be
helpful for someone to
come up<br>
with a proposal for<br>
this in advance of the
meeting. Jari has
provided a proposal for
this.<br>
<br>
<span>14:15 - 15:00</span><br>
CG meeting/conference
call schedule. (Milton)<br>
We need to figure out
how often we'd like to
have calls and when our<br>
face-to-face meetings<br>
will be. This would be
another good item to
have a proposal for in
advance.<br>
<br>
<span>15:00 - 15:45</span><br>
Parking lot for any item
we need to come back to.<br>
<br>
<span>15:45 - 16:00</span><br>
Break.<br>
<br>
<span>16:00 - 16:30</span><br>
Parking lot for any item
we need to come back to.<br>
<br>
<span>16:30 - 17:00</span><br>
Summary and wrap-up.<span><font
color="#888888"><br
clear="all">
<br>
--<span
class="Apple-converted-space"> </span><br>
<div dir="ltr"><br>
<br>
<br>
Narelle Clark<br>
President and
Board Member<br>
Internet Society
of Australia<br>
ph: 0412 297 043<br>
int ph:<span
class="Apple-converted-space"> </span><a
moz-do-not-send="true" href="tel:%2B61%20412%20297%20043"
value="+61412297043"
target="_blank">+61
412 297 043</a><br>
<a
moz-do-not-send="true"
href="mailto:president@isoc-au.org.au" target="_blank">narelle@isoc-au.org.au</a><br>
<a
moz-do-not-send="true"
href="http://www.isoc-au.org.au/" target="_blank">www.isoc-au.org.au</a><br>
The Internet is
for Everyone!<br>
</div>
</font></span></div>
</blockquote>
</div>
<br>
<br clear="all">
<br>
--<span
class="Apple-converted-space"> </span><br>
<div dir="ltr"><br>
<br>
<br>
Narelle Clark<br>
President and Board Member<br>
Internet Society of
Australia<br>
ph: 0412 297 043<br>
int ph:<span
class="Apple-converted-space"> </span><a
moz-do-not-send="true"
href="tel:%2B61%20412%20297%20043"
value="+61412297043"
target="_blank">+61 412
297 043</a><br>
<a moz-do-not-send="true"
href="mailto:president@isoc-au.org.au"
target="_blank">narelle@isoc-au.org.au</a><br>
<a moz-do-not-send="true"
href="http://www.isoc-au.org.au/"
target="_blank">www.isoc-au.org.au</a><br>
The Internet is for
Everyone!<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<br>
--<span class="Apple-converted-space"> </span><br>
<div dir="ltr"><br>
<br>
<br>
Narelle Clark<br>
President and Board Member<br>
Internet Society of Australia<br>
ph: 0412 297 043<br>
int ph:<span
class="Apple-converted-space"> </span><a
moz-do-not-send="true"
href="tel:%2B61%20412%20297%20043"
value="+61412297043"
target="_blank">+61 412 297 043</a><br>
<a moz-do-not-send="true"
href="mailto:president@isoc-au.org.au"
target="_blank">narelle@isoc-au.org.au</a><br>
<a moz-do-not-send="true"
href="http://www.isoc-au.org.au/"
target="_blank">www.isoc-au.org.au</a><br>
The Internet is for Everyone!<br>
</div>
</div>
</div>
</div>
_______________________________________________<br>
Isoc-advisory-council mailing list<br>
<a moz-do-not-send="true"
href="mailto:Isoc-advisory-council@elists.isoc.org"
target="_blank">Isoc-advisory-council@elists.isoc.org</a><br>
<a moz-do-not-send="true"
href="https://elists.isoc.org/mailman/listinfo/isoc-advisory-council"
target="_blank">https://elists.isoc.org/mailman/listinfo/isoc-advisory-council</a><br>
</blockquote>
</div>
<br>
</div>
<br>
_______________________________________________<br>
IANAxfer mailing list<br>
<a moz-do-not-send="true"
href="mailto:IANAxfer@elists.isoc.org">IANAxfer@elists.isoc.org</a><br>
<a moz-do-not-send="true"
href="https://elists.isoc.org/mailman/listinfo/ianaxfer"
target="_blank">https://elists.isoc.org/mailman/listinfo/ianaxfer</a><br>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<br>
--<span class="Apple-converted-space"> </span><br>
<div dir="ltr">------------------------------------------------------------------------<br>
<font color="#888888">
<blockquote style="margin: 0pt 0pt 0pt 0.8ex;
border-left-width: 1px; border-left-style:
solid; border-left-color: rgb(204, 204, 204);
padding-left: 1ex; font-family: garamond,
serif;"><i><span style="color: rgb(0, 102, 0);">Seun
Ojedeji,<br style="color: rgb(0, 102, 0);">
</span><span style="color: rgb(0, 102, 0);">Federal
University Oye-Ekiti<br style="color: rgb(0,
102, 0);">
</span><span style="color: rgb(0, 102, 0);">web:
<span class="Apple-converted-space"> </span></span><a
moz-do-not-send="true"
href="http://www.fuoye.edu.ng/"
target="_blank">http://www.fuoye.edu.ng</a><br>
<span style="color: rgb(0, 102, 0);"></span><span
style="color: rgb(0, 102, 0);">Mobile:<span
class="Apple-converted-space"> </span><a
moz-do-not-send="true"
value="+2348035233535">+2348035233535</a></span><span
style="color: rgb(0, 102, 0);"></span><br>
</i><i><span style="color: rgb(0, 102, 0);">alt
email:<a moz-do-not-send="true"
href="http://goog_1872880453/"
target="_blank"><span
class="Apple-converted-space"> </span></a><a
moz-do-not-send="true"
href="mailto:seun.ojedeji@fuoye.edu.ng"
target="_blank">seun.ojedeji@fuoye.edu.ng</a></span></i><br>
<br>
<blockquote style="margin: 0px 0px 0px 0.8ex;
border-left-width: 1px; border-left-style:
solid; border-left-color: rgb(204, 204, 204);
padding-left: 1ex;">The key to understanding
is humility - my view !</blockquote>
</blockquote>
</font></div>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
IANAxfer mailing list
<a class="moz-txt-link-abbreviated" href="mailto:IANAxfer@elists.isoc.org">IANAxfer@elists.isoc.org</a>
<a class="moz-txt-link-freetext" href="https://elists.isoc.org/mailman/listinfo/ianaxfer">https://elists.isoc.org/mailman/listinfo/ianaxfer</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Olivier MJ Crépin-Leblond, PhD
<a class="moz-txt-link-freetext" href="http://www.gih.com/ocl.html">http://www.gih.com/ocl.html</a>
</pre>
</body>
</html>