[fmc] New Version Notification for draft-schott-fmc-requirements-01.txt - Input

[<[e-mail]>]

Hi all,

regarding our new version I make the proposal to update
the introduction an terminology part by some references/cites.
Therefore I have put the information I had about section 1, 3 and 11
together and combined it.

I suggest also referencing to draft-sun-fmc-use-case-00.


---

1.  Introduction

   With the network heterogeneity and huge demand of multimedia and
   audio-visual services and applications, users' satisfaction is the
   aim of each service provider to reduce the churn, promote new
   services and improve the ARPU (Average Revenue per User).  A crowded
   market is observed with many players providing Internet and
   entertainment services which triggers new business models considering
   users' experience and considering roaming agreement between different
   operators.  In this crowded market, the new expectations for users'
   consumption style focus on personalized and interactive usage
   allowing users on one hand to share content across many devices and
   with other users and on the other hand to access content all
   seamlessly at the touch of a button.

   Under the term Fixed-Mobile Convergence various meanings can be understood.
   This document has not the ambition to give a complete definition regarding
   business and technical aspects.
   Fixed-mobile convergence has recently been used to include various
   use cases in which a wireless device travels between a point of
   attachment in a mobile network (such as a cellular base station) and
   another point of attachment anchored in a fixed network such as a
   WiFi hotspot.  Convergence refers to a perceived unification of the
   service level available to applications which is, to the extent
   feasible, independent of the nature of the underlying physical
   medium.


   Consequently, Quality of Experience (QoE) has become a crucial
   determinant of the success or failure of the multimedia and audio-
   visual applications and services.  QoE evaluates the users' perceived
   quality for the provided services and hence reflects the users'
   satisfaction.  Regarding QoS 3GPP has defined architecture as
   described in [TS23.203] and [TS29.212]. Additionally IETF has also described
   how QoS can be achieved over IP [RFC 5865].


   This document proposes a set of requirements based on use cases
   including those discussed in [I-D.draft-sun-fmc-use-case-00].
   These use  cases have been underdiscussion in BBF [WT-203].
   The requirements discussed in this document are meant to help the IETF
   community to decide whether it should take part of the corresponding effort
   or not.

   This document identifies and analyzes issues that have arisen so far
   and elaborates a set of requirements for the FMC protocol design.



3.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as specified in [RFC2119].

   The following additional terms are used in this document:

   Codec

      Compression/Decompression of multimedia data through a hardware
      device or software.


   CPE

      Customer Premises Equipment.  Equipment found in the customer's
      physical location and provided by the network operator or service
      providers.  DSL routers, Set-Top-Box (STB), decoders, .. are
      examples of CPE.


   FMC

      Fixed Mobile Convergence means enabling an end-user to access
      services or retrieve content whatever the network access conditions
      (e.g., fixed or mobile access infrastructure), and whether the end-
      user is in motion or not. This includes also access conditions with
      this own service profile although having access by a 3 rd party.



   host_id

      an identifier for the wireless device, as described in
      [I-D.ietf-intarea-nat-reveal-analysis].

   Port set

      a defined set of ports, in this document used as an example of a
      host_id.  Each host under the same external IP address is assigned
      a restricted port set.  These port sets may then be advertised to
      remote servers.  Port sets assigned to hosts may be static or
      dynamic.




11.  References

11.1.  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC3711]  Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K.
              Norrman, "The Secure Real-time Transport Protocol (SRTP)",
              RFC 3711, March 2004.

   [RFC4301]  Kent, S. and K. Seo, "Security Architecture for the
              Internet Protocol", RFC 4301, December 2005.

   [RFC5246]  Dierks, T. and E. Rescorla, "The Transport Layer Security
              (TLS) Protocol Version 1.2", RFC 5246, August 2008.

11.2.  Informative references

   [RFC2663]  Srisuresh, P. and M. Holdrege, "IP Network Address
              Translator (NAT) Terminology and Considerations",
              RFC 2663, August 1999.

   [RFC6269]  Ford, M., Boucadair, M., Durand, A., Levis, P., and P.
              Roberts, "Issues with IP Address Sharing", RFC 6269,
              June 2011.

   [RFC6264]  Jiang, S., Guo, D., and B. Carpenter, "An Incremental
              Carrier-Grade NAT (CGN) for IPv6 Transition", RFC 6264,
              June 2011.

   [RFC5996]  Kaufman, C., Hoffman, P., Nir, Y., and P. Eronen,
              "Internet Key Exchange Protocol Version 2 (IKEv2)",
              RFC 5996, September 2010.

   [TS29.212]
              "3GPP TS29.212, Policy and Charging Control (PCC) over
              Gx/Sd reference point", December 2011.

   [TS23.203]
              "3GPP TS23.203, Policy and Charging control architecture",
              December 2011.

   [RFC 5865]
              Baker, F., Polk, J., Dolly, M.,A Differentiated Services Code
              Point (DSCP)for Capacity-Admitted, May 2012 Traffic

   [TR23.829]
              "3GPP TR23.829, Local IP Access and Selected IP Traffic
              Offload (LIPA-SIPTO)", October 2010.

   [I-D.so-ipsecme-ikev2-cpext]
              So, T., "IKEv2 Configuration Payload Extension for Private
              IPv4 Support for Fixed Mobile Convergence",
              draft-so-ipsecme-ikev2-cpext-02 (work in progress),
              June 2012.

   [WT146]    "Broadband Forum Working Text WT-146, Subscriber
              Sessions", June 2011.

   [I-D.ietf-intarea-nat-reveal-analysis]
              Boucadair, M., Touch, J., Levis, P., and R. Penno,
              "Analysis of Solution Candidates to Reveal a Host
              Identifier (HOST_ID) in Shared Address Deployments",
              draft-ietf-intarea-nat-reveal-analysis-02 (work in
              progress), April 2012.

   [WT203]    "Broadband Forum Working Text WT-203, Interworking between
              Next Generation Fixed and 3GPP Wireless Access",
              December 2011.

   [samog]    "3GPP TR 23.852 V1.0.0, Study on S2a Mobility based On GTP
              & WLAN access to EPC (SaMOG) (Release 11)", December 2011.

   [ieee802.11]
              "Information technology - Telecommunications and
              information exchange between systems - Local and
              metropolitan area networks - Specific requirements - Part
              11: Wireless LAN Medium Access Control (MAC) and Physical
              Layer (PHY) specifications", IEEE Standard 802.11, 2008",
              2008.

   [I-D.draft-sun-fmc-use-case-00]
           Xie, C., Sun, Q., Use Cases and Requirements in Fixed Mobile
             Convergence (work in progress), July 2012

---

Regards

Roland