Ting Zou (Tina Tsou)

Authored 10+ Internet Engineering Task Force (IETF) Requests for Comments (RFCs) including:
>> RFC5729, Clarifications on the Routing of Diameter Requests Based on the Username and the Realm
>> RFC 5866, Diameter Quality-of-Service Application
>> RFC 6159, Session-Specific Explicit Diameter Request Routing
>> RFC 6431, Huawei Port Range Configuration Options for PPP IP Control Protocol (IPCP)
>> RFC 6479, IPsec Anti-Replay Algorithm Without Bit… Show more

Authored 10+ Internet Engineering Task Force (IETF) Requests for Comments (RFCs) including:
>> RFC5729, Clarifications on the Routing of Diameter Requests Based on the Username and the Realm
>> RFC 5866, Diameter Quality-of-Service Application
>> RFC 6159, Session-Specific Explicit Diameter Request Routing
>> RFC 6431, Huawei Port Range Configuration Options for PPP IP Control Protocol (IPCP)
>> RFC 6479, IPsec Anti-Replay Algorithm Without Bit Shifting
>> RFC 6654, Gateway-Initiated IPv6 Rapid Deployment on IPv4 Infrastructures (GI 6rd)
>> RFC 7075, Realm-Based Redirection In Diameter
>> RFC7388, Definition of Managed Objects for IPv6 over Low-Power Wireless Personal
>> RFC7596, Lightweight 4over6: An Extension to the Dual-Stack Lite Architecture
>> RFC7658, Deprecation of MIB Module NAT-MIB: Managed Objects for Network Address Translators (NATs)
>> RFC7659, Definitions of Managed Objects for Network Address Translators (NATs)
>> RFC7666, Management Information Base for Virtual Machines Controlled by a Hypervisor
>> Wrote Internet Architecture Board paper entitled “Protocol Profiles for Constrained Devices,” 2011 Show less

>> J. Brzozowski, T. Tsou, D Fang, D. Lopez, G. Turner, 2014, “ONLINE EXCLUSIVE: Bits-N-Bytes: Running Code at IETF,” IETF Journal. https://www.internetsociety.org/articles/online-exclusive-bits-n-bytes-running-code-ietf
>> Wending X., Tina T., Diego L., Qiong S. Wei F., Haiyong X., 2013, “A Software Defined Approach to Unified IPv6 Transition”, Sigcomm’13. http://conferences.sigcomm.org/sigcomm/2013/papers/sigcomm/p547.pdf
>> H. Xie, Y. Li, J. Wang, D. Lopez, T. Tsou… Show more

>> J. Brzozowski, T. Tsou, D Fang, D. Lopez, G. Turner, 2014, “ONLINE EXCLUSIVE: Bits-N-Bytes: Running Code at IETF,” IETF Journal. https://www.internetsociety.org/articles/online-exclusive-bits-n-bytes-running-code-ietf
>> Wending X., Tina T., Diego L., Qiong S. Wei F., Haiyong X., 2013, “A Software Defined Approach to Unified IPv6 Transition”, Sigcomm’13. http://conferences.sigcomm.org/sigcomm/2013/papers/sigcomm/p547.pdf
>> H. Xie, Y. Li, J. Wang, D. Lopez, T. Tsou, Y. Wen, 2013, “vRGW: Towards Network Function Virtualization Enabled by Software Defined Networking,” IEEE ICNP. http://ieeexplore.ieee.org/document/6733632/
>> Q. Sun, C. Xie, Y. Cui, Y. Chen, I. Farrer, M. Boucadair, Y. Lee, T. Tsou, S. Liu, 2013, “Lightweight 4over6 Efforts Debuted at IETF 85: An IPv4 Service Continuity Solution for Smooth IPv6 Transition,” IETF Journal. http://www.internetsociety.org/articles/lightweight-4over6-efforts-debuted-ietf-85-ipv4-service-continuity-solution-smooth-ipv6
>> M. Menth, B. Brisco, T. Tsou, 2012, “Precognition notification: new QoS support for differentiated services IP networks”, IEEE Communications Magazine. http://ieeexplore.ieee.org/Xplore/login.jsp?url=http%3A%2F%2Fieeexplore.ieee.org%2Fiel5%2F35%2F6163570%2F06163587.pdf&authDecision=-203
>> X. Deng, S. Hares, X. Huang, C. Jacquenet, Y. Ma, and T. Tsou, edited by X. Deng, 2012, “Demonstrating IPv4 Multicast Service Continuity During IPv6 Migration,” IETF Journal. http://www.internetsociety.org/articles/demonstrating-ipv4-multicast-service-continuity-during-ipv6-migration
>> T. Tsou, D. Lopez, J. Brzozowski, C. Popoviciu, C. Perkins, and D. Cheng, 2012, “Exploring IPv6 Deployment in the Enterprise: Experiences of the IT Department of Futurewei Technologies,” IETF Journal. https://www.internetsociety.org/articles/exploring-ipv6-deployment-enterprise-experiences-it-department-futurewei-technologies Show less

