FW: Manual Post Requested for draft-porfiri-dhc-dhcpv4-over-dhcpv6-ra

Here we are with the Post Request.

Best regards,
Claudio Porfiri

-----Original Message-----
From: IETF I-D Submission Tool <[email protected]> 
Sent: Thursday, February 1, 2024 8:56 AM
To: [email protected]
Cc: Claudio Porfiri <[email protected]>; Claudio Porfiri <[email protected]>; Jari Arkko <[email protected]>; Mirja Kuehlewind <[email protected]>; Suresh Krishnan <[email protected]>
Subject: Manual Post Requested for draft-porfiri-dhc-dhcpv4-over-dhcpv6-ra


Hi,

Manual posting has been requested for the following Internet-Draft.
The IETF Secretariat will handle this request; no further action is
required at this time.


Full idnits results are available at the end of this message.

I-D Submission Tool URL: 
  https://datatracker.ietf.org/submit/status/139810/

  File name       : draft-porfiri-dhc-dhcpv4-over-dhcpv6-ra
  Revision        : 00
  Submission date : 2024-01-31
  Group           : Individual Submission 

  Title           : DHCPv4 over DHCPv6 with Relay Agent Support
  Document date   : 2024-02-01
  Pages           : 7
  File size       : 16.8 KB

  Submitter       : Claudio Porfiri <[email protected]>

  Abstract        : 
   This document describes a general mechanism for networks with legacy
   IPv4 only clients to use DHCPv4-over-DHCPv6 (DHCP 4o6) for
   discovering information about network Topology.  To address this
   scenario, this document specifies an amendment to RFC7341 that allows
   a new 4o6 Relay Agent (4o6RA) to perform the 4o6 DHCP en- and
   decapsultion instead of the client.



  Authors:
    Claudio Porfiri <[email protected]>
    Suresh Krishnan <[email protected]>
    Jari Arkko <[email protected]>
    Mirja Kuehlewind <[email protected]>


  Comment to the secretariat:




  Idnits result:

idnits 2.17.00 (12 Aug 2021)

/a/www/www6s/staging/draft-porfiri-dhc-dhcpv4-over-dhcpv6-ra-00.txt:
-(7): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding

  Checking boilerplate required by RFC 5378 and the IETF Trust (see
  https://trustee.ietf.org/license-info):
  ----------------------------------------------------------------------------

     No issues found here.

  Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt:
  ----------------------------------------------------------------------------

  == There are 2 instances of lines with non-ascii characters in the document.

  == The page length should not exceed 58 lines per page, but there was 1
     longer page, the longest (page 1) being 384 lines


  Checking nits according to https://www.ietf.org/id-info/checklist :
  ----------------------------------------------------------------------------

     No issues found here.

  Miscellaneous warnings:
  ----------------------------------------------------------------------------

  == Couldn't figure out when the document was first submitted -- there may
     comments or warnings related to the use of a disclaimer for pre-RFC5378
     work that could not be issued because of this.  Please check the Legal
     Provisions document at https://trustee.ietf.org/license-info to determine
     if you need the pre-RFC5378 disclaimer.


  Checking references for intended status: Proposed Standard
  ----------------------------------------------------------------------------

     (See RFCs 3967 and 4897 for information about using normative references
     to lower-maturity documents in RFCs)

     No issues found here.

     Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 0 comments (--).

     Run idnits with the --verbose option for more detailed information about
     the items above.




_______________________________________________
dhcwg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dhcwg