[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: What is the purpose of the discussion? Answer
There is a difficult balance here. If the requirements are too specific
for one protocol, then they should simply be taken to the working
group that deals with that protocol. If they are too general, then,
as you mention, they will not have much relevance to the work of
the IETF. Somewhere between these extremes are requirements that
are specific enough, but do not affect current protocol work, and
therefore should point to places that need attention in IETF.
I think the current set of requirements has some that are very general
and others that are more specific.
jak
>From: "Atsushi Takeshita" <takeshita@dcl.docomo-usa.com>
>To: <more@ops.ietf.org>
>Cc: <paul.reynolds@orange.co.uk>
>Subject: Re: What is the purpose of the discussion? Answer
>Date: Tue, 12 Jun 2001 17:20:46 -0700
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
>
>Paul,
>
>Thank you for your reply.
>
>I understand your point.
>My concern is that the requirements are too general
>to influence IETF discussion.
>
>I guess we need to make detailed requirements for
>a specific topics based on the informational RFC you
>mentioned below.
>
>Am I correct?
>
>If my guess is correct, I understand the goal of this discussion
>and its importance.
>
>
>
>----- Original Message -----
>From: <paul.reynolds@orange.co.uk>
>To: <more@ops.ietf.org>
>Sent: Tuesday, June 12, 2001 1:17 AM
>Subject: What is the purpose of the discussion? Answer
>
>
>>
>> For many years, individuals involved in ISPs have been an important
>component
>> of IETF, as they have brought experience and requirements to the task of
>> developing protocols for the Internet. Until recently, most ISPs were
>involved
>> in providing service through standard wired networks. With the growth of
>the
>> wireless Internet, the technology and business of mobile operators are
>becoming
>> more like that of an ISP and less like that of a telephone company. Mobile
>> operators have traditionally not had as close a relationship with the
>IETF. To
>> start this engaugement an Internet Draft
>>
>http://www.ietf.org/internet-draft/draft-reynolds-mobile-isp-requirements-00
>.txt
>> , has been produced which represents the result of a year long study
>comprising
>> the major mobile operators and mobile ISPs.
>>
>> The percieved problem is that the IETF needs to tackle, that isn't already
>> within scope for an existing WGs, is to have protocol development more
>focused
>> upon wireless requirements. To address this problem the discussion has two
>main
>> objectives:
>>
>> 1: Present an opportunity for companies and individuals that will have to
>> deploy and offer Internet services on wireless networks to present ***
>what they
>> think the wireless requirements for the protocols to support those
>services
>> should be ***, and for equipment vendors, software developers, academic
>> researchers, and others involved in engineering and development of mobile
>> networking protocols *** to engage in a discussion with the wireless ISPs
>on
>> their requirements ***
>>
>> 2: The next stage is to *** conduct a BoF *** which will make the case for
>> forming a short term, focused, working group to refine the requirements
>in
>> draft-reynolds-mobile-isp-requirements-00.txt for *** publication as an
>> Informational RFC ***.
>>
>>
>> Paul Reynolds
>> Orange SA
>>
>>
>>
>>
>****************************************************************************
>***
>> Important. This E-mail is intended for the above named person and may be
>> confidential and/or legally privileged. If this has come to you in error
>you
>> must take no action based on it, nor must you copy or show it to anyone;
>please
>> inform the sender immediately.
>>
>****************************************************************************
>***
>>
>>
>>
>
>