>> H. Xie, T. Tsou, D. Lopez, R. Sidi, H. Yin, P. Aranda, 2012, “Software-defined Networking Efforts Debuted at IETF 84,” IETF Journal. https://www.internetsociety.org/articles/software-defined-networking-efforts-debuted-ietf-84
>> T. Tsou, C. Jacquenet, X. Deng, 2011, “New Technology Demo: PCP,” IETF Journal. https://www.internetsociety.org/articles/new-technology-demo-pcp

This document defines a Dynamic Host Configuration Protocol version 6
(DHCPv6) Option for multicast IPv4 service continuity solutions,
which is used to carry the IPv6 prefixes to be used to build unicast
and multicast IPv4-embedded IPv6 addresses.

In some use cases, e.g., Lightweight 4over6, the client may require
not just one port, but a port set. This document defines an
extension to the Port Control Protocol (PCP) that allows clients to
manipulate a set of ports as a whole. This is accomplished using a
new MAP option: PORT_SET.

Various IPv6 transition strategies require the introduction of large-
scale NATs (e.g., AFTR and NAT64) to share the limited supply of IPv4
addresses available in the network until transition is complete.
There has recently been debate over how to manage the sharing of
ports between different subscribers sharing the same IPv4 address.
One factor in the discussion is the operational requirement to log
the assignment of transport addresses to subscribers. It… Show more

Various IPv6 transition strategies require the introduction of large-
scale NATs (e.g., AFTR and NAT64) to share the limited supply of IPv4
addresses available in the network until transition is complete.
There has recently been debate over how to manage the sharing of
ports between different subscribers sharing the same IPv4 address.
One factor in the discussion is the operational requirement to log
the assignment of transport addresses to subscribers. It has been
argued that dynamic assignment of individual ports between
subscribers requires the generation of an excessive volume of logs.
This document suggests a way to achieve dynamic port sharing while
keeping log volumes low. Show less

This memo deprecates MIB module NAT-MIB, a portion of the Management
Information Base (MIB) previously defined in RFC 4008 for devices
implementing Network Address Translator (NAT) function. A companion
document defines a new version, NATV2-MIB, which responds to
deficiencies found in module NAT-MIB and adds new capabilities.

This document obsoletes RFC 4008. All MIB objects specified in RFC
4008 are included in this version unchanged with only the… Show more

This memo deprecates MIB module NAT-MIB, a portion of the Management
Information Base (MIB) previously defined in RFC 4008 for devices
implementing Network Address Translator (NAT) function. A companion
document defines a new version, NATV2-MIB, which responds to
deficiencies found in module NAT-MIB and adds new capabilities.

This document obsoletes RFC 4008. All MIB objects specified in RFC
4008 are included in this version unchanged with only the STATUS
changed to deprecated. Show less

This memo defines a portion of the Management Information Base (MIB)
for devices implementing the Network Address Translator (NAT)
function. The new MIB module defined in this document, NATV2-MIB, is
intended to replace module NAT-MIB (RFC 4008). NATV2-MIB is not
backwards compatible with NAT-MIB, for reasons given in the text of
this document. A companion document deprecates all objects in NAT-
MIB. NATV2-MIB can be used for the monitoring of NAT… Show more

This memo defines a portion of the Management Information Base (MIB)
for devices implementing the Network Address Translator (NAT)
function. The new MIB module defined in this document, NATV2-MIB, is
intended to replace module NAT-MIB (RFC 4008). NATV2-MIB is not
backwards compatible with NAT-MIB, for reasons given in the text of
this document. A companion document deprecates all objects in NAT-
MIB. NATV2-MIB can be used for the monitoring of NAT instances on a
device capable of NAT function. Compliance levels are defined for
three application scenarios: basic NAT, pooled NAT, and
carrier-grade NAT (CGN). Show less

This document defines a portion of the Management Information Base
(MIB) for use with network management protocols in the Internet
community. In particular, this specifies objects for managing
virtual machines controlled by a hypervisor (a.k.a. virtual machine
monitor).

Dual-Stack Lite (DS-Lite) (RFC 6333) describes an architecture for transporting IPv4 packets over an IPv6 network. This document specifies an extension to DS-Lite called "Lightweight 4over6", which moves the Network Address and Port Translation (NAPT) function from the centralized DS-Lite tunnel concentrator to the tunnel client located in the Customer Premises Equipment (CPE). This removes the requirement for a Carrier Grade NAT function in the tunnel concentrator and reduces the amount of… Show more

