Tópicos para Proyecto del Ramo

        Title           : Simple Control Transmission Protocol
        Author(s)       : R. Stewart, Q. Xie,  K. Morneault, C. Sharp,
                          H. Schwarzbauer,  T. Taylor,  I. Rytina,
                          M. Kalla, L. Zhang, V. Paxon
        Filename        : draft-ietf-sigtran-sctp-07.txt
        Pages           : 96
        Date            : 02-Mar-00
 
This document describes the Simple Control Transmission Protocol
(SCTP). SCTP is designed to transport PSTN signalling messages over
IP networks, but is capable of broader applications.
SCTP is a reliable datagram transfer protocol operating on top of an
unreliable routed packet network such as IP. It offers the following
services to its users:
-- acknowledged error-free non-duplicated transfer of user data,
-- data segmentation to conform to discovered path MTU size,
-- sequenced delivery of user messages within multiple streams,
with an option for order-of-arrival delivery of individual
user messages,
-- optional multiplexing of user messages into SCTP datagrams, and
-- network-level fault tolerance through supporting of multi-homing
at either or both ends of an association.
The design of SCTP includes appropriate congestion avoidance behaviour
and resistance to flooding and masquerade attacks.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sigtran-sctp-07.txt


        Title           : Extension of the Session Description Protocol (SDP)
                          for ATM-based  Narrowband Telephon
        Author(s)       : R. Kumar, M. Mostafa
        Filename        : draft-rajeshkumar-mmusic-sdp-atm-00.txt
        Pages           : 29
        Date            : 08-Mar-00
 
This document extends the Session Description Protocol (SDP)
described in RFC2327 for narrowband telephony applications that use
AAL1 or AAL2. The list of extensions is meant to be exhaustive.
Individual applications can use subsets of these extensions.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-rajeshkumar-mmusic-sdp-atm-00.txt

        Title           : Overview of Transition Techniques for IPv6
                          only to Talk to IPv4-only Communication
        Author(s)       : K. Yamamoto, M. Sumikawa
        Filename        : draft-ietf-ngtrans-translator-03.txt
        Pages           : 8
        Date            : 09-Mar-00
 
This memo discusses translators to enable direct communication
between IPv4 hosts and IPv6 hosts. Three translation mechanisms are
described. From the address mapping point of view, the translators
are categorized into four types and each feasibility is considered.
This memo is based on a paper appeared in Proceedings of
INET98[INET].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ngtrans-translator-03.txt

        Title           : Asynchronous Layered Coding A scalable reliable
                          multicast protocol
        Author(s)       : M. Luby, L. Vicisano et.al
        Filename        : draft-ietf-rmt-pi-alc-00.txt
        Pages           : 28
        Date            : 10-Mar-00
 
This document describes Asynchronous Layered Coding, a scalable reli-
able multicast protocol, hereafter referred to as ALC.   ALC can be
used to reliably transmit objects to multiple receivers.  An object
can be any well-defined piece of data.  Examples include any type of
file such as a group of pictures in an MPEG stream, a MP3 music file,
a JPEG image, and a collection of files that are zipped into one
file.  In addition, the ALC delivery model is fairly flexible, e.g.,
on demand or a push delivery.  When using ALC, the payload of the
packets that flow from senders to receivers in no way depend on net-
work conditions or the reaction of receivers to these conditions,
although the rate of flow of the packets in various parts of the net-
work does depend on network conditions. Receivers may join or leave
an existing packet stream in an asynchronous manner independent of
other receivers. Congestion control is achieved by sending several
packet streams ordered in a layered fashion and delivering only a
subset of these to individual receivers. The number of streams
received is dictated by the local bandwidth availability and network
conditions. A possible way to achieve this is by using a distinct
multicast address for each stream.   Receivers join the lowest layer
stream they are not currently joined to at coordinated points in time
when there is more available bandwidth between those receivers and
the sender.  Similarly, receivers leave one or more highest layer
streams they are currently joined to as soon as they feel congestion
(typically as evidenced by packet loss).  Another possibility to
achieve this form of congestion control is through router-assisted
schemes. Reliability is achieved via FEC coding only, i.e. there is
no request for feedback for retransmission from receivers that miss
packets for whatever reason.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rmt-pi-alc-00.txt

        Title           : Reliable Multicast Transport Building Block: Forward
                          Error Correction Codes
        Author(s)       : M. Luby, L. Vicisano et.al
        Filename        : draft-ietf-rmt-bb-fec-00.txt
        Pages           : 14
        Date            : 10-Mar-00
 
