Replacement IESG Note for draft-foster-mgcp-basic-packages-10.txt

[Allison Mankin <mankin@psg.com>]

The reason for the change is that the new one matches the one
we used in RFC 3435 and mentions security in particular.

---------
RFC Editor, replace the IESG Note in draft-foster-mgcp-basic-packages-10.txt.

Old:

IESG NOTE: 
 
  This document is being published for the information of the 
  community. It describes a non-IETF protocol that is currently being 
  deployed in a number of products. Implementers should be aware that 
  the IETF Megaco working group and the ITU-T Study Group 16 have 
  produced a standards track RFC "Megaco Protocol Version 1.0" (RFC 
  3015, also published as ITU recommendation H.248) which addresses the 
  same problem space and are developing extensions to that protocol for 
  functions of this type.

New:

IESG Note

   This document is being published for the information of the
   community.  It describes a non-IETF protocol that is currently
   being deployed in a number of products.  Implementers should be
   aware of RFC 3015, which was developed in the IETF Megaco Working
   Group and the ITU-T SG16 and which is considered by the IETF and
   ITU-T to be the standards-based (including reviewed security
   considerations) way to meet the needs that MGCP was designed to
   address.  The IETF Megaco working group and the ITU-T Study Group
   16 are developing extensions to RFC 3015 that for functions of the
   type in addressed in this document.