RE: WG Last Call: draft-ietf-v6ops-3gpp-cases-02.txt

["Fischer, Christine A (Chris)" <cafischer@lucent.com>]

Comments from Chris Fischer on Transition Scenarios for 3GPP Networks

Section 2, last paragraph: It might be useful to include a reference to 3GPP TS 23.221, "Architectural requirements", which shows the transition scenarios for 3GPP.

Section 3.1, third paragraph: change "comprised of" to "comprising"

Section 3.2, under I-CSCF:  typo on "operator's"
same section: change "an 3GPP" to "a 3GPP"

Section 4.1, item 1), last paragraph: You may want to add a comment that this may require the use of NAT on external interfaces, when appropriate.  Also, a comment that the placement and handling of DNS servers for IPv4 / IPv6 communication has not been included in these scenarios.

Section 4.1, item 4): Please define intent of the boxes marked by "x".  Are these IPv4 networks or transition gateways?

Page 10, under Acknowledgements:  There is an unknown character after Sipil.


-----Original Message-----
From: Margaret Wasserman [mailto:mrw@windriver.com]
Sent: Monday, February 17, 2003 11:05 AM
To: v6ops@ops.ietf.org
Subject: WG Last Call: draft-ietf-v6ops-3gpp-cases-02.txt




Hi All,

This is a WG Last Call for comments on sending the 3GPP scenarios
document to the IESG for consideration as an Informational RFC:

Title:     Transition Scenarios for 3GPP Networks
Filename:  draft-ietf-v6ops-3gpp-cases-02.txt
Editor:    J. Soininen
Date:      January 2003

The document can be found at:
http://www.ietf.org/internet-drafts/draft-ietf-v6ops-3gpp-cases-02.txt

Abstract

    This document describes different scenarios in Third Generation
    Partnership Project (3GPP) defined packet network, i.e. General
    Packet Radio Service (GPRS) that would need IP version 6 and IP
    version 4 transition. The focus of this document is on the scenarios
    where the User Equipment (UE) connects to nodes in other networks,
    e.g. in the Internet. GPRS network internal transition scenarios,
    i.e. between different GPRS elements in the network, are out of scope
    of this document.

    The purpose of the document is to list the scenarios for further
    discussion and study.

Since this is the first WG last call that we have had in the v6ops
WG, we would like to remind you of the process that we discussed for
WG last calls when we started this WG.

The WG Last Call is a final check that the WG has rough consensus
to advance the document to the IESG.  Advancing a document to the
IESG indicates that the WG believes that this document is both
technically sound and useful.  It also indicates that we believe
that the document meets all of the requirements for publication
as an RFC.

To pass WG last call, this document must be reviewed and actively
supported by a significant number of people, including experts in
all applicable areas, or it will not be sent to the IESG.

Silence does NOT indicate consent during this phase.

So, please review this document carefully, and send your feedback
to the list, indicating whether or not you believe that this
document is ready to go to the IESG.  Unless sufficient support
is demonstrated on the list, the document will not be send to
the IESG.

Thanks,
Margaret, Itojun and Bob
v6ops WG Chairs