This memo describes the use of Forward Error Correction (FEC) codes
within the context of reliable IP multicast transport and provides an
introduction to some commonly-used FEC codes.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rmt-bb-fec-00.txt

        Title           : RTP: A Transport Protocol for Real-Time Applications
        Author(s)       : H. Schulzrinne, S. Casner, R. Frederick, V. Jacobson
        Filename        : draft-ietf-avt-rtp-new-07.txt,.ps
        Pages           : 101
        Date            : 13-Mar-00
 
This memorandum is a revision of RFC 1889 in preparation for
advancement from Proposed Standard to Draft Standard status. Readers
are encouraged to use the PostScript form of this draft to see where
changes from RFC 1889 are marked by change bars.
This memorandum describes RTP, the real-time transport protocol. RTP
provides end-to-end network transport functions suitable for
applications transmitting real-time data, such as audio, video or
simulation data, over multicast or unicast network services. RTP does
not address resource reservation and does not guarantee quality-of-
service for real-time services. The data transport is augmented by a
control protocol (RTCP) to allow monitoring of the data delivery in a
manner scalable to large multicast networks, and to provide minimal
control and identification functionality. RTP and RTCP are designed
to be independent of the underlying transport and network layers. The
protocol supports the use of RTP-level translators and mixers.
This specification is a product of the Audio/Video Transport working
group within the Internet Engineering Task Force. Comments are
solicited and should be addressed to the working group's mailing list
at rem-conf@es.net and/or the authors.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-new-07.txt


        Title           : Extension of the Session Description Protocol (SDP)
                          for ATM-based Narrowband Telephony
        Author(s)       : R. Kumar, M. Mostafa
        Filename        : draft-rajeshkumar-mmusic-sdp-atm-01.txt
        Pages           : 29
        Date            : 13-Mar-00
 
This document extends the Session Description Protocol (SDP)
described in RFC2327 for narrowband telephony applications that use
AAL1 or AAL2. The list of extensions is meant to be exhaustive.
Individual applications can use subsets of these extensions.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-rajeshkumar-mmusic-sdp-atm-01.txt


        Title           : IP Version 6 Multicast Addressing Architecture
        Author(s)       : B. Haberman, D. Thaler
        Filename        : draft-haberman-ipngwg-mcast-arch-01.txt
        Pages           : 7
        Date            : 13-Mar-00
 
This specification defines the multicast addressing architecture of the
IP Version 6 protocol.  The updated multicast address architecture
presented in this document allows for unicast prefix-based allocation
of multicast addresses.  It is an update of section 2.7 of the RFC
2373.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-haberman-ipngwg-mcast-arch-01.txt


        Title           : RObust Checksum-based header COmpression (ROCCO)
        Author(s)       : L. Jonsson, M. Degermark, H. Hannu, K. Svanbro
        Filename        : draft-jonsson-robust-hc-04.txt,.ps
        Pages           : 67
        Date            : 13-Mar-00
 