Dual-Stack Lite (DS-Lite) (RFC 6333) describes an architecture for transporting IPv4 packets over an IPv6 network. This document specifies an extension to DS-Lite called "Lightweight 4over6", which moves the Network Address and Port Translation (NAPT) function from the centralized DS-Lite tunnel concentrator to the tunnel client located in the Customer Premises Equipment (CPE). This removes the requirement for a Carrier Grade NAT function in the tunnel concentrator and reduces the amount of centralized state that must be held to a per-subscriber level. In order to delegate the NAPT function and make IPv4 address sharing possible, port-restricted IPv4 addresses are allocated to the CPEs. Show less

This document defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs).

The first IETF Bits-N-Bytes took place in the summer of 2012. The Bits-N-Bytes concept, however, has deep roots in the technical and operational communities. In fact, events similar to Bits-N-Bytes were a part of the North American Network Operator’s Group meetings as early as 2009.
...

It has been a significant challenge for network carriers
to deploy and provision a large number of Customer-Premises
Equipment (CPE) devices located at subscribers’ premises and
connected to a carrier’s network infrastructure. In this paper, we
make a first systematic attempt to fundamentally re-shape the
access networks into a software defined networking architecture
by virtualizing the network functionality of residential gateways
(vRGW). Our approach can be generalized… Show more

It has been a significant challenge for network carriers
to deploy and provision a large number of Customer-Premises
Equipment (CPE) devices located at subscribers’ premises and
connected to a carrier’s network infrastructure. In this paper, we
make a first systematic attempt to fundamentally re-shape the
access networks into a software defined networking architecture
by virtualizing the network functionality of residential gateways
(vRGW). Our approach can be generalized to other CPE such
as set-top boxes. Our analysis suggests that vRGW can achieve
significant economic benefits ranging from up to 90% reduction
on the call center cost and up to 46% reduction on the product
return cost. Show less

The forthcoming transition period when both IPv4 and IPv6 will have to coexist raises new challenges for service providers. In particular, they need to ensure that their customers will still be able to access the IPv4 Internet from any IPv4-only terminal while they will be provisioned with an IPv6-only prefix. There is widespread need for continuing this so-called IPv4 Internet service.
The IETF 82 meeting last November in Taipei, Taiwan, provided an opportunity for academics, service… Show more

The forthcoming transition period when both IPv4 and IPv6 will have to coexist raises new challenges for service providers. In particular, they need to ensure that their customers will still be able to access the IPv4 Internet from any IPv4-only terminal while they will be provisioned with an IPv6-only prefix. There is widespread need for continuing this so-called IPv4 Internet service.
The IETF 82 meeting last November in Taipei, Taiwan, provided an opportunity for academics, service providers, and vendors to demonstrate techniques that address the need for IPv4 multicast service continuity. Two demonstrations were arranged for that purpose, thanks to a close collaboration among Beijing University of Posts and Telecommunications (BUPT), China Telecom, Comcast, France Telecom/Orange, Huawei, and ZTE Corporation. Show less

Several organizations collaborated to carry out the Port Control Protocol (PCP) demonstrations during the IETF Quebec City meeting. PCP is a simple, flexible, lightweight protocol that is being designed by the IETF to address some of the issues raised by the forthcoming IPv6 transition period where access to some legacy IPv4 content requires the control of firewall or network address translator capabilities for the dynamic allocation of transport-layer port numbers.

In certain application scenarios, there is a range of devices involved with very different capabilities.
In the core of the Smart Grid, one will find full fledged servers. Close to metering points, one will
more likely see embedded PC-like devices that still offer plenty of resources when it comes to the
implementation of network protocols. Within industrial settings or households, we will likely find
so called constrained devices consisting of 8-bit or 16-bit microcontrollers with… Show more

In certain application scenarios, there is a range of devices involved with very different capabilities.
In the core of the Smart Grid, one will find full fledged servers. Close to metering points, one will
more likely see embedded PC-like devices that still offer plenty of resources when it comes to the
implementation of network protocols. Within industrial settings or households, we will likely find
so called constrained devices consisting of 8-bit or 16-bit microcontrollers with wireless network
interfaces such as 802.15.4 radios [1]. In scenarios involving a range of very different devices,
there is usually a desire to restrict the set of different protocols used to a certain subset that
can scale across device types. Experience with protocol gateways translating between protocols
providing similar services tells us that such gateways can cause nasty operational problems since
protocol semantics are often not 100% translatable in certain corner cases. Hence, it is often
desirable to implement multiple protocols even on constrained devices since this approach allows
easier integration with existing software components and a reduction of complexity (no protocol
gateways needed), which in turn usually leads to a reduction of operational costs. Of course,
in application scenarios where only constrained devices are used (or they clearly dominate), the
development of protocols optimized to the specific scenario reduces device complexity and may
be desirable. Show less