The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2003-Aug> msg00027



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

draft-ietf-mpls-in-ip-or-gre-01.txt to PS

  • From: Scott Bradner <sob@harvard.edu>
  • Date: Tue, 12 Aug 2003 11:36:04 -0400 (EDT)
  • Cc: mpls@UU.NET, swallow@cisco.com


> I thought that  IANA Considerations are only needed  if there are additional
> values which IANA may be called upon to assign in the future. 

such a section is needed whenever the IANA should do something -
on the specific document or setup a process for the future - this
doc assumes that values will be assigned but does not say specifically
that the values should be assigned

> Probably I should ask IANA for  assignments now, but I'm always reluctant to
> do that  because they  hardly ever respond  ;-( Alternatively we  could hope
> that the  RFC editor will get  the assignments made  by IANA as part  of the
> pre-publication process.  What's our best bet? 

the normal process is for the RFC Editor to ask the IANA (one of the
reasons for the IANA considerations section - so that the need to
request is clear)

> Scott> I predict that there will be  pushback from the security ADs over the
> Scott> level of non-detail about how to use IP Sec to secure the links 
> 
> What level of detail do you think they will require? 

at least say something about what IPSec mode and where keys come from
(manual would work for me but I'm not a SEC AD) - but this is hard to
predict (at least for me)

Scott