IP/UDP/RTP header compression [CRTP] can generate a large number of
lost packets when used over links with significant error rates,
especially when the round-trip time of the link is large.
This document describes a more robust header compression scheme. The
scheme is adaptable to the characteristics of the link over which it
is used and also to the properties of the packet streams it
compresses. Robustness against link-loss is achieved without
decreasing compression efficiency.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-jonsson-robust-hc-04.txt


        Title           : Source-Specific Multicast for IP
        Author(s)       : H. Holbrook, B. Cain
        Filename        : draft-holbrook-ssm-00.txt
        Pages           : 18
        Date            : 13-Mar-00
 
IP addresses in the 232/8 (232.0.0.0 to 232.255.255.255) range are
designated as source-specific multicast (SSM) destination addresses and
are reserved for use by source-specific applications and protocols
[IANA-ALLOCATION].  This document defines the semantics of source-
specific multicast addresses and specifies the policies governing their
use.  It defines an extension to the Internet network service that
applies to datagrams sent to SSM addresses and defines the host
extensions to support this service.

Appendix I of this document describes changes to the Internet Group
Management Protocol Version 3 (IGMPv3) [IGMPv3] to support source-
specific multicast.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-holbrook-ssm-00.txt

        Title           : The UDP Lite Protocol
        Author(s)       : L. Larzon, S. Pink, M. Degermark
        Filename        : draft-larzon-udplite-02.txt
        Pages           : 5
        Date            : 13-Mar-00
 
This document describes the UDP Lite Protocol,  which  is
similar   to   classic   UDP   [RFC-768],  but  aimed  at
applications which can handle a partially damaged payload
in  lossy  network  environments.  If this feature is not
used, it is semantically identical to classic UDP.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-larzon-udplite-02.txt


        Title           : Protocol Independent Multicast Routing in the Internet
                          Protocol Version 6 (IPv6)
        Author(s)       : H. Sandick, G. Kump, B. Haberman
        Filename        : draft-ietf-pim-ipv6-03.txt
        Pages           : 5
        Date            : 13-Mar-00
 
This document outlines recommendations in the use of the Protocol
Independent Multicast routing protocol to support Internet Protocol
version 6.  It describes the changes needed in order to handle the
differences between IPv6 and IPv4 and conform to the logic introduced
by other routing protocols enabled for IPv6.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pim-ipv6-03.txt


        Title           : Network performance measurement for periodic streams
        Author(s)       : G. Grotefeld, V. Raisanen
        Filename        : draft-ietf-ippm-npmps-00.txt
        Pages           : 17
        Date            : 14-Mar-00
 
This document describes some of the issues associated with
application-level measurements of network performance for periodic
streams. An example application would be the testing of Dst-Src routes
for use as bearer for multimedia streams. In this document,
the reader is assumed to be familiar with the terminology of the
Framework for IP Performance Metrics RFC 2330 [1].  This document is
parallel to A One-way Delay Metric for IPPM RFC 2679[2]. A sample
metric is described that is suitable for application-level measurement
for streaming multimedia over IP. Using such a measurement,
transmission service of a network is probed with a traffic stream
similar to that of the application of interest, which is likely to be
very dissimilar to the Poisson inter-arrival interval described in [2].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ippm-npmps-00.txt


        Title           : Source-Specific Protocol Independent Multicast
        Author(s)       : N. Bhaskar, I. Kouvelas
        Filename        : draft-bhaskar-pim-ss-00.txt
        Pages           : 11
        Date            : 14-Mar-00
 
Source-Specific PIM (PIM-SS) is a variant of PIM Sparse-Mode that only
builds source specific shortest path trees. These trees are built
directly on receiving group membership reports that request a given
source. PIM-SS precludes the building of shared trees, effectively par-
titioning the different source trees from one another. For this reason
it is specifically suited for existing multicast applications for which
there is expected and intended to be exactly one source.

Source-Specific PIM can co-exist with PIM-SM. It uses a subset of PIM-SM
messages and lends itself to incremental deployment.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-bhaskar-pim-ss-00.txt


        Title           : The Congestion Manager
        Author(s)       : H. Balakrishnan, S. Seshan
        Filename        : draft-balakrishnan-cm-02.txt
        Pages           :
        Date            : 14-Mar-00
 
