|
Choose Mail Service
Select the mail service that you would like to use with your
FlexTraining Software. When using a Windows 2003 Server or better, you must
choose either CDO or Remote SMTP. CDO
is the recommended choice.
Enter Remote SMTP Server
Remote SMTP allows you to connect to your own privately run
mail server located on a different system than the FlexTraining
installation. Enter the web address of
this external server here.
Select Remote Security Type
Security Type is the type of login access required to use
the remote SMTP mail server. The three
options are: 1) Anonymous, which is the least secure method of connection, 2)
Basic, which sends the password in clear-text format, and 3) NTLM, which is an
encrypted password format. You will need to use the format that is dictated by
your Remote SMTP server’s configuration.
Enter Remote SMTP Login
If you choose Basic or NTLM for the Security Type setting,
you must specify a login name here.
Enter Remote SMTP Password
If you choose Basic or NTLM for the Security Type setting,
you must specify a password here.
Select Remote SMTP SSL
If your remote SMTP server requires the use of Secure Socket
Layers, specify “Yes” here.
|
Training
Region. There were 26 comments submitted related to the definition of a region. Seven comments supported the open definition provided in the NPRM, arguing that the possible integration opportunities in an area should define the region and that there were too many possible variations to allow a restrictive definition. Six commenters who expressed concern over varying conditions interpreted the definition to mean Metropolitan Planning Area (MPA). Five comments suggested an MPA was too restrictive. Eight other comments indicated that the proposed definition of a region did not clearly identify what entity would have the lead in developing a regional ITS architecture or thought the definition implied the MPO should have the lead. Nine comments suggested various limits or boundaries to fit specific situations. Ten comments expressed a need for greater clarification of the definition for a region.
The intent of the proposed definition was to allow considerable flexibility on the part of the stakeholders in defining the boundaries of a region to best meet their identified integration opportunities. While there was no intent to generally restrict the definition to MPAs or States, the FHWA determined that regional ITS architectures should be based on an integration strategy that was developed by an MPO or State as part of its transportation planning process.
Given that the final rule does not require or reference an integration strategy, the FHWA feels a need to provide more specific guidance on the definition of a region. As such, the definition of a region has been revised to indicate that the MPA should be the minimum area considered when establishing the boundaries of a region for purposes of developing a regional ITS architecture within a metropolitan area. This should not be interpreted to mean that a region must be an MPA, or no less than an MPA, but the MPA and all the agencies and jurisdictions within the MPA should be at least considered for inclusion in the process of developing a regional ITS architecture within a metropolitan area. This rule is silent on other possible limits or minimum areas for defining a region, relying on the flexible nature of this rule to accommodate those special circumstances. The FHWA also acknowledges it is possible that overlapping regions could be defined and overlapping regional ITS architectures be developed to meet the needs of the regions.
|