This document describes the Congestion Manager (CM), an end-system
module that (i) enables an ensemble of multiple concurrent flows
from a sender destined to the same receiver and sharing the same
congestion properties to perform proper congestion avoidance and
control, and (ii) allows applications to easily adapt to network
congestion. This CM framework integrates congestion management
across all applications and transport protocols. The CM maintains
congestion parameters (available aggregate and per-flow bandwidth,
per-receiver round-trip times, etc.) and exports an API that
enables applications to learn about network characteristics, pass
information to the CM, share congestion information with each
other, and schedule data transmissions. This document focuses on
applications and transport protocols with their own independent
per-byte or per-packet sequence number information, and does not
require modifications to the receiver protocol stack.  The
receiving application must provide feedback to the sending
application about received packets and losses, and the latter uses
the CM API to update CM state.  This document does not address
networks with reservations or service discrimination.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-balakrishnan-cm-02.txt


        Title           : TCP Congestion Window Validation
        Author(s)       : M. Handley, J. Padhye, S. Floyd
        Filename        : draft-handley-tcp-cwv-02.txt
        Pages           : 11
        Date            : 14-Mar-00
 
TCP's congestion window controls the number of packets a TCP flow may
have in the network at any time.  However, long periods when the
sender is idle or application-limited can lead to the invalidation of
the congestion window, in that the congestion window no longer
reflects current information about the state of the network.  This
document describes a simple modification to TCP's congestion control
algorithms to decay the congestion window cwnd after the transition
from a sufficiently-long application-limited period, while using the
slow-start threshold ssthresh to save information about the previous
value of the congestion window.
An invalid congestion window also results when the congestion window
is increased (i.e., in TCP's slow-start or congestion avoidance
phases) during application-limited periods, when the previous value
of the congestion window might never have been fully utilized.  We
propose that the TCP sender should not increase the congestion window
when the TCP sender has been application-limited (and therefore has
not fully used the current congestion window).  We have explored
these algorithms both with simulations and with experiments from an
implementation in FreeBSD.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-handley-tcp-cwv-02.txt


        Title           : IP Version 6 Addressing Architecture
        Author(s)       : R. Hinden, S. Deering
        Filename        : draft-ietf-ipngwg-addr-arch-v3-00.txt
        Pages           : 25
        Date            : 15-Mar-00
 
This specification defines the addressing architecture of the IP
Version 6 protocol [IPV6].  The document includes the IPv6 addressing
model, text representations of IPv6 addresses, definition of IPv6
unicast addresses, anycast addresses, and multicast addresses, and an
IPv6 node's required addresses.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ipngwg-addr-arch-v3-00.txt


        Title           : PIM-SM Rules for Support of Single-Source Multicast
        Author(s)       : H. Sandick, B. Cain
        Filename        : draft-sandick-pimsm-ssmrules-00.txt
        Pages           : 14
        Date            : 15-Mar-00
 
This document describes the minor changes in protocol processing rules
for the PIM-SM [PIMSM] protocol to support source specific multicast
(SSM) routing semantics over the SSM address range [EXPRESS][SSM]. Used
in combination with IGMPv3 [IGMPV3], the SSM delivery model can be
supported with current protocol implementations.  IGMPv3 can be used for
communicating source specific (S,G) channel memberships to local
routers; PIM-SM can be used for construction of SSM forwarding trees.
This document describes the processing rules for PIM-SM in the SSM
address range to support construction of SSM delivery trees.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-sandick-pimsm-ssmrules-00.txt


        Title           : A Guide to the Introduction of IPv6 in the IPv4 World
        Author(s)       : W. Biemolt, H. Steenman, M. Kaat, A. Durand,
                          G. Tsirtsis, R. van der Pol, Y. Sekiya
        Filename        : draft-ietf-ngtrans-introduction-to-ipv6-transition-03.txt
        Pages           : 36
        Date            : 15-Mar-00
 
This document is a guide to the introduction of IPv6 in the IPv4
based Internet or Intranets.  Several general issues to start IPv6
networking in a predominantly IPv4 world are discussed, such as IPv6
addresses, IPv6 DNS and routing issues.  Short descriptions are given
of the different translation and migration tools and mechanisms that
translate between IPv6 and IPv4 and/or tunnel IPv6 over IPv4.  The
remainder of this document describes how IPv6 can be introduced in
various environments, such as ISPs, Internet Exchanges and end user
environments.  Suggestions are given on the use of the different
translation and migration tools in each environment.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ngtrans-introduction-to-ipv6-transition-03.txt

        Title           : Reliable Multicast Transport Building Blocks for
                          One-to-Many Bulk-Data Transfer
        Author(s)       : B. Whetten, M. Handley, S. Floyd, R. Kermode,
                          L. Vicisano, M. Luby
        Filename        : draft-ietf-rmt-buildingblocks-02.txt
        Pages           : 21
        Date            : 15-Mar-00
 
This document describes a framework for the standardization of bulk-data
reliable multicast transport.  It builds upon the experience gained
during the deployment of several classes of contemporary reliable
multicast transport, and attempts to pull out the commonalities between
these classes of protocols into a number of building blocks. To that
end, this document recommends that certain components that are common to
multiple protocol classes be standardized as 'building blocks.' The
remaining parts of the protocols, consisting of highly protocol
specific, tightly intertwined functions, shall be designated as
'protocol cores.'  Thus, each protocol can then be constructed by
merging a 'protocol core' with a number of 'building blocks' which can
be re-used across multiple protocols.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rmt-buildingblocks-02.txt


        Title           : Mobility Support in IPv6
        Author(s)       : D. Johnson, C. Perkins
        Filename        : draft-ietf-mobileip-ipv6-11.txt
        Pages           : 104
        Date            : 16-Mar-00
 
This document specifies the operation of mobile computers using IPv6.
Each mobile node is always identified by its home address, regardless
of its current point of attachment to the Internet.  While situated
away from its home, a mobile node is also associated with a care-of
address, which provides information about the mobile node's current
location.  IPv6 packets addressed to a mobile node's home address are
transparently routed to its care-of address.  The protocol enables
IPv6 nodes to cache the binding of a mobile node's home address with
its care-of address, and to then send any packets destined for the
mobile node directly to it at this care-of address.  To support this
operation, Mobile IPv6 defines four new IPv6 destination options,
including one that MUST be supported in packets received by any node,
whether mobile or stationary.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mobileip-ipv6-11.txt


        Title           : Multicast DNS
        Author(s)       : B. Aboba, L. Esibov, D. Thaler
        Filename        : draft-aboba-dnsext-mdns-00.txt
        Pages           : 10
        Date            : 16-Mar-00
 
Today, with the rise of home networking, there are an increasing number
of small networks operating without a DNS server. In order to allow DNS
name resolution in such environments, the use of a multicast DNS is
proposed.

With wide deployment of the hosts registered with IPv6 addresses by
routers, in the absence of the DHCP server multicast DNS is proposed to
be used to discover available DNS servers, that will be used for unicast
DNS.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-aboba-dnsext-mdns-00.txt


        Title           : Number Portability in the GSTN: An Overview
        Author(s)       : M. Foster, J. Yu, T. McGarry
        Filename        : draft-foster-e164-gstn-np-00.txt
        Pages           : 28
        Date            : 16-Mar-00
 
This document provides an overview of E.164 telephone number
portability (NP) in the Global Switched Telephone Network (GSTN).
There are three types of number portability: service provider
portability (SPNP), location portability, and service portability.
Service provider portability, the focus of the present draft, is a
regulatory imperative in many countries seeking to liberalize local
telephony service competition, by enabling end-users to retain pre-
existing telephone numbers while changing service providers.
Implementation of NP within national GSTN entails potentially
significant changes to numbering administration, network element
signaling, call routing and processing, billing, service management,
and other functions.  NP changes the fundamental nature of a dialed
E.164 number from a hierarchical physical routing address to a
virtual address, thereby requiring the transparent translation of
the later to the former.  In addition, there are various regulatory
constraints which establish relevant parameters for NP
implementation, most of which are not network technology specific.
Consequently, the implementation of NP behavior consistent with
applicable regulatory constraints, as well as the need for
interoperation with the existing GSTN NP implementations, are
relevant topics for numerous areas of IP telephony work-in-progress
at IETF.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-foster-e164-gstn-np-00.txt


       Title           : Universal Mobile IP (UMIP) Location Management
        Author(s)       : J. Wang, A. Tang
        Filename        : draft-wang-mobileip-umip-00.txt
        Pages           : 34
        Date            : 16-Mar-00
 
Global roaming is one of the design objectives for next generation
(3G) cellular networks.  To efficiently support real-time
applications for mobile users in these networks, signaling and
payload traffic delays must be minimal.  It has been identified that
one of the sources causing long delays is triangle routing. That is,
for example, in the registration process the registration requests
have to be transmitted from a foreign agent in the visited network
all the way to the home network every time the mobile node initiates
a call or when the mobile node roams into a different visiting
network [2].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-wang-mobileip-umip-00.txt


        Title           : A ''traceroute'' facility for IP Multicast.
        Author(s)       : B. Fenner, S. Casner
        Filename        : draft-ietf-idmr-traceroute-ipm-06.txt,.ps
        Pages           : 22
        Date            : 16-Mar-00
 
This draft describes the IGMP multicast traceroute facility.
Unlike unicast traceroute, multicast traceroute requires a special
packet type and implementation on the part of routers.  This speci-
fication describes the required functionality in multicast routers,
as well as how management applications can use the new router func-
tionality.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idmr-traceroute-ipm-06.txt


        Title           : Advice for Internet Subnetwork Designers
        Author(s)       : P. Karn, J. Touch, J. Mahdavi, D. Grossman,
                          G. Montenegro, A. Falk, M. Montpetit, G. Fairhurst
        Filename        : draft-ietf-pilc-link-design-02.txt
        Pages           : 21
        Date            : 16-Mar-00
 
This document provides advice to the designers of digital
communication equipment, link layer protocols and packet switched
subnetworks (collectively referred to as subnetworks) who wish to
support the Internet protocols but who may be unfamiliar with the
architecture of the Internet and the implications of their design
choices on the performance and efficiency of the Internet.
This document represents an evolving consensus of the members of the
IETF Performance Implications of Link Characteristics (PILC) working
group.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pilc-link-design-02.txt


        Title           : TCP Performance Implications of Network Asymmetry
        Author(s)       : H. Balakrishnan, V. Padmanabhan
        Filename        : draft-ietf-pilc-asym-01.txt
        Pages           : 15
        Date            : 15-Mar-00
 
This document describes TCP performance problems that arise because
of asymmetric effects. These problems arise in several access
networks, including bandwidth-asymmetric networks and packet radio
networks, for different underlying reasons. However, the net effect
on TCP performance is the same in both cases: performance degrades
significantly because of imperfection and variability in the ACK
feedback from the receiver to the sender. This document details
several solutions to these problems, which use a combination of
local link-layer techniques and end-to-end mechanisms. Solutions to
the problem of asymmetry are two-pronged: (i) techniques to manage
the reverse channel used by ACKs, typically using header compression
or reducing the frequency of TCP ACKs, and (ii) techniques to handle
this reduced ACK frequency to retain the TCP sender's
acknowledgment-triggered self-clocking.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pilc-asym-